Compiler problems
Cablefish
Member Posts: 37
When i importing script packages to my PW freescape i ran into some problems when trying to compile a module that contained both CEP and Shayans Subrace Engine.
When compiling a module containing only Shayans Subrace Engine i ran into some IDENTIFIER LIST FULL errors at four of the spell scripts. However when i imported CEP i the toolset simply crashed with the ERROR ACCES VIOLATION.
I manege to get it to compile without any errors in 1.69 toolset using NWN:TX (Toolset Extender).
Since the extended toolset compiler doesn't spring any error messages i'm assuming its not a problem with the scripts but mainly with the compiler. Is there any plans to make the compiler more powerful or is anyone planning to make NWN:TX work with EE?
When compiling a module containing only Shayans Subrace Engine i ran into some IDENTIFIER LIST FULL errors at four of the spell scripts. However when i imported CEP i the toolset simply crashed with the ERROR ACCES VIOLATION.
I manege to get it to compile without any errors in 1.69 toolset using NWN:TX (Toolset Extender).
Since the extended toolset compiler doesn't spring any error messages i'm assuming its not a problem with the scripts but mainly with the compiler. Is there any plans to make the compiler more powerful or is anyone planning to make NWN:TX work with EE?
1
Comments
How to add haks: Stop the compile - hit cancel as soon as possible. Until the toolset is fixed this is the only option for larger modules.
Working with scripts or other module resources (remember not all hak materials are module resources) examples: scripts, areas (yes they can be in haks), creatures, placables, conversations, stores and such that are all contained in modules can be easily imported and exported via the temp folder.
When Toolset opens a module there is a temp folder made in the module folder. Cut and paste to this temp folder to add or delete resources. Save and reload the module.
The advantage of removing and or adding via the temp folder is:
1) Very easily and quickly done using the standard OS GUI
2) NO auto compile or other module breaking action taken by the toolset.
Using the compiler - go to the advanced options and turn off everything but the ONE thing you need it to do - such as compile scripts.
These tricks should keep you going.