Difference between revisions of "Ogre:FAQ"
m (→New users & Install) |
(→New users & Install) |
||
Line 3: | Line 3: | ||
==New users & Install== | ==New users & Install== | ||
What do I do first?<br> | What do I do first?<br> | ||
− | + | :Check the how to obtain a [[ObtainingASubscription|subscription]] page. | |
I paid you now what?<br> | I paid you now what?<br> | ||
Revision as of 18:21, 13 November 2012
FAQ and Help
Contents
General
New users & Install
What do I do first?
- Check the how to obtain a subscription page.
I paid you now what?
Other general stuff
HowTo: Have ISXOgre automatically load.
HowTo: Connect computers via uplink.
OgreBot
Internal cast order of the bot. (Which tab executes when)
OgreCraft
It woln't work
Problem: The bot is missing a spell
Problem: The bot stops casting for no reason
Problem: I need to patch again because something is missing
I NEED HELP! What to do?
Please follow these rules, otherwise you will probably just get linked this page to read prior to being helped.
- If you get an error message, READ THE ERROR MESSAGE. Each error message is manually typed out for that specific scenario.
- If you get an error message WHILE following a walkthrough, recheck to make sure you didn't miss any steps.
- When asking for help with an error message, copy and paste the EXACT error message. This may sound harsh, but my custom error message are much more useful than your opinion of what isn't working. If you knew what wasn't working, you'd just fix it yourself. How to copy from the console.
- Give FACTS over opinions.
- I was doing _____, when I got error message <copy paste error message>.
- When I type ogre < command > I get error message <copy paste error message>
- I was doing _____, when I got error message <copy paste error message>.
- Try to help yourself. Do a quick search/scan the wiki (FAQ and Help section) to see if it's a common problem you are having and how to fix it.
- Keep in mind, you are asking for help. Be respect to those trying to help you. Once you start insulting people trying to help you, the help stops very quickly.
- If you get an error message, READ THE ERROR MESSAGE. Each error message is manually typed out for that specific scenario.
Here's a little list of things to avoid doing, since they don't really help.
- Asking: "Anyone there?", or "Kannkor, you there?"
- Just ask the question, if someone is there, they will answer it. There are times when I'm doing other things, and when I see a message, I'll flip to it, :**but if it simply asks "Are you there?", I'll probably ignore it because I'm walking away again, when I could have answered it if you asked the question.
- Your opinion on subjects/topics where you aren't an expert. It absolutely drives me and many others crazy, when people start giving bad advice because they want to hear themself talk.
- I can assure you, I understand the basics of how to program/script with lavishscript. You don't need to make a suggestion, and tell me how easy it would be. If it's that easy, feel free to do it and send it to me and I'll include it.
- I can assure you, I understand the basics of how to program/script with lavishscript. You don't need to make a suggestion, and tell me how easy it would be. If it's that easy, feel free to do it and send it to me and I'll include it.
- Asking: "Anyone there?", or "Kannkor, you there?"
Related, here is a very good read about asking questions. http://catb.org/~esr/faqs/smart-questions.html
If you can't find the answer, you can find contact information here.
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.