TranslateCommonToLanguage toolset crash

[Legacy_ShadowM]

               

I been trying to use TranslateCommonToLanguage function from DMFI / my hr tool etc..

but when I use other than with the talking system for like just getting a translated string it throw a toolset error.  C0000420

 

Anyone else got this issue?

               
               

               
            

[Legacy_henesua]

               

I am currently making use of these string cyphers, and not running into trouble. But I did at one point before I started using NWNTX because I had exceeded the number of labels which the compiler allows. I don't know what that error code means, but wonder if it is a similar sort of problem.

               
               

               
            

[Legacy_ShadowM]

               

I am currently making use of these string cyphers, and not running into trouble. But I did at one point before I started using NWNTX because I had exceeded the number of labels which the compiler allows. I don't know what that error code means, but wonder if it is a similar sort of problem.

Thanks henesua, that kinda what I was thinking. I been adding so much into my hr base that I think I hit label or some other limit. I'm using nwntx too. I got around it by runing it through a ExecuteScript call, so all good. I have to spend one of my updates condensing and fine tuning the amounts I using so I have some breathing room still. I only got the error when I was running it through my spell router script also. If I just did it with a simple script call it worked fine.

               
               

               
            

[Legacy_FunkySwerve]

               

You're hitting the 'too many identifiers' compiler error. The solution is to use a compiler like Skywings (which is also in the NWNTX, now), which can handle more identifiers. SIMTools runs into the same problem if you include it in any scripts. It's one of the reasons I gave serious consideration to retrofitting out all the english-based string consts intended to make it more portable to other languages - the sheer number of consts makes the identifier count problematic when you include it in almost any other major module event script (which themselves are likely to have a fair number of identifiers).

 

Funky

               
               

               
            

[Legacy_ShadowM]

               

Thanks Funky for the information and link. Is there a fast way to get a total count of identifiers I have? I have to get around to cleaning house and doing some reorganizing.