wow if that is true that is a really bad bug.

I would like to make items that you could run an event on called powerUp and after a time specified in the xml it would call powerDown. You could use this to put arbitrary timed events on things. For example you over charge on your over chargeable weapon it would do double damage for a time then do ...

itmSetPower would be a nice thing to have but the only problem with that is we don't have a way of doing timed events for items. (other than onUpdate and that is expensive)

what started this all is because we wanted a weapon that fired only when certain conditions where met. Using firing power even when not being fired didn't seem fair. Maybe an easier solution is to allow a return value from OnFireWeapon that communicates whether or not we should consume power (or so...

maybe we could do without timers if we had events for when it would normally change power.

what started this all is because we wanted a weapon that fired only when certain conditions where met. Using firing power even when not being fired didn't seem fair.

There would be a default that you would put in the xml (like all items currently have). The new power use would be used instead of that one while it is active (however long the timer is). If a new one is applied it would overwrite the old one (this is on a single device so I don't see any issues wit...

I was thinking just a stored number for the current power consumption stored on the item that would be removed or invalidated after the timer is done. I suggested that way because a GetPowerConsumption would be expensive and power use doesn't change that often. There might be use for a flag to say n...

I would think a itmConsumePower might be easier. It would overwrite the old itmConsumePower and you would already have a list. It would only consume extra power for installed items so you would need virtual equipped items for consuming power with no corresponding equipped item. You would also need a...

objAddOverlay returns the id of the added overlay so save that and use that to remove.

hmm this could also be an issue with the forth coming canFire event but I am not sure how to say you can't fire now and you can't fire ever again.
Maybe in the canFire you would have the enemy gate out.

congratulations on getting 1.0 out. 8)
I also noticed that transdata 2.0 is out.

Shrike added

this is just a suggestion no one is going to take down a mod just because the mod maker forgot to put in what it over writes.

for post 1.0 I would like some way to tell the game what kind of things and how often a shot will interact with a given object. maybe an event called <ShotInteraction> that returns a percent chance that the shot interacts with the given object. Things this would help would be things like lasers shou...