Has anyone been able to mod Toolset?

[Baaleos]

               Hi guys,
Not sure whats going on, but

My module builds fine in both compilers. No errors.

However, when I build with the new extended toolset compiler, and go into game, a 'Traveller Charm' item I have, which acts as a multi-location recall stone, ceases to work.

But only some of the scripts.

When I build it again, using the default toolset, the scripts and the item, functions again.

Cant post the script contents, as I am at work.
I was just wondering if anyone noticed anything querky like that?
               
               

               
            

[Baaleos]

               Does anyone know

The 16k Limit, is this a limit of the .mod filetype, or limitation imposed by toolset or nwnserver.exe etc


Is it possible to mod this?
It just seems that if we have already improved the compiler, why stop there.
               
               

               
            

[Legacy_leo_x]

               

Baaleos wrote...

Hi guys,
Not sure whats going on, but

My module builds fine in both compilers. No errors.

However, when I build with the new extended toolset compiler, and go into game, a 'Traveller Charm' item I have, which acts as a multi-location recall stone, ceases to work.

But only some of the scripts.

When I build it again, using the default toolset, the scripts and the item, functions again.

Cant post the script contents, as I am at work.
I was just wondering if anyone noticed anything querky like that?

I noticed something similar too.  One of my scripts seemed to get corrupted and have the entire contents of the module in it, so the size of the module would essentially double and some scripts would cease to function.

Compiling scripts with the compiler was not even necessary to recreate it, it seems to happen on module save every time for me.  Almost like it's saving the .BackupMod in side the module proper or something.
               
               

               

                     Modifié par pope_leo, 20 juin 2011 - 01:17 .
                     
                  

            

[Legacy_Thayan]

               New release problems, aye? '>

Sadly, I have to report a similiar situation. The problem was due to my own errors - but the compiler was compiling all my scripts without errors. So then, the change I was testing to a starting conditional script was not occurring. Even when I put in a simple debug line in the SC script saying "this script is firing" and did a full build on the module, the debug info didn't get sent when I tried testing it.

I eventually ended up going back to the default toolset .exe and compiler and found using that, there were a couple scripts that I had recently modified which had logic errors (like a parenthesis in the wrong spot, and so on). Once I fixed those and did a full build using the default toolset compiler, and then the old PrC compiler, my scripts worked as intended and the debug line fired as expected too.
               
               

               

                     Modifié par Thayan, 20 juin 2011 - 03:39 .
                     
                  

            

[Legacy_SkywingvL]

               Could you send me a copy of the scripts in question in their problematic state and all of their include dependencies?

Also, could you give building the scripts with the standalone compiler from the ASC distribution a shot? This will help us identify whether there is a problem with the toolset integration part or the compiler core.
               
               

               

                     Modifié par SkywingvL, 20 juin 2011 - 04:55 .
                     
                  

            

[Legacy_Lazarus Magni]

               Wow that's messed up, my virus soft ware show viruses in the file from the link virusman posted.
               
               

               

                     Modifié par Lazarus Magni, 21 juin 2011 - 07:06 .
                     
                  

            

[Legacy_virusman]

               Since it injects a DLL into nwtoolset process to modify its behavior, it's no wonder some paranoid AVs may give a false positive.
               
               

               

                     Modifié par virusman, 21 juin 2011 - 01:28 .
                     
                  

            

[Baaleos]

               Virus Software picks it up...
The author is called Virusman.....

HELLO!!!
WAKE UP AND SMELL THE COFFEE.....


Kidding.
Nothing from Virusman has ever set off my virus scanners. (YET).
               
               

               
            

[Legacy_FunkySwerve]

               AHA! It's as I always suspected. You play a long game, vman, building our trust with years of useful plugins, just so you can release upon an unsuspecting public a virus to turn us all into santa-hat-wearing-will o' wisps - doubtless part of your plans for word domination. Well, played, sir, well played.

Funky
               
               

               
            

[Baaleos]

               You know...
The amount of people that use nwnx, imagine the DDOS attack he could accomplish if he used nwnx to Zombie all the Servers using it. Lol

CIA - Tango Down!!

Virusman - The man behind LulzSec!!

(Any libelous statements above are meant in jest - Disclaimer)
               
               

               
            

[Legacy_Lazarus Magni]

               Well I am glad to hear it is not malicious, and just to be clear I was not accusing anyone of anything, just reporting what happened. I certainly am one of those who benifits from all the hard work from the nwnx team, and appreciate it very much! I got to say though, I was wondering why I woke up this morning with a santa hat on? Or was it a dunce cap?
               
               

               

                     Modifié par Lazarus Magni, 21 juin 2011 - 08:26 .
                     
                  

            

[Legacy_ShadowM]

               Just a thought on people who are having scripts not working after compile, I had similar problems with the other prc compiler that I found was fixed  when I took out the optimize script option. I do not know if this one has that in by default. Oh and if there another update version for NWN1 is it at the other link or is there another vault entry for just nwn1 version?
               
               

               

                     Modifié par ShadowM, 24 juin 2011 - 03:15 .
                     
                  

            

[Legacy_SkywingvL]

               The Advanced Script Compiler distribution supports NWN1 as well.

If you have a script that isn't working after compiling with the ASC or virusman's plugin, but compiles with the standard BioWare compiler (or silently fails to complete with the ASC or virusman's plugin), can you drop me a copy of the script and all its dependencies?

Unfortunately, if there is a problem here, so far there hasn't been sufficient actionable information to track it down.
               
               

               
            

[Legacy_leo_x]

               

SkywingvL wrote...

The Advanced Script Compiler distribution supports NWN1 as well.

If you have a script that isn't working after compiling with the ASC or virusman's plugin, but compiles with the standard BioWare compiler (or silently fails to complete with the ASC or virusman's plugin), can you drop me a copy of the script and all its dependencies?

Unfortunately, if there is a problem here, so far there hasn't been sufficient actionable information to track it down.

sorry for the delay, for my part, the issue was with my own setup, not your plugin / compiler.

thanks!
               
               

               
            

[Legacy_ShadowM]

               Here one that does not work when I run it through the toolset compiler. I clearing the actions because I want this conversation to start even in combat. When I compile it with the basic toolset or prc compiler it works, but when I run it through the update compiler toolset it does not fire in game.

object oTarget = GetPCSpeaker();
void main()
{

AssignCommand(oTarget,ClearAllActions(TRUE));
AssignCommand(oTarget,ActionStartConversation(oTarget,"player_guide", TRUE, FALSE));
}