Report bugs and typos here.

[zelazko]

There is a syntax error in the FW0511 baf

 

IF
Global("GV#CORPSExists","%DurlagsTower_D1%",0)
THEN
RESPONSE #100
SetGlobal("GV#CORPSExists","%DurlagsTower_D1%",1)
CreateCreature("gv#corps",[1660.1430],0)
Continue()
END

 

On my playthrough experience it caused substantial lag until I 'fixed' by changing %Durla value into GLOBAL

 

Spoiler

IF
Global("GV#CORPSExists","GLOBAL",0)
THEN
RESPONSE #100
SetGlobal("GV#CORPSExists","GLOBAL",1)
CreateCreature("gv#corps",[1660.1430],0)
Continue()
END

 

[jastey]

I'd first check whether the file in question was compiled using EVALUATE BUFFER so the "%DurlagsTower_D1%" was actually translated to the area code (and the variable was actually set).

Or, why would an area variable cause a lagging?

[Graion Dilach]

Yeah, the EVAL is missing from the BGT/BGEE/EET path and is only listed at the Tutu path. It lags because it always runs, I guess.

[Connelly]

Easy enough to find the lines and finish them. Would there be any way to fix it in a running game?

[jastey]

You could open the script in NI and edit it accordingly.

[Connelly]

Ah, right. I had read the whole thing as the EVAL being the correct fix pre install and not Zelasko's global. Thanks.

[jastey]

32 minutes ago, Connelly said:

I had read the whole thing as the EVAL being the correct fix pre install and not Zelasko's global. Thanks.

What happens without the EVAL during compilation is that the installer writes "%DurlagsTower_D1%" as the variable type. Since this doesn't make sense (type not defined), "no" variable is set and the script starts looping.

I'd suggest for a game that was already started, replacing it with "MYAREA", that should do the trick, i.e.

IF
Global("GV#CORPSExists","MYAREA",0)
THEN
RESPONSE #100
SetGlobal("GV#CORPSExists","MYAREA",1)
CreateCreature("gv#corps",[1660.1430],0)
Continue()
END