• Developers Corner
• Development Bugs

NeilStevens: This page is solely for developer bookkeeping. All users should record issues on the BugReports page instead.

Issues

• DevBugReport1 (3.0.0): flag_remove() memory trampling bug

• DevBugReport2 (3.0.0): Flags with string values don't work in item and ego definitions

• DevBugReport3 (3.0.0): Trapkit obj not saved when set as trap

Chatter

NeilStevens: I don't think we should create a second bug archive. How are we going to keep the bug numbers straight? Check both pages?

Or if we use a different namespace for 3.0 bugs now, what will we do when 3.0 is released? Any bugs that remain will leave us stuck with two bug report namespaces forever.

So if nobody objects, I'll delete this page.

Besides, for its purpose, the name of this page is inaccurate. ToME 3.0.0 isn't out. If it were out, then the users *would* be testing it for us. It's only the current ToME 3 development, before ToME 3.0.0, that is developer-only.

DarkGod: then rename it to Development Version Bugs, but it sounds logical to have a repository for the devs to put and peek bugs into.

NeilStevens: Doesn't it just duplicate the TODO list then, if developers use it to list things they intend to fix?

DarkGod: TODO is more for the things to .. well .. do, while this is more for the things to fix

NeilStevens: Alright, renaming this page to Development Bugs then.