[Wesnoth-bugs] [bug #14429] Chasm/castle transition problem

URL: Summary: Chasm/castle transition problem Project: Battle for Wesnoth Submitted by: luther11 Submitted on: Friday 10/02/2009 at 18:23 Category: Bug Severity: 3 - Normal

[Wesnoth-bugs] [bug #15037] Tutorial Part II - fatal error

Follow-up Comment #7, bug #15037 (project wesnoth): It would seem that the MOVE macro does not reliably take away MP from the units. Turn 1 goes fine, but in turn 2, Dumbo, the orcish grunt, runs onto the bridge, like he's supposed to, but then comes back to attack in the same turn. The other orc

[Wesnoth-bugs] [bug #15037] Tutorial Part II - fatal error

Additional Item Attachment, bug #15037 (project wesnoth): File name: Wesnoth_Tutorial_Part_II-Auto-Save4.gz Size:38 KB ___ Reply to this item at: ___ Message s

[Wesnoth-bugs] [bug #15037] Tutorial Part II - fatal error

Follow-up Comment #9, bug #15037 (project wesnoth): Sorry, my mistake. I was using 1.7.11. If I had clicked over one more revision, I would've seen that shadowmaster fixed this in reference to bug #14926, which I believe this bug duplicates. I'm not done downloading the SVN checkout, but you seem

[Wesnoth-bugs] [patch #1477] [gold] should give an error when 'side' is not a number

URL: Summary: [gold] should give an error when 'side' is not a number Project: Battle for Wesnoth Submitted by: luther11 Submitted on: Monday 02/22/2010 at 04:36 Priority: 5 - Normal

[Wesnoth-bugs] [patch #1477] [gold] should give an error when 'side' is not a number

Additional Item Attachment, patch #1477 (project wesnoth): File name: gold1.patchSize:1 KB File name: test1.tar.bz2 Size:0 KB ___ Reply to this item at: ___

[Wesnoth-bugs] [patch #1477] [gold] should give an error when 'side' is not a number

Follow-up Comment #2, patch #1477 (project wesnoth): That's easy enough to fix. In gold1.patch, I set the default value before the error check. ___ Reply to this item at: ___

[Wesnoth-bugs] [bug #15349] can't replace map edge terrain

Follow-up Comment #2, bug #15349 (project wesnoth): Doesn't this violate the feature freeze? As a use case, my TCG Era has a feature where it has to find the size of the largest castle on the map. When counting tiles, it would be very bad to count those outside the playing field. Granted, it's

[Wesnoth-bugs] [bug #15530] Mandatory wml missing yet unchecked for

URL: Summary: Mandatory wml missing yet unchecked for Project: Battle for Wesnoth Submitted by: luther11 Submitted on: Thursday 03/04/2010 at 04:58 Category: Bug Severity: 3 -

[Wesnoth-bugs] [bug #15349] can't replace map edge terrain

Follow-up Comment #3, bug #15349 (project wesnoth): Why was this bug closed? Did no one see my previous comment? I need a definite decision on the feature freeze issue, because this bugfix breaks compatibility, and it affects a critical piece of info on the wiki (http://wiki.wesnoth.org/Internal

[Wesnoth-bugs] [bug #15349] can't replace map edge terrain

Follow-up Comment #5, bug #15349 (project wesnoth): BTW, let me know if I need to file a separate bug report. "outside the playing field": I mean border hexes. Tiles on the edge that the units can't reach. If you tested the TCG Era, I have to point out that a keep tile has to be on the border f

[Wesnoth-bugs] [bug #15349] can't replace map edge terrain

Follow-up Comment #6, bug #15349 (project wesnoth): I apologize for that 2p map there. When I click on the file name to confirm it's the right one, my browser just opens a new "File Upload" window. (file #8454) ___ Additional Item Attachme

[Wesnoth-bugs] [bug #18455] False warning: "Unknown attribute 'color_lock' discarded"

URL: Summary: False warning: "Unknown attribute 'color_lock' discarded" Project: Battle for Wesnoth Submitted by: luther11 Submitted on: Fri 05 Aug 2011 08:13:51 AM GMT Category: Bug

[Wesnoth-bugs] [bug #18455] False warning: "Unknown attribute 'color_lock' discarded"

Follow-up Comment #1, bug #18455 (project wesnoth): After compiling with build=debug and doing a backtrace, I finally found the source of the problem. In src/gamestatus.cpp, around line 899, add "color_lock" to that list of strings. I tested this, and it seems to solve the problem. _

[Wesnoth-bugs] [bug #18966] helper.rand is unusable

URL: Summary: helper.rand is unusable Project: Battle for Wesnoth Submitted by: luther11 Submitted on: Thu Nov 10 19:36:53 2011 Category: Bug Severity: 3 - Normal

[Wesnoth-bugs] [bug #19402] Upgrade to Lua 5.2

URL: Summary: Upgrade to Lua 5.2 Project: Battle for Wesnoth Submitted by: luther11 Submitted on: Fri 03 Feb 2012 05:00:46 PM GMT Category: Feature Request Severity: 1 - Wish

[Wesnoth-bugs] [bug #19402] Upgrade to Lua 5.2

Follow-up Comment #2, bug #19402 (project wesnoth): Is it bad that they made some changes to it? In my experience, changes to a free programming language are generally done for a very good reason, and they lead to the users' code being simpler and cleaner. I can't promise anything, but if I find