NWN SCRIPTS

Someone ran into the instruction limit in their OnModuleLoad script after putting in 20 treasure tables. The KTG_DeclareTreasureTable function can require lots of instructions to complete for a large treasure table or once you get to a certain number of "tabled items". There is a limit on the number of instructions a single script is allowed to execute. The game engine interrupts the script when the limit is reached. Normally you will see a TMI (Too Many Instructions) error displayed when this limit is reached by a script and the game interrupts it. But since nobody is logged in when the OnModuleLoad script runs, you cannot see the message. What ends up happening is that the end of the OnModuleLoad script does not complete which obviously will cause problems with those systems you are using that rely on initialization in OnModuleLoad to complete correctly.

The good news is that there is a way to work around the limit by postponing part of a script so it gets run later after OnModuleLoad completes. The idea is to move some of the code out of the script into a script of its own, then have the original script call the new script using a DelayCommand. This allows the original script to use only a single instruction to accomplish what used to take very many...but the trade off is that the code won't get done until after the original script ends. This means it matters what code you choose to move out to the new script. Depending on what the original script is doing, it is not always safe to move the code out because it is needed later on in the original script. But for code that does not matter if it gets done just after the original script ends, you can safely move it out and thus effectively "give" the original script more instructions to run.

In KTG, declaring treasure tables need not be done in the OnModuleLoad script at all. You can declare a table from anywhere. Since it only ever needs to be done once, the OnModuleLoad is the best choice, but that is not a requirement. The requirement is that all tables be declared before you try to generate loot drops with KTG_GenerateTreasure using those tables. So it is safe to move the KTG table declaration stuff out of OnModuleLoad into a delayed script to allow OnModuleLoad to have as many instructions available to it as possible. This is a very good idea to implement in your module even if you aren't seeing a problem and I suggest using the following method instead of what is written in the user's guide.

Here's what you do:
===========================================================
First move all your KTG_DeclareTreasureTable calls out of the OnModLoad script and put them into a new script called "tt_declares" that looks like this:

// KTG Treasure Table Declaration script - tt_declares

#include "_ktg_inc"

void main()

{ DelayCommand( 0.1, KTG_DeclareTreasureTable( ...));

  DelayCommand( 0.2, KTG_DeclareTreasureTable( ...));

  DelayCommand( 0.3, KTG_DeclareTreasureTable( ...));

...

  DelayCommand( 2.0, KTG_DeclareTreasureTable( ...));

}

Next, where you removed all those declares from the OnModLoad, put this:

// OnModuleLoad script

#include "_ktg_inc"

 

...

 

void main()

{ KTG_SetLoggingEnabled( TRUE); // Optional

  KTG_SetBroadcastEnabled( TRUE); // Optional

  DelayCommand( 0.1, ExecuteScript( "tt_declares", OBJECT_SELF));

 

...

 

Hopefully using technique this will move enough instructions out of the OnModuleLoad script to allow it to complete all its tasks. It will minimize KTG's use of OnModuleLoad instructions and will also help protect against a really big treasure table causing a TMI that prevents other treasure tables from getting declared.