5 replies to this topic

[temnix]

In my ACTION.IDS (BG:EE) I had "AddXpWorth(O:Object)," that's number 384. The G3 Guide lists two versions of that action at that number: the one I had and "AddXPWorthOnce(O:Object*,I:ClearStat*BOOLEAN)." As you can see, they aren't the same - the second can make a creature XP-worthless after it relinquishes its points. That's what I needed in my case, but the engine wasn't recognizing the alternative, refused to compile. I edited my ACTION.IDS and replaced the action at 384. And it works on my setup, but what about players who download my mod? Do I need to include my ACTION.IDS? That seems a bit much.

[Avenger_teambg]

If you are making a weidu mod, you can add the entry with something like this:

 

APPEND ~action.ids~ ~384 AddXPWorthOnce(O:Object*,I:ClearStat*BOOLEAN)~        UNLESS ~AddXPWorthOnce~

 

This will work on current and future versions of EE.

 

You should have both versions of the action. 

Edited by Avenger_teambg, 22 December 2017 - 02:49 PM.

[temnix]

So two entries for 384 are no problem? Good to know.

[subtledoctor]

The UNLESS line means it won't be appended if it is already there

[The Imp]

The UNLESS line means it won't be appended if it is already there

No. You failed to ... I don't know what, but you failed, as the install will make the .ids read:
384 AddXpWorth(O:Object)
...
384 AddXPWorthOnce(O:Object*,I:ClearStat*BOOLEAN)

And then, as there two 384's, termix asks if that is OK, and it is.

Edited by The Imp, 26 December 2017 - 01:33 PM.

[Avenger_teambg]

Imp is correct again There are lots of actions with aliases, this was used even by the vanilla game, weidu can handle it too.

With the EE, we added a few 'enhancements' to old actions, but we kept the old syntax around so dialogs which use script source won't be broken.