Jump to content

Possible bug


Miloch

Recommended Posts

As described in this post, when doing a variable scan in DLTCEP, sometimes variables that contain a # will get recognised as LOCALS in the second instance they're used.

 

For example, DLTCEP reports this:

GLOBAL p#coran_complains is referenced only 1 times.
LOCALS coran_complains is referenced only 1 times.

When in fact the script has this:

IF
 ...
THEN
 RESPONSE #100
RealSetGlobalTimer("P#Coran_Complains","GLOBAL",TWO_DAYS)
SetGlobal("P#ComplainTimerStarted","GLOBAL",1)
END

IF
 RealGlobalTimerExpired("P#Coran_Complains","GLOBAL")
 ...

Link to comment

Yes, it is fully possible that it doesn't know all triggers/actions.

There is a huge table in the code which configures the behaviour.

So it is easy to flunk but also easy to fix.

 

I don't think it cannot handle #, i believe you use that other variable somewhere as well.

Link to comment
So it is easy to flunk but also easy to fix.
If it's easy to fix, would you mind doing so :help:? I'm just thinking it'd help the BG1NPC effort in the original post. This is the only tool I'm aware of that can scan variables like this, though maybe I'm overlooking features in other tools.
Link to comment

Archived

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

×
×
  • Create New...