widelands

Wood Gnome win conditions index field

Bug #1243082 reported by GunChleoc
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
widelands
Fix Released
Undecided
Unassigned
widelands build18-rc1

Bug Description

At the end of a Wood Gnome game, the player gets the message who has won. Then there is an additional message with a Lua error:

Lua Coroutine Failed

win_conditions:04_wood_gnome: 160: attempt to index field '?' (a nil value)

This script has a few more lines in my branch; it's the 4th line from the bottom:

  wl.game.report_result(points[i][1], 1, make_extra_data(points[i][1], wc_name, wc_version, {score=points[#points

Revision history for this message
SirVer (sirver) wrote :

Have you saved and reloaded this game?

Changed in widelands:
status: New → Incomplete
Revision history for this message
GunChleoc (gunchleoc) wrote :

No, it was a new game.

Revision history for this message
wl-zocker (wl-zocker) wrote :

I can confirm. I started a new game, sped it up, waited till the end. I got 12 messages ("The game will end in x minutes.") with the current state and another one with the final result.
At the same time (after four hours) I got the mentioned error message (in my news window):
[c:/data/bzr/widelands/trunk/src/scripting/scripting.h:42] [string "win-conditions:04_wood_gnome"]:153: attempt to index field '?' (a nil value). I have changed nothing in the script.

Changed in widelands:
status: Incomplete → Confirmed
Revision history for this message
SirVer (sirver) wrote :

Chees.... that code can never have worked before. How did that ever get committed? Fixed in r6816.

Changed in widelands:
status: Confirmed → Fix Committed
milestone: none → build18-rc1
Revision history for this message
SirVer (sirver) wrote :

Released in build-18 rc1.

Changed in widelands:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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