Kannkor
Ogre
It's expansion time again! Few reminders for everyone, and a feature request/bug thread all in one!
Reminders
DO NOT SUBMIT ANY REQUESTS WITH BETA INFORMATION. I want live data only.
Feature Requests
There are good feature requests, and bad feature requests. Let me try to explain what makes them good and bad. I don't play all that many classes, so being vague, or giving me minimal information, is a bad feature request. Giving me the full details, and mechanics, is a good feature request.
If you submit a bad feature request, what happens? It means I need to do research on that class/ability, so it gets pushed to the BOTTOM of the list. I'm going to cherry pick the easy to implement ones first.
If you submit a good feature requeset, what happens? It will probably be at the top (or near the top) of the feature request section. Keep in mind, features/bugs that affect more people, will almost always be completed first. Example: Something that affects all priests would be implemented before a feature specific to rangers.
Example of a bad feature request:
Please add support for Paladin new ability.
Remember - I don't play all the classes. I have no idea what this new ability is, how it works, or what you want from it. So I would need to do the research to see how it works. You didn't even take the time to tell me the ability, or where it comes from.
Example of a GOOD feature request:
Paladin new ability: Paper Tank. New presitage line, end ability on left. When a block happens, they get the ability to cast 'OMFG_I_Didn't_Die'. It shows up in the maintained window and you get a message with 'Use your new ability omg omg'.
This means, I can borrow a friends pally, spec it, and go do 1 fight, and I'll have all the information I need.
Bugs
When submitting a bug, be as specific as possible. Try to walk me through how to reproduce it also.
Example of a bad bug report:
New ability in CAs doesn't work.
What I'll do, is go target a training dummy. If I kill it, then I'll close your bug report and assume it's on your end. Since the only test I have, is checking if 'some random' CA works or not.
Example of a good bug report:
Brigand new presitage 'Pokem From Behind' - 3rd down on right side doesn't work in CAs. The bot just skips it.
This gives me how to get the ability, and I can go test it.
In the end, make my life easier, and I'll try to complete your requests.
The same holds true for crafting requests, please be as specific as possible.
Reminders
- If you get any new abilities, in order for OgreBot to read them, you must do a: ogre spell in the console. Do not zone, or engage in combat while it's running. Once it is completed, reload the bot and your new abilities should appear in the list.
DO NOT SUBMIT ANY REQUESTS WITH BETA INFORMATION. I want live data only.
Feature Requests
There are good feature requests, and bad feature requests. Let me try to explain what makes them good and bad. I don't play all that many classes, so being vague, or giving me minimal information, is a bad feature request. Giving me the full details, and mechanics, is a good feature request.
If you submit a bad feature request, what happens? It means I need to do research on that class/ability, so it gets pushed to the BOTTOM of the list. I'm going to cherry pick the easy to implement ones first.
If you submit a good feature requeset, what happens? It will probably be at the top (or near the top) of the feature request section. Keep in mind, features/bugs that affect more people, will almost always be completed first. Example: Something that affects all priests would be implemented before a feature specific to rangers.
Example of a bad feature request:
Please add support for Paladin new ability.
Remember - I don't play all the classes. I have no idea what this new ability is, how it works, or what you want from it. So I would need to do the research to see how it works. You didn't even take the time to tell me the ability, or where it comes from.
Example of a GOOD feature request:
Paladin new ability: Paper Tank. New presitage line, end ability on left. When a block happens, they get the ability to cast 'OMFG_I_Didn't_Die'. It shows up in the maintained window and you get a message with 'Use your new ability omg omg'.
This means, I can borrow a friends pally, spec it, and go do 1 fight, and I'll have all the information I need.
Bugs
When submitting a bug, be as specific as possible. Try to walk me through how to reproduce it also.
Example of a bad bug report:
New ability in CAs doesn't work.
What I'll do, is go target a training dummy. If I kill it, then I'll close your bug report and assume it's on your end. Since the only test I have, is checking if 'some random' CA works or not.
Example of a good bug report:
Brigand new presitage 'Pokem From Behind' - 3rd down on right side doesn't work in CAs. The bot just skips it.
This gives me how to get the ability, and I can go test it.
In the end, make my life easier, and I'll try to complete your requests.
The same holds true for crafting requests, please be as specific as possible.