Post by Stingray888 on Aug 10, 2013 6:15:21 GMT
There is a limit of about 16,000 resources in a module (when not counting contents of hak files). To see how many you are at, open your module in the toolset, go to your NWN/modules/temp0 folder and see how many files are in there.
Each script takes up 2 resources (a .nss file (script text) and a .ncs file (compiled script)).
Each item blueprint takes up 1 resource.
Each creature blueprint takes up 1 resource.
Each placeable blueprint takes up 1 resource.
Each merchant blueprint takes up 1 resource.
Each trigger blueprint takes up 1 resource.
Each sound object blueprint takes up 1 resource.
Each encounter blueprint takes up 1 resource.
Each waypoint blueprint takes up 1 resource.
Each door blueprint takes up 1 resource.
Each area takes up 3 resources (1 .git file, 1 .gic file, and 1 .are file).
Each of the palettes adds 1 file (.itp files).
You can exceed this limit by moving script and blueprint files into a hak file (where I think the limit is also near 16k resources) that is located server-side (for a PW/online module) or on your computer (for a single-player module), and associated with your module.
There is another limitation in-game. If there are too many total blueprints on the palettes (a combination of those stored directly in the module file and those in haks), DMs can crash their game client when they enter the running module. Not sure of the limit here, but it might also be around 16k (I'm sure somebody else knows this limit).
My module is currently 97.5 MB with somewhere over 550 areas, hundreds of items and scripts, and it runs without any problems.
My module currently uses 13,285 resources, which I'm in the process of reducing by rewriting all of the spells and many other scripts (combining many spells into multipurpose scripts, then moving those combo scripts to a hak file) and removing many blueprints (particularly placeables) that aren't called by scripts (I usually just drop in any placeable and edit the properties for my current needs anyway rather than rely on the palette anymore).
Each script takes up 2 resources (a .nss file (script text) and a .ncs file (compiled script)).
Each item blueprint takes up 1 resource.
Each creature blueprint takes up 1 resource.
Each placeable blueprint takes up 1 resource.
Each merchant blueprint takes up 1 resource.
Each trigger blueprint takes up 1 resource.
Each sound object blueprint takes up 1 resource.
Each encounter blueprint takes up 1 resource.
Each waypoint blueprint takes up 1 resource.
Each door blueprint takes up 1 resource.
Each area takes up 3 resources (1 .git file, 1 .gic file, and 1 .are file).
Each of the palettes adds 1 file (.itp files).
You can exceed this limit by moving script and blueprint files into a hak file (where I think the limit is also near 16k resources) that is located server-side (for a PW/online module) or on your computer (for a single-player module), and associated with your module.
There is another limitation in-game. If there are too many total blueprints on the palettes (a combination of those stored directly in the module file and those in haks), DMs can crash their game client when they enter the running module. Not sure of the limit here, but it might also be around 16k (I'm sure somebody else knows this limit).
My module is currently 97.5 MB with somewhere over 550 areas, hundreds of items and scripts, and it runs without any problems.
My module currently uses 13,285 resources, which I'm in the process of reducing by rewriting all of the spells and many other scripts (combining many spells into multipurpose scripts, then moving those combo scripts to a hak file) and removing many blueprints (particularly placeables) that aren't called by scripts (I usually just drop in any placeable and edit the properties for my current needs anyway rather than rely on the palette anymore).
