• 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 - Item timers

Addict

Well-known member
Joined
Aug 18, 2019
RedCents
570¢
Hello all!

A bug that I am encountering is that when I zone the item timers get messed up. For example the monk epic. After zoning and running the command:
[CODE lang="rich" title="Commands"]
/varset epicfists Transcended Fistwraps of Immortality
/echo ${FindItem[${epicfists}].Timer}
[/CODE]

returns a very high number of 1646. Prior to zoning the timer shows the correct number after usage of 180 seconds.
1569569669750.png
The items hotbar image also shows incorrectly that the item is ready and not on cooldown:
1569569680621.png

the red timer that normally appears is not showing on the hotbar but EQ knows that the item is on cooldown as it won't activate when clicked manually again within the timer of 3 minutes.

Has anyone encountered something similar? This seems to be the case with the Shaman epic as well. A quick fix is to remove the check
[CODE lang="rich" title="Commands"]
${FindItem[${epicfists}].Timer}==0
[/CODE]
from my code, but I don't want it to spam the click..
 
Last edited:
/echo ${FindItem[${epicfists}].Timer.TotalSeconds}

Reports it in seconds, try that for your tests. ticks are wierd.
 
/echo ${FindItem[${epicfists}].Timer.TotalSeconds}

Reports it in seconds, try that for your tests. ticks are wierd.

Running this command gives me 10812 which is about 180 minutes. The true value should be 3 minutes in total. Very weird.
 
Use TimerReady. I've never had an issue with it.

INI:
holyshit4=/if (!${FindItem[Mistmoore Battle Drums].TimerReady} && !${Me.Buff[Thunderous Barrier Rk. II].ID}) /useitem "Mistmoore Battle Drums"

as an example of it's usage. TimerReady returns item timer, if it's 0, it's ready to click.

C++:
    case TimerReady:
        Dest.DWord = 0;
        Dest.Type = pIntType;
        if (GetItemFromContents(pItem)->Clicky.TimerID != 0xFFFFFFFF)
        {
            Dest.DWord = GetItemTimer(pItem);
            return true;
        }
        if (GetItemFromContents(pItem)->Clicky.SpellID != -1)
        {
            Dest.DWord = 0; // insta-click or instant recast
            return true;
        }
        return false;
 
/echo ${FindItem[${epicfists}].TimerReady} returns 10853 when I zone for the monk epic. At this point I think I should reinstall eq.
 
Rich (BB code):
/echo ${Me.ItemReady[=${epicfists}]}

Returns FALSE when it was ready to use.

My current fix is to remove all ItemReady or Timer checks.
 
Rich (BB code):
/echo ${Me.ItemReady[=${epicfists}]}

Returns FALSE when it was ready to use.

My current fix is to remove all ItemReady or Timer checks.
Is there a reason why you're varsetting the epic item? are you changing the item after declaring it elsewhere?
 
if your thing returns 180 minutes then your thing is brokes

cause my clickies all reported corrrectly with the totalseconds.
/echo ${FindItem[=${epicfists}].Timer.TimeHMS}

i think your varset of a multiple word string is borking you, either do the = or enclose the name in quotes in the varset.
 
Yea, then sounds like something is corrupted in your install. But I have also seen where the date and time on your system is wrong and causes this issue.
 
Use TimerReady. I've never had an issue with it.
I replaced all TImer checks with this one. Thanks :)

Is there a reason why you're varsetting the epic item? are you changing the item after declaring it elsewhere?
No real reason, I'll take it out of varset and just use the name.

Yea, then sounds like something is corrupted in your install. But I have also seen where the date and time on your system is wrong and causes this issue.
I think this was it actually.. Thanks a bunch! I will do some more testing tomorrow to make sure.
 
Problem - Item timers

Users who are viewing this thread

Back
Top
Cart