ToME 3 bug reports should now be done at http://bugs.t-o-m-e.net/

When making a report on the bug tracker, please make sure you use the right project (there is one for T-Engine and then one for each module), thanks.

NOTICE: July 9, 2007 - The bug tracker is now open for 3rd party module developers. If you'd like to use the ToME bug tracker for your ToME 3 module, make sure you're a registered bug tracker user and add a note to the BugTracker wiki page with your tracker username and the name of the module you'd like added. ToME 2 issues should still go on this page and not on the new bug tracker.





The following sections are deprecated and only kept as history


Add new bugs by editing this page and adding them to the bottom of the list. Follow the format of the other bugs in the list, please. Developers will move fixed or otherwise resolved bugs to the resolved section of the list.

Only put a summary of the bug on this page. Write detailed information you have for us on the BugReportN page and tell us about it there. Mark the bug as a spoiler if the detailed information contains one.

Important: Do NOT write the full bug description onto this page. Also, never assume the reader of the full Bug Report page has read this page first.

And please, don't bother to recycle bug numbers. There are plenty to go around. And don't worry about getting it in perfect sequential order. If things get messy, say, around the 650s... just jump ahead to 700. We don't want that to be an impediment to reporting bugs.

NOTICE: Please do NOT report bugs about ToME, the module, when testing ToME 3 alphas. Engine bugs only, please.

NOTE: An easy way to find an available number for your bug report is to change the address in your browser's URL/Location bar manually to read

where NNN is a bug number which you think might be free. If the number you have chosen isn't free you can simply try again with NNN+1. When you have found a free page, write your bug report, and add a link to it on this page.

Warning: Many of the links on this page lead to spoily information. Even if the original bug report is not spoily, followup discussion can become so. You have been warned.

On Modules: Some module authors keep bug reports here. Others use their Modules page. Check with the Modules page to see what the preference is.



ToME 2 Bugs

New Bug Reports

In-game typographical errors

This section should be used to report in-game typos, spelling or grammatical errors.

Alchemy Bugs

Tome 3 Bugs (Section Deprecated!)

Module Bugs

Annals of Ea

Gerband

Gerband Quest

Hobbit

Narnia

Scroll

Theme

Furymod

Website bugs

Resolved Bugs

ToME 2

(If you think an older resolved bug is missing, see /Old_resolved_bugs)

ToME 3

Modules

Annals of Ea

Gerband

Gerband Quest

Theme

Website Bugs

Chatter

/Old_Chatter has been moved to make this page easier to edit.

Is it feasible to have a search facility which only searches Bug pages? This list is getting quite long and I want to avoid posting duplicate bugs... By the way, is there a way to mark bugs as duplicates? 327 is a duplicate of 37 -- JulesBean

Bandobras: I see 2.3.2 has just been released. Great. But it seems, the fixes included with bug reports above did not make it into 2.3.2. In particular, the fix for the awful dark arena bug (see http://www.killerbunnies.org/angband/). :< At least, I couldn't find them in the changes.txt file. Could someone please confirm?

ReenenLaurie: Naming the pages according to the heading is a good idea, as then you don't have to go up and down to see which number to use. Like ThemeBugX. AFAIK you cannot start a page name with a number (just write it down in camelcase). So 3.0.0's bugs could look like TEngine300_BugX. It is just a suggestion.


NeilStevens: ToME 3 alpha bug report removed, because we're not ready for beta testing yet. Sorry.

NotsoSwift: (My first time. Hope I'm doing this right. The directions said "the bottom of the list", so that's what I did)...Theme 1.20 over ToME 2.3.3: I just found two artifacts that I had mathomed under an earlier version of Theme (1.14): Faramir and Girion. When I went back to the museum (the one in Lothlorien), the entries for these items were blank--as were a number of other entries--and the ID descriptions were screwed up, saying they grant the ability to spit acid, or somesuch. A few non-blank entries also appeared screwed up. e.g. "an amulet of &Necklace~". My guess is that the other entries that were blank are going to reappear in a dungeon at some point as well. Don't know if reporting this is apropos since the cause may possibly be attributable to changing Theme versions in the middle of a character.

To: NotsoSwift - the artifact list was compacted in Theme 2.3.3 - probably to make it easier for the author to see how many open slots were left for artifacts. Certain artifacts had their numbers changed; I believe this is, also, the reason for the Theme bug about Trone's coat.

TobiasParker: Could someone (with more patience than i) divide this page up so that each bug report section (Tome 2, Tome 3, Mods) is it's own subpage. I just tried to add some bugs and it took me 15 minutes just to find the right section and the first time i accidently put it under Resolved bugs. Maybe i am just dumb but it seems it could be more efficient.

ReenenLaurie: Yes, this page is getting too large, but I think moving/rearranging them down is quite a large task.

NeilStevens: The situation is being resolved by the developers. In fact, I'd better get in gear and finish this question before we release the first engine beta.

ShrikeDeCil There's a lot of of T3 bugs that still happen that are not marked 'alpha12/14' and thus haven't made the transition yet. I was going to weed through the whole list of T3 bugs here and plug ones that still happen into the new bug tracker. But I'd like to make notations _here_ of what exactly happened to some of these bugs. Some of the bugs are going to be harder to reproduce than others, for instance. This whole section is deprecated, so I don't think adding 'MOVED' or 'IRREPRODUCIBLE' or 'NOTMACOSX' or whatever should be too offensive. Example above for just the first couple of T3 bugs. Reasonable? I wanted to ask before hacking this page too much, it is pretty unwieldy already. (Witness new bug tracker, heartfelt thanks much :D

EricStevens: Sounds good to me. I moved some of the newer bugs, but I really didn't have the time to look at all of them. I appreciate the help.


CategoryCategory

BugReports (last edited 2010-01-01 21:57:13 by localhost)