I didn't go through much, but just got some obvious things for you:
Code:
sub EVENT_AGGRO { |
Code:
Sub EVENT_TIMER { |
Jolig that is working thanks a lot! What was wrong with it?
bad_captain, I see I had 4 starting brackets and 2 ending, but where would the other 2 brackets have gone? |
There's a reason people format code, because it is much more obvious when things are wrong. Compare your code to this:
Code:
Sub EVENT_TIMER |
This part:
Code:
Sub EVENT_TIMER { You're original posting was correct..the second one is wrong. Quote:
There could still be other issues, but this is how procedures should be wrapped. I don't know if perl let's you use single-line conditional statements. If it does, and that's what you're attempting to do, then the con checks shouldn't have the opening bracket after it. IF perl does let you, it should look like this. Otherwise you need both open and close brackets around any procedure or sub-procedure. Code:
Sub EVENT_TIMER { |
Here try this.
Also look at this: Quote:
Code:
sub EVENT_COMBAT { |
If you need additional help you can contact me at akaishigpg@gmail.com
|
as for your timer checks, when you are using a string, you should enclose it in quotations and use the eq operator (if the name of your timer is an integer, you don't need the quotations and you use == instead). it's also better practice to use elsif for when you only expect a single condition to be met, otherwise the script will continue to evaluate the rest of the conditions instead of stopping at the first one it sees. here's an example:
Code:
Sub EVENT_TIMER |
Quote:
|
Quote:
|
All times are GMT -4. The time now is 10:45 PM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.