Actually, it does seem like it would be useful to use an event handler here. Just create a generic Type with the necessary Communications, Events, and Language elements, then you can add that code with eventHandler= in the ShipClass or (objSetEventHandler obj unid). If you use the latter, you might ...

Event handlers basically just allow you to add the XML of another type onto the XML of an existing object, usually to add Events and Language elements. You don't need them if you just want to change how one type behaves at all times. To change Salvagers' behavior without modifying the engine, you'd ...

Maybe just always generate the list of known systems with (filter (sysGetNodes) node (sysIsKnown node)) ? With a bunch of non-contiguous systems known, allowing manual reordering and deciding how to maintain the order as you discover systems seems like more trouble than it's worth. I guess you could...

Seems like there might be yet another bug. I think "level=9" is supposed to override the system level, so the loot shouldn't depend on system level. "x=" multiplies the total value of the items to be generated, and there's some formula to determine how much to multiply the number appearing of each i...

It's hard-coded in the engine, I believe, but I haven't looked at it.

Currently the in-game display is in 10ths (rounded), so 2 = 25%, 3 = 32% ... 10 = 100%. I'd like it to be more clear, too, but George didn't seem to like my suggestions.

Nice! I'm looking forward to this never coming out so I can not play it!

Thanks again. More great info explained really well. Using this code will remove a heap of list handling code from the mod. I couldn't make the 'adding a value' code work unless the 'theStruct' already existed. I misunderstood what you meant by "theStruct can be Nil to start". Once I set 'theStruct...

They don't function normally. They collapse more easily, maybe if they take any damage at all.

SysFindObject finds autons in OnGlobalPlayerLeftSystem for me. Try something like this:

So there seem to be two issues: 1. The number of distinct items generated is too small for tables with large multipliers, resulting in very large quantities being needed to add up to enough value. 2. All the items may be drawn from the same entry in the Items table, resulting in several kinds of arm...

This is probably due to the changes to enable level-based treasure value in API 39 . Maybe it's picking one item and scaling up the quantity to the specified value rather than picking more items. Unfortunately, the logic is buried in many levels of helper functions and I can't find the relevant part...

There can be multiple non-recurring timers of the same name on a type/object/whatever. I'm not sure about recurring timers. Regardless, the cancel functions cancel all matching timers, so this should be OK.

If you want something more plausible but still straightforward, you could have to buy a starship field repair kit, or hire a mobile repair platform wingman.

Presumably you'd use the node IDs as keys. One option is to allow each value to be an object or list of objects. E.g. { SE:(15708 15672) BA:2098 } You could add to the struct with: (setq theStruct (structAppend theStruct key value)) In many cases this would be OK, but sometimes you might have to che...