[Mod] "Simoom's Lantern" - Ultimate Cheat Menu

[alexalsp]

Not sure.

I put the empty station. I hired crew.
With Maelstrom jumped in Devriese crew in place.

http://imgur.com/a/D1l0Z

How long to wait before the disappearance of the crew?

PS

I do not use this mod.

[Nikola515]

So it was not just me than... Fell free to ask me if you need anything else tested

[mr.WHO]

Hi Simoom - I just want to drop by and say that Canteran plot statino script work fine - missing stations have been placed and shipyard build and sell ships - suprisingly the first capship that is build is Construction Vessel, so I wonder what will AI do with it.

[Marvin Martian]

as far nothing is changed on vanilla AI-shipyard script the ship will get "explore" (move die) because it is simply to have use of delivered ressources, nothing more

but with some changes, the ship can used as Trader like other ships, maybe better, because Marodeur-Pirates will not take care about Ships with "build"-purpose

[Simoom]

AHA! Tracked down the cause of the assigned station crew disappearing! No solution yet, simply found the cause.

It would seem that there's something inherently different about crew members generated by the mod (via "Summon Personnel") from the "normal" crew you can hire from stations.

Any station crew generated by "Summon Personnel" would disappear when assigned to a player station, when the player leaves zone. However, crew you HIRE normally from an NPC station will not disappear.

It would seem that the characters generated by "Summon Personnel" is being flagged as "generic" NPC's, not player crews, and therefore being despawned by the NPC generator ("ai_unit"). I just need to figure out why that is.

For now, please hire your station crew "normally", or simply use the ones spawned with the station.

[alexalsp]

I can not confirm. 30 minutes waiting. A hired the crew on a player stations. Assign crew on the empty station.

Waited in the zone, the zone changed, and systems. Everything is in place.

How long to wait? ))

[Nikola515]

@ Alex

This bug is only related to this mod. When you place station you get crew already inside so you don't need to place anyone. But if you want to replace that crew that's when you start having thise problems. I haven't used your mod for some time now but i think they work much differently.

Edit: Also Simoom have function where you can turn station to NPC and with working manager script (especially for shipyards). So that might be one of reasons why this is happening.I suck in making mods (i can do only some basic XML file editing) but im pretty sure this was not easy and many things that can go wrong...

[Simoom]

Guys, I found the cause of the issue, and filed a bug report here:
http://forum.egosoft.com/viewtopic.php? ... 75#4609675

The issue has to do with the way NPC's are categorized when spawned. If an NPC is created using <create_cue_actor>, the value $customactor is set, and this NPC will not receive a "timeout" value (which will destroy the NPC in 10-20 minutes, or destroy it immediately if the player leaves the zone the NPC is in - which is the case if you assign him to a station and then leave).

All NPC's created using <create_platform_actor> (which is pretty much 99% of the NPC's you see in game) will receive a "timeout" value by default, because all NPC's are meant to be temporary. The ONLY exception is if the NPC is already a controlentity at the time of spawning (such as the ones spawned alongside a station - which is why the station crew created by "Summon Stations" do not disappear).

Now, when you hire a "normal" NPC (created by <create_platform_actor>), this timeout value gets cancelled. The problem is if an NPC is spawned directly onto the Skunk using <create_platform_actor>, already owned by you, then he WILL have a timeout value that never gets cancelled (because you never "hired" him). This means he will disappear the moment you assign him to a station and leave the zone.

At this time, the only way to fix this issue is to avoid using <create_platform_actor> completely for spawning NPC crew directly onto the Skunk. I am already working on the fix, will post an update in a minute.

@ alexalsp - If you are using <create_cue_actor> in "setup_npc_cheat_menu.xml", you are fine. Avoid <create_platform_actor> (except for specialists, they don't have a timeout value by default)

[hisazul]

Hi Simoom,
1. Taking over an NPC station to yourself makes a bug where all the personal has a ?????????????? and you can not change any options like manager acount and so on. By reloading the game it works fine. I have to say thought that also used other station mods like StationEngineer and populate player stations, so i am not sure if the mentioned mods have a compatibility issue (sorry i did want to look into the dubug log, but its was over 380 MB big, so i gave up, most ot the errors where caused by CES).

That "??????" all over has nothing to do with the mod, I had that happen to me a few times. Can't recall if I saw that happen before 4.0 or after.

[Simoom]

Version updated - the issue with crew disappearing has been fixed! Even added some new extra goodies for you good folks (race selection for crew spawning) - below is the new changelog.

Update 5/3/16:

• [New Feature] "Repair Station Wreck": Restores wrecked NPC stations in player's current zone. Feature not yet functional. Codes are in place, but the detection routine isn't yet working.
• [Improvement] "Claim Target": Feature now automatically sets the target's status to fully revealed before setting the owner faction to the player. This should circumvent the UI glitch where a NPC ship or station that has been turned to you still shows "???" under its details.
• [Improvement] "Summon Personnel": Race selection now available! Choose from Argon, Canteran, Teladi, or Split crew!
• [Bug fix] "Summon Personnel": Crew created by this feature no longer despawn when player leaves zone (after assigning the crew elsewhere). Issue was tracked down to <create_platform_actor>, which doesn't include a safety check to exclude player-owned actors from being assigned a "timeout" value (technically a dev oversight, though under normal circumstances player-owned platform actors wouldn't spawn directly onto the Skunk without being hired - and the hiring action is what triggers the timeout cancellation). This feature now uses <create_cue_actor> to circumvent the issue.

If you have spawned any crew using "Summon Personnel" before this version, please fire them and spawn new ones!

[Nikola515]

Nice update

Would it be possible to disable boost/shield draining. This would be useful when it comes to exploring. Especially exploring sectors without highways.....

[Simoom]

Nice update

Would it be possible to disable boost/shield draining. This would be useful when it comes to exploring. Especially exploring sectors without highways.....

Your shield will not drain from boosting when "Immortality" (god mode) is enabled.

[Nikola515]

Nice update

Would it be possible to disable boost/shield draining. This would be useful when it comes to exploring. Especially exploring sectors without highways.....

Your shield will not drain from boosting when "Immortality" (god mode) is enabled.

Thanks for info I haven't tried God mod yet but I will check it out.


Edit: Another bug that I have discovered (not sure if it is bug). When using X-perimental jump when docked inside station whole station will jump with you. Docked in cap ship will do the same thing. All though I must agree it is somewhat fun

Edit2: Also I noticed that warehouse that I summoned (never changed to NPC) is having player engineer.

http://images.akamai.steamusercontent.c ... 8C2E57B0A/

Edit3: I did some more testing and it looks like this is case with every new summoned station and not just warehouse. It is nice not to worry about getting your stations destroyed

[Simoom]

Edit: Another bug that I have discovered (not sure if it is bug). When using X-perimental jump when docked inside station whole station will jump with you. Docked in cap ship will do the same thing. All though I must agree it is somewhat fun

The script is written to jump the "container" of the Skunk (whatever it is docked at) if the player is docked somewhere. This is for convenience reasons (so if you are docked on a capship, you don't have to undock to jump).

I should probably disallow the whole station being jumped along though... That's just silly.

Edit2: Also I noticed that warehouse that I summoned (never changed to NPC) is having player engineer.

http://images.akamai.steamusercontent.c ... 8C2E57B0A/

Edit3: I did some more testing and it looks like this is case with every new summoned station and not just warehouse. It is nice not to worry about getting your stations destroyed

This is intended. Stations are actually meant to have engineers, regardless of player or NPC. Egosoft disabled the ability for players to assign an Engineer to a station, because they want to force players to do station repairs through the Architect/CV (which is annoying, but I understand why they implemented it that way). But by default all stations can accommodate engineers (which is why w.evans' "Station Engineers" mod is literally two lines of code - all it does is enable the player to assign engineers to stations, and Egosoft's own scripts handle the rest).

I figured people who don't want engineers on their stations can just unassign them (tell them to "Come back on board").

[Nikola515]

That's good to know about engineers..... I was always wondering why player didn't have them on station on first place.

[Marvin Martian]

"Claim Target": Feature now automatically sets the target's status to fully revealed before setting the owner faction to the player.

if you would use player.primaryship.owner instead of faction.player you can with set_cover_owner (at player+ship) realize simple change into each faction without great changes
you only need to make at the relevant positions a switch to npc-scripts in case they different

[Simoom]

"Claim Target": Feature now automatically sets the target's status to fully revealed before setting the owner faction to the player.

if you would use player.primaryship.owner instead of faction.player you can with set_cover_owner (at player+ship) realize simple change into each faction without great changes
you only need to make at the relevant positions a switch to npc-scripts in case they different

I am not too sure how the "realowner" and "coverowner" system works - can you elaborate on this?

[Marvin Martian]

set

Code: Select all

<set_cover_owner object="player.primaryship" faction="$coverfaction"/>

unset

Code: Select all

<set_cover_owner object="player.primaryship"/>

at cover state player.primaryship.owner will return the coverfaction (or faction.player if not covered)
player.primaryship.trueowner is always faction.player (or what faction the object is)
i know there is a .coverowner (or something like that), but no idea for what is good for, maybe it returns false in uncovered state - i think .owner is always good enough

so use for conversation coditions if you check about player stuff better always about .trueowner (or .isplayerowned should return also true i think, not tested yet) instead of .owner if you think about to use coverfunctions

[mr.WHO]

Can we have a Jump Drive coolant in "Grant Treasures" section?

[Simoom]

Can we have a Jump Drive coolant in "Grant Treasures" section?

Yeah I can add the jump drive components into the treasure hunt section...