Teilnehmer

I don’t hate Dres at all. I hate Ike instead. Btw, in Toki Pona, ike means ‘bad’.

I wanted to use the OnVesselRollout event in my mod to do stuff only when the vessel is at launch, but discovered that this event is not triggered after a Reverting to Launch. I’d prefer identical behavior for the first launch and relaunches. How can I detect that a Reverting to Launch has happened?

Version 1.11.4 Fixes: Revert to launch bug fixed. ModuleAutoAction is always writen to the craft file again. Warning:  Bugs of all kinds are still totally possible. Please report!

I cover my head with ashes! The mod doesn’t work at all when reverting to launch. Unfortunately, the onVesselRollout event does not trigger after reverting to launch for some reason. So, now, I have to revert to the old logic which also has some minor issues.

Thanks a lot! Now, I can add action set support to my AutoActions mod.

   Version 1.11.3 What’s new: Now, you can choose which action set will be activated on launch. (Thanks to @JPLRepo) Warning:  Bugs of all kinds are totally possible. Please report!

   Version 1.11.2 What’s new: Updated to KSP 1.11.0. Added ‘Stage’ button making the vessel stage on launch. Less craft file spamming: only one ModuleAutoAction per file, only non-default settings in ModuleAutoAction, no ModuleAutoAction when no no-default settings. Fixed behavior after the ‘Switch editor’ button is clicked. Some minor fixes and changes. Warning:

How can I set the current action set (default, 1, 2, 3, or 4) in flight from code?

In my mod AutoActions, I use ModuleManager to add a module to all command parts to store per-vessel settings in it. When a craft file is saved in KSP without the mod, and I open it in KSP with the mod (or vice versa), everything works fine except for some warnings in the log: [WRN 11:34:59.939] [Part]: PartModule indexing mismatch at probeCoreOcto2.v2, index 5. Node 'ModuleAutoAction' found in loaded data, but 'ModuleTripLogger' is defined in prefab. Looking for ModuleAutoAction in other indices... Is it bad to have warnings like that? Does it cause performance losses or something?

Version 1.11.0.0 Updated to KSP 1.11.0.

Version 1.11.0.0 Updated to KSP 1.11.0.

Here’s a silly minimal example of two-way communication between two mods via Reflection: https://github.com/formicant/ModCommunicationSample The Util mod detects the current vessel’s throttle changes and invokes throttleChanged events. The Other mod changes the current vessel’s cargo bay door deploy limit according to the throttle evel received from the Util mod. It calls the methods of the Util mod to subscribe to the events or unsubscribe. The UtilApiWrapper and UtilApiAlternativeWrapper do the same thing but are written a bit differently.

Here, I’m doing this in my mod CriticalTemperatureGauge using System.Reflection: https://github.com/formicant/CriticalTemperatureGauge/tree/master/CriticalTemperatureGauge/Wrappers The wrappers provide access to the methods of Linuxgurugamer’s ClickThroughBlocker and ToolbarController mods, also providing a fallback behavior when the mods are not installed. Unfortunately, I had to write a lot of code to wrap the custom delegate TC_ClickHandler. However, if both UTIL and OTHER are your own mods, you have more freedom to make the access via Reflection less complicated. Delegates o

When a KSPAddon(KSPAddon.Startup.Flight) starts, what is the best way to determine if it’s a new vessel launch (not switching to an already launched vessel or loading a save)?

My first try — 51 383 m.