READ FIRST: NeoLemmix Bugs & Suggestions Subforum Rules

[namida]

In order to keep this subforum useful and tidy, please observe the following rules:

1. One bug per topic, unless you're very sure they're closely related. The topics can be merged, or linked to each other, if need be.

2. Please put one of the following tags as appropriate at the start of your topic title, to make it clear what you're posting:
[BUG] Something that surely should work differently
[SUGGESTION] Improvements, additions, new features and the like
[DISCUSSION] If you're proposing a discussion around a new or existing feature / etc that isn't necesserially a suggestion on what to change

4. Please put one of the following tags as appropriate at the start of your topic title (including the brackets) to indicate what part of NeoLemmix the bug/suggestion relates to. If you're not entirely sure where the problem lies (for example, if it's a bug that only seems to come up during playtest mode, but might be a player problem nonetheless), just guess; it can always be corrected if you get it wrong. The tags are:
[PLAYER] For the NeoLemmix engine itself
[CONTENT] For any "official" content, like official styles, standard music, sound effects, ...
[EDITOR] For the NeoLemmix level editor

If the bug is for a release candidate version, please add [RC] to your topic title.

Bugs should only be reported for either the latest stable version, or the latest release candidate version. Bugs with experimentals should be reported, but these reports go in the experimental's release topic. To be very clear - this means, do not report bugs for old-formats NeoLemmix, or for the deprecated tools.

5. Mention in your topic what version of NeoLemmix or the editor you're getting the bug in. Despite the "report issues with stable version only" rule, this is useful if an issue doesn't get fixed right away and I come back to it later.

6. Try to give a brief description of the bug or suggestion in your topic title. If that's impossible (or you're not sure how to best word it), at least give a general idea of what it relates to. "OMG A BUG" is not helpful; "Nuke bug" at least points in the right direction; "Saved percentage higher than it should be if level is nuked" is best of all.

7. In all cases discussion on what should be done to fix the bug is welcome and highly encouraged. However, topics can and generally will be closed once the bug is fixed or the suggestion is implemented.

8. All topics should be created on the main Bugs & Suggestions board. NeoLemmix developers will move it to one of the sub-boards as and when appropriate.

9. Bugs / suggestions will generally be moved to the "Closed" subforum once an official release that fixes / implements them has been released.

[namida]

I have changed these rules to allow suggestions on this sub-forum. Please post all future suggestions here, rather than on the main board or via PM, if possible.

[namida]

I've dropped the whole "make a blank post, then reply with your comments" thing, as there's really no reason I can't just edit the original post and place the notes at the start of it, so all it really does is create inconvenience. (However, if you prefer to make the blank post, you're still welcome to.)

[namida]

I've amended rule 7 to request that people always mention the version number of the game / tool that they encounter bugs on, rather than "only if it's an experimental". This is important as from time to time, NeoLemmix or associated tools might get several updates rapidly, and so it can't be assumed that everyone reporting issues has the latest version (and even if they do, it's possible that I might have to leave the bug for now and come back to it later, at which point the version it occurred on won't be the latest anymore).

[namida]

Modified the above to reference that I've created sub-boards for the Player and Editor respectively, and that topics should still be created on the main board.

Also, I'd like to remind people to include the relevant tags - whether a topic is a bug, suggestion, etc; and whether it relates to the player, editor, etc - at the start of their topic titles.