View Issue Details

IDProjectCategoryView StatusLast Update
0000401FSSCPgameplaypublic2005-05-12 02:54
Reporterkarajorma Assigned ToGoober5000  
PrioritynormalSeverityfeatureReproducibilityalways
Status resolvedResolutionfixed 
Summary0000401: Can't use variables in repeating events
DescriptionWhen using the $VariableName option in a message the variable is resolved into a string the first time the event is called. If the message is called a second time the variable is not resolved and whatever was the value the first time is used.
Additional Information(Press N to check this in the mission provided. The first message is sent, the second variable is altered and then a sceond message is sent to prove this. Finally the first message is sent again. If the check is carried out properly messages 2 & 3 should be the same. If the variable is not being resolved a second time messages 1 & 3 will be the same).
TagsNo tags attached.

Activities

2005-05-01 20:09

 

string.fs2 (10,181 bytes)

phreak

2005-05-02 22:20

developer   ~0002311

Assigned to G5K.

Goober5000

2005-05-11 07:04

administrator   ~0002342

This should now be fixed.

Goober5000

2005-05-11 07:35

administrator   ~0002343

@#$%@#%!!!

Okay, there are several different ways to solve this. The original way was to permanently write the variable into the message. The way I have it right now is that the message reflects the value of the variable at the time it appears on the screen.

Unfortunately, I think the variable translation must be done a third way... the message must reflect the value of the variable at the time the message is queued. This is distinctly different from either 1) or 2) and about five times harder than either. So it might be awhile before this is properly fixed.

Goober5000

2005-05-12 02:54

administrator   ~0002354

Okay. Fixed, finally.

Issue History

Date Modified Username Field Change
2005-05-01 20:09 karajorma New Issue
2005-05-01 20:09 karajorma File Added: string.fs2
2005-05-02 22:20 phreak Note Added: 0002311
2005-05-02 22:20 phreak Assigned To => Goober5000
2005-05-02 22:20 phreak Status new => assigned
2005-05-11 07:04 Goober5000 Status assigned => resolved
2005-05-11 07:04 Goober5000 Resolution open => fixed
2005-05-11 07:04 Goober5000 Note Added: 0002342
2005-05-11 07:35 Goober5000 Status resolved => feedback
2005-05-11 07:35 Goober5000 Resolution fixed => reopened
2005-05-11 07:35 Goober5000 Note Added: 0002343
2005-05-11 08:06 Goober5000 Status feedback => assigned
2005-05-12 02:54 Goober5000 Status assigned => resolved
2005-05-12 02:54 Goober5000 Resolution reopened => fixed
2005-05-12 02:54 Goober5000 Note Added: 0002354