• You've discovered RedGuides, an EverQuest multi-boxing and scripting community 🧙‍♀️⚙️. We want you to play several EQ characters at once, come join us and say hello! 👋

  • A TLP without truebox has thawed (Very Vanilla ready)
    Frostreaver

Problem - Bug maybe ? just happened tonight when i loged on ?

Status
Not open for further replies.

Chanticleer

yells at clouds
Creator
Joined
Dec 14, 2010
RedCents
189¢
this is the error im getting with /mac kissassist pullertank



Rich (BB code):
kissassist.mac@1463 (CheckCasting(int CCtime): /delay 5
kissassist.mac@1403 (Castwhat(string castwhat, int castTarget.id,String sentfrom)): /call checkcasting 30
kissassist.mac@1071 (CombatCast: /castWhat "${DPS[${i}]}" ${DPSTarget.id}DPS
kissassist.mac@948 (Combat): /if (${DPSOn}&& (!${Role.Equal[puller]} || !${ChainPull})) /cast Combatcast
Kissassist.mac@676 (CheckforCombat(int SkipCombat, string Fromwhere)): /call combat
kissassist.mac@660 (Main): /call checkForcombat 0 Mainloop
 
What is the actual error?. Its the line that appears above this stuff.

/mq2log
/mlog on
and post the error text from the log.
 
will post soon as I get home from work -

- - - Updated - - -

DoCommand- Couldn't Parse "1"

- - - Updated - - -

Rich (BB code):
[2015/04/17 07:34:44] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:44] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:44] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:45] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:45] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:45] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:45] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:46] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:46] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:46] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:46] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:47] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:47] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:47] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:48] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:48] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:48] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:48] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:49] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:49] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:49] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:49] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:50] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:50] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:50] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:51] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:51] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:51] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:51] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:52] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:52] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:52] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:52] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:53] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:53] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:53] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:53] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:54] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:54] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:54] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:54] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:55] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:55] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:55] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:56] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:56] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:56] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:56] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:57] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:57] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:57] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:57] Cannot end a macro when one isn't running.

[2015/04/17 07:34:57] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:58] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:58] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:58] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:58] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:59] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:59] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:59] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:59] DoCommand - Couldn't parse '1'

[2015/04/17 07:35:00] DoCommand - Couldn't parse '1'

[2015/04/17 07:35:00] DoCommand - Couldn't parse '1'
 
Sounds like one of the holies has an error. Might have to disable them one by one....it's running into the macro routine. Hope this isn't my sk one ;)
 
Thats exactly what I am thinking. That kind of spam is caused by bad mq2melee holy/downshit.


[2015/04/17 07:34:57] DoCommand - Couldn't parse '1'

[2015/04/17 07:34:57] Cannot end a macro when one isn't running.
 
Oh I know it is........my chanter bugged out cause of the chromatic haze holy......didn't understand why. I thought I found a bug in KA with an aura but then I looked at debugs and saw it didn't like !${Me.Song[Chromatic Haze].ID} in my holy. Odd since it was fine with that on a different chanter but it kept spitting unable to parse, non numeric encountered. I changed it to a BOOL and it was fine. Weird how it was sometimes working and sometimes not.

Wannabe....if that's my sk holy, double check and ambiguous conditions and try to set for BOOL if .ID are specified. I don't know why sometimes it takes Spell.ID and other times it says non numeric encountered. I'm trying to make my holies more consistent now.
 
No response from ticket opener in regards to verifying if its a holy/down shit error (which all indications point to) for 7 days.

We can only assume from no response that this is resolved because it was apparently never a KA issue to begin with.

Ticket will be closed, but NOT locked for an additional week, as to afford user the opportunity to provide feedback as was requested.
 
Last edited:
Problem - Bug maybe ? just happened tonight when i loged on ?
Status
Not open for further replies.

Users who are viewing this thread

Back
Top
Cart