Unknown variable realnumflames

Bug #1301608 reported by Orpheon
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Gang Garrison 2
Confirmed
Undecided
Unassigned

Bug Description

___________________________________________
ERROR in
action number 1
of Other Event: User Defined 2
for object Flamethrower:

Error in code at line 149:
                       for(i = 0; i < realnumflames; i += 1)
                                      ^
at position 37: Unknown variable realnumflames

Version: 2.7.2

No real context data was available, sorry. The code itself gets executed when a pyro extinguishes a teammate, and the variable is supposed to be in the Character namespace. It's not mentioned in the Create event though.

It does not consistently crash though, or at least I have not found out how to cause it to crash.

Revision history for this message
Thomas Crouse (tac20131) wrote :

To reproduce:
Start a server and leave host in spectate.
Start 3 other clients and connect to host.
Set client 1 to Infiltrator, set invisible, and move just outside spawn.
Set client 2 to same team Firebug, and move next to Infiltrator.
Set client 3 to other team Firebug, and move next to invisible enemy Infiltrator.
Ignite enemy Infiltrator using client 3 Firebug.
Extinguish Infiltrator using client 2 Firebug before burning is finished.
Host instance will produce the specified error.

Revision history for this message
Thomas Crouse (tac20131) wrote :

Guess technically I should have switched the steps for selecting a client 2 and 3 teams...

Why not initialize realnumflames on character create instead of the first draw step?

Changed in gg2:
status: New → Confirmed
Revision history for this message
Orpheon (alex-liebendorf) wrote :

Ah, that's what's causing it.
Realnumflames probably wasn't intended to be a persistent variable anyways, the extinguishing code should create its own temp variable.

Also this allows any 3 clients to crash servers, not sure how urgent fixing it would be.

description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.