[1.0.4] Load order bug?

[Crim, The Red Thunder]

Just finished downloading this nice new addon called beholder. Rather then jump right into it, I turn it off and load up an old character I'm still working on. This character had been run many times, and still worked with no conflicts/issues. However, it refused to load, hung at 100%, and never went anywhere.

Attempting to start a new game, with the same 3 addon's involved also hung. (In this case, the addon's were I500, Arcanum, and opt-in adventurers). These have cooperated many times. I have run numerous characters with them. No conflicts. New game, hangs at 100%.

Deleting the beholder addon from list, and trying again, everything works again. Now, since it was turned off, someone suggested it would be influencing load order, which would be causing conflicts. Not sure if this is the case, or if there is some bizarre bug in the game itself.

Following is the logfile from attempting a newgame, with the 3 addons in question, before deleting beholder.

So what did happen, and how to resolve it in the future?

[Hachem_Muche]

It doesn't make sense that an addon that is not being bound would affect this, but all addons are at least preliminarily processed when loading a module (if only to be rejected by game/savefile settings).

Looking through the log, the last few lines show a talent redefinition error.

I500 loads a new engine routine (_M:newTalent) specifically to allow talents to be redefined, so this error means that the new routine is either being overwritten (by the original version) or being prevented from running somehow. I500's new talent information can't be loaded without it and so causes the crash.

The log is incomplete and the stack traceback is cut off. Can you run the game with the -flush-stdout option and duplicate the error to get a complete log? That should give a complete traceback that will pinpoint where the error is starting.

[Crim, The Red Thunder]

This is the same as using the launcher and it's option for 'flush logs' before running, correct? If so, this should be what you're looking for. (Worth mentioning, this is a newer version of beholder, but the same issue occurs causing no new game to start, or old games to load, even with the addon disabled).

[StarKeep]

Did you try to manually edit the init.lua file, and change the weight to 101?

[Crim, The Red Thunder]

How do I do that? (And no, obviously )

[Hachem_Muche]

I've just uploaded a new version of I500 (http://te4.org/sites/default/files/game ... 1.10c.teaa).

The only change is I set the addon weight to 99 (so it get's loaded first). This seems to fix the problem, which appears to be an instantiation issue with nesting of the newTalent function in engine.interface.ActorTalents.lua and data.talents.lua. Somehow redefining this function after it is nested confuses the engine's module loader and it reverts to the raw version (pretty strange).

With this change, I was able run the game with I500, arcanum, opt-in-adventurers, and the beholder addon, though I didn't try to find any explicit compatibility issues.

(Note: Editing the init file will invalidate the addon.)