Difference between revisions of "Known Bugs"

From BattleMaster Wiki
Jump to navigation Jump to search
(changed to use new template)
Line 7: Line 7:
 
==Major Bugs==
 
==Major Bugs==
  
* '''Rebellion Bug''' - Anyone rebelling will currently find themselves bumped to rogue immediately before the first turn of the rebellion. This causes the rebellion to fail. [[http://bugs.battlemaster.org/view.php?id=1526 Bug #1526]]
+
{{Kbug|Rebellion Bug|1526|Anyone rebelling will currently find themselves bumped to rogue immediately before the first turn of the rebellion. This causes the rebellion to fail.}}
* '''Secession Issues''' - When a city secedes, not everything is severed from it as it (seems like it) should be.  This results in some odd situations like being able to send messages to vassals who are members of an enemy realm, or being able to see the standing orders of an enemy realm's Duchy army. [[http://bugs.battlemaster.org/view.php?id=1448 Bug #1448]]
+
{{Kbug|Secession Issues|1448|When a city secedes, not everything is severed from it as it (seems like it) should be.  This results in some odd situations like being able to send messages to vassals who are members of an enemy realm, or being able to see the standing orders of an enemy realm's Duchy army.}}
 
 
 
==Minor Bugs==
 
==Minor Bugs==
  
* '''Appointment Bug''' - If a Council-member steps down and someone new needs to be appointed, the game will allow you to appoint immediately, but will throw a SQL error when you try, and not actually appoint them.  It goes away after an as-yet-undetermined number of turns.  Confirmed for General only (so far). [[http://bugs.battlemaster.org/view.php?id=1475 Bug #1475]]
+
{{Kbug|Appointment Bug|1475|If a Council-member steps down and someone new needs to be appointed, the game will allow you to appoint immediately, but will throw a SQL error when you try, and not actually appoint them.  It goes away after an as-yet-undetermined number of turns.  Confirmed for General only (so far). }}
  
 
=Not Really Bugs=
 
=Not Really Bugs=

Revision as of 22:14, 13 August 2006

This will provide a list, updated (hopefully) frequently, of known bugs affecting gameplay in a noticeable way. It should include major and minor bugs, as well as features that appear in the game, but are not implemented yet, and things that appear to be bugs, but are, in fact, not. If you know of something that is confirmed to be a bug--not just something that you think looks weird--or you find something that is not implemented or that seems like a bug, but isn't, please add it to the appropriate section.

Bugs

These are errors in the code, or in the database, that have a visible effect on the game to ordinary people playing. They will usually have at least one bugtracker entry associated with them.

Major Bugs

  • Rebellion Bug - Anyone rebelling will currently find themselves bumped to rogue immediately before the first turn of the rebellion. This causes the rebellion to fail. [Bug #1526]
  • Secession Issues - When a city secedes, not everything is severed from it as it (seems like it) should be. This results in some odd situations like being able to send messages to vassals who are members of an enemy realm, or being able to see the standing orders of an enemy realm's Duchy army. [Bug #1448]

Minor Bugs

  • Appointment Bug - If a Council-member steps down and someone new needs to be appointed, the game will allow you to appoint immediately, but will throw a SQL error when you try, and not actually appoint them. It goes away after an as-yet-undetermined number of turns. Confirmed for General only (so far). [Bug #1475]

Not Really Bugs

The first category here is things that are sort of bugs, but not exactly: they're features that Tom has planned, and has put some reference to in-game (like a link), but hasn't actually finished the code for. The second category is for things that appear to be bugs, but are, in fact, the expected behaviour of the code. That doesn't mean that it's sensible from a real-life perspective, or even that it's the way it'll always be--just that it's the way the code, in its current form, is expected to work.

Unimplemented Features

  • Shadow Government - A Banker option; no ETA on implementation

Apparent Bugs

  • Combat Confusion - There are times when a battle seems like it should happen, but doesn't, or people come out on odd sides in a battle. This actually deserves its own separate article, which will be at Battle/Choosing Sides.