Jump to content

SetGlobalTimer Weidu problem


Red Carnelian

Recommended Posts

My debug file crops up with this message

 

[ds/tutu/crebaf/dstest.BAF] PARSE ERROR at line 1304 column 63-63

Near Text: )

[setGlobalTimer] argument [FOUR_MINUTES] not found in [GTimes.IDS]

 

 

due to this kind of bcs entry

 

SetGlobalTimer("PLAYER2","GLOBAL",20)

 

Now I've seen this kind of entry in in many other scripts so why is Weidu flagging it?

Link to comment

Unless it's changed recently, I'm showing:

IF
 Global("CE5","GLOBAL",0)
 Global("OMEN5","GLOBAL",5)
THEN
 RESPONSE #100
Wait(5)
ForceSpell(Myself,FIRE_DAM1)
Wait(5)
ForceSpell(Myself,FIRE_DAM1)
Wait(5)
ForceSpell(Myself,FIRE_DAM1)
Wait(5)
SetGlobal("CE5","GLOBAL",1)
SetGlobalTimer("CE5_DOOM","GLOBAL",20)
END

I don't know why it would try to convert "20" to "FOUR_MINUTES" either.

Link to comment
For some reason during development SetGlobalTimer had become SetGlobalTimer("CE5_DOOM","GLOBAL",FOUR_MINUTES) in my baf files.

 

This happens when you install the "Modder Pack" component of the G3 BG2 Fixpack and then decompile an existing script. I've experienced similar issues in the past.

 

The simplest solution is to remove the modified GTIMES.IDS from your override folder.

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...