Follow-up Comment #6, bug #21966 (project wesnoth):
well the reason seems to be that somewhere an impossible move was issured.
Which usualy causes an OOS.
Maybe you didn't read my original submission in a detail. The first problem
happened prior to the OOS:
- it looks until turn 3 of the green
Follow-up Comment #13, bug #21882 (project wesnoth):
@involution
I have corrected the part about modify_side
http://wiki.wesnoth.org/DirectActionsWML#.5Bmodify_side.5D not affecting the
defeat condition, that was intended to be added.
But why? Some people don't know lua, and would like to be
Follow-up Comment #7, bug #21966 (project wesnoth):
well its known that OOS error messages appear as soon as you use the currupted
data not in the moment when that data is created and thats where the actual
error happened.
If the is a too long [move] in the replay then stopping erarly is exactly
Follow-up Comment #8, bug #21966 (project wesnoth):
@Anonymous:
My save is from replays.wesnoth.org, and I think players didn't have when they
informed me about the problem.
It is also possile that ... this is related to your addon.
I checked all use of u.max_moves and manipulation with
Update of bug #21983 (project wesnoth):
Assigned to:None = fendrin
___
Follow-up Comment #2:
i was told that fabi is the one to edit teh default hotkeys preferences file.
So i assigned this
Follow-up Comment #9, bug #21966 (project wesnoth):
I will try to reconstruct what was happening, in my best knowledge:
I was not the host in the initial game.
The error occurred right when I moved the spearman that just got teleported.
I did not encounter any errors prior to that and the error
Follow-up Comment #10, bug #21966 (project wesnoth):
I will try to reconstruct what was happening, in my best knowledge:
I was not the host of the initial game.
The error occurred right when I moved the spearman that just got teleported.
I did not encounter any errors prior to that and the error
Follow-up Comment #11, bug #21966 (project wesnoth):
Blop, the game you reloaded (and that was not corrupted) was from which turn?
___
Reply to this item at:
http://gna.org/bugs/?21966
___
Follow-up Comment #12, bug #21966 (project wesnoth):
It was right after the error occurred (turn 4).
As the unit moved correctly for my side, the reload resolved the OOS.
I had only moved another one unit and had not yet recruited.
___
Update of bug #21746 (project wesnoth):
Status:None = Fixed
___
Follow-up Comment #2:
I think AI fixed the rest of them, I'm not sure. But they seem to work fine
now, so I'm marking
10 matches
Mail list logo
