Macro | statusHANDLE instead of statusName
Moderators: Moderators, Developers
Re: [need help] With my status check macro
Try this...
Reason: As stated in the FAQ
Code: Select all
automacro buffs {
status not Steamed Scorpion
inventory "Jellopy" > 0 #bring along jellopy
run-once 1 #or exclusive 1
call buff
}
macro buff {
pause 1
do respawn
pause 1
do move 149 91
do talknpc 146 93 c c c c c c r0 c c c n
release buffs
}
Reason: As stated in the FAQ
Re: [need help] With my status check macro
I tried it, and.. still not working.ezza wrote:Try this...Code: Select all
automacro buffs { status not Steamed Scorpion inventory "Jellopy" > 0 #bring along jellopy run-once 1 #or exclusive 1 call buff } macro buff { pause 1 do respawn pause 1 do move 149 91 do talknpc 146 93 c c c c c c r0 c c c n release buffs }
Reason: As stated in the FAQ
by the way.. Thank you.
-
- Super Moderators
- Posts: 801
- Joined: 06 May 2008, 12:47
- Noob?: No
Re: [need help] With my status check macro
Are you using latest OpenKore svn and latest macro plugin svn?
please, just don't assume so but test it with the following commands:
- for openkore:
- for the macro plugin:
post your output here please, thanks.
please, just don't assume so but test it with the following commands:
- for openkore:
Code: Select all
version
Code: Select all
macro version
One ST0 to rule them all? One PE viewer to find them!
One ST_kRO to bring them all and in the darkness bind them...
Mount Doom awaits us, fellowship of OpenKore!
One ST_kRO to bring them all and in the darkness bind them...
Mount Doom awaits us, fellowship of OpenKore!
Re: [need help] With my status check macro
here you are :Technology wrote:Are you using latest OpenKore svn and latest macro plugin svn?
please, just don't assume so but test it with the following commands:
- for openkore:- for the macro plugin:Code: Select all
version
post your output here please, thanks.Code: Select all
macro version
-
- Noob
- Posts: 2
- Joined: 11 Aug 2010, 14:33
- Noob?: No
Re: [need help] With my status check macro
I got the same problem in macro trigger.
When my status is Blessing, i used an automacro to check it.
But it did not triggered.
So i used an another automacro to check my status.
It appeared my status was EFST_BLESSING
Why my status name is different in macro?
When my status is Blessing, i used an automacro to check it.
Code: Select all
automacro HAHA {
status Blessing
run-once 1
call {
log HAHAHAHA
}
}
So i used an another automacro to check my status.
Code: Select all
automacro StatusCheck {
run-once 1
call {
log $.status
}
}
Why my status name is different in macro?
Re: [need help] With my status check macro
version
*** OpenKore what-will-become-2.1 ( r7443 ) - Custom Ragnarok Online client ***
*** http://www.openkore.com/ ***
macro version
macro plugin version 2.0.3-svn
macro.pl 6744
Macro::Automacro 6760
Macro::Script 6782
Macro::Parser 6759
Macro::Utilities 6812
Macro::Data 6753
*** OpenKore what-will-become-2.1 ( r7443 ) - Custom Ragnarok Online client ***
*** http://www.openkore.com/ ***
macro version
macro plugin version 2.0.3-svn
macro.pl 6744
Macro::Automacro 6760
Macro::Script 6782
Macro::Parser 6759
Macro::Utilities 6812
Macro::Data 6753
-
- Super Moderators
- Posts: 801
- Joined: 06 May 2008, 12:47
- Noob?: No
Re: [need help] With my status check macro
yep, seems like the macro plugin has got a bug.Melchizedek wrote:It appeared my status was EFST_BLESSING
The EFST_BLESSING is actually a statusHANDLE, not a statusName.
Kore got updated to support and use these handles internally.
It seems like the macro plugin wasn't updated accordingly.
So thank you, the bug is confirmed and I'm moving this to the appropriate section.
One ST0 to rule them all? One PE viewer to find them!
One ST_kRO to bring them all and in the darkness bind them...
Mount Doom awaits us, fellowship of OpenKore!
One ST_kRO to bring them all and in the darkness bind them...
Mount Doom awaits us, fellowship of OpenKore!
-
- Developers
- Posts: 1798
- Joined: 05 Dec 2008, 05:42
- Noob?: Yes
Re: [need help] With my status check macro
Fixed in r7480.Technology wrote:The EFST_BLESSING is actually a statusHANDLE, not a statusName.Melchizedek wrote:It appeared my status was EFST_BLESSING
(Statuses with no defined names will still be displayed like handles here.)
-
- Noob
- Posts: 4
- Joined: 25 Nov 2010, 14:35
- Noob?: Yes
Re: Macro | statusHANDLE instead of statusName
i have the latest openkore svn(to be 2.1) and macro version is 2.0.3(svn) and im also getting the same problem..bot wont read the status..and u said it was only handle, not status name right ? but im able to use skills perfectly using wat is listed in skill_id_handle =/
and im also having one problem..im not able to see ANYTHING under my status..like when i type 'S' in console it show nothing but 'Falcon' in statuses..even though i made macro for the bot to use healer+buffer and its both blessed and inc agi...any light on that plz ?
and im also having one problem..im not able to see ANYTHING under my status..like when i type 'S' in console it show nothing but 'Falcon' in statuses..even though i made macro for the bot to use healer+buffer and its both blessed and inc agi...any light on that plz ?