See: http://forums.openkore.com/viewtopic.php?f=36&t=18450
This is simply unexcusable; both that such a bug persisted for ninety (90) months unpatched, and that none of the thousands of kore users brought up the problem sooner, so that it could be patched by a developer.
If I can stumble upon a crashable bug so easily, then surely there are many more the rest of you have found.
And, if they're triggered by a command a user types and executes, they're normally much easier to narrow down and patch up.
It's fun too, trying to make a command crash the whole program. Okay, it's annoying as hell when your bot won't work 'cause a simple command crashed it.
Take the 5-10 minutes to report the problem, so it can be fixed instead of wearing down your patience. No user-entered command should EVER crash kore. Let's give kore a good shakedown so that it's more stable for you, and everyone.
I'll bet that the rest of you can find 6 crashes before I find another one myself. Beat me to finding a bug that crashes core... and we all win for the effort.
Please do not put bug reports in this thread, make up a clear post in the Bug Reports sub-forum.
- List the revision you're using in the thread title. A title like "r8320: Crash with 'foo' command" will help grab our attention. (Use "version" in the console of kore, and state the (r####) revision number it outputs)
- Describe in a simple set of steps what you did to cause the crash. Can you repeat your steps, and get the same crash? Repeatable steps help make it easier for a Tester to check the problem, and/or a Developer to code a fix for it.
- Check if you have an errors.txt generated from your crash -- paste it in, and surround it with a "code" or "quote" block tags. All that gibberish in there helps the Devs figure out what part of the code caused the error, right down to the line numbers.
- Remember to do that "version" command in kore, and state in the title which revision number you're using. Seriously now, it makes the errors.txt make sense to the other Developers.
