GameHelper: A light version of PoeHUD/Exile-Api

[hermes790727]

It seems that the download is still the same as the offset

[GameHelper]

It seems that the download is still the same as the offset

Is everyone having the same experience? Or just the Garena folks?

[camapxam]

Is everyone having the same experience? Or just the Garena folks?

working fine with me. No problem with offset (standalone client version)

[ocslappy]

these ones I haven't added yet. Can you share the component list they got? so i can add it to GH.
Also, where did you ignore it? using a Fork are you?

Metadata/Monsters/Daemon/Archnemesis/ColdSnapGroundDaemon
Is Valid: True
Entity Type: Monster
Componenets>>
Animated: 17049F06240
Inventories: 1700BDF5BB0
Pathfinding: 16EF0EC7DB0
Monster: 1700A805740
Actor: 16F71CEE1A0
BaseEvents: 16F87F6B6E0
Stats: 16F28ED5310
DiesAfterTime>>
Address: 16F38616B90
Targatable: 1701A4278D0

These archnemesis daemons are also the reason why some blue packs have double icons (one blue *the correct one* and and one red *the daemon*) on top of eachother. The easist way to find these is to just enter Uber Atziri's map, since all packs in there are magic (blue) by default, the red dots are easy to spot.

Where can i find the component list in the Data Visualization tool?

[killerng1703]

Is everyone having the same experience? Or just the Garena folks?

Seems that only garena fork has that problem.
I am currently using the v.0350 with the latest garena offset, still have this problem.

[Terroos]

Every time someone says "i got banned" they never elaborate or reply back. So weird. I've been using this since release with limited user and have never gotten banned.

[myspleen]

Is everyone having the same experience? Or just the Garena folks?

its been working on standalone for me as well

AutoHotkey Feature Request: Conditions to wait for another trigger to be/or not be on cooldown. Example: Trigger 1 has 3sec cooldown, on the Conditions for Trigger 2 you end up entering something like (Trigger 1) (is not/is) On cooldown

Is this something that could be easily implemented? It would help immensely to mitigate sending an unnecessary amount of inputs to POE, and really open things up in a big way for creativity/customization.

[JustAnotherGamer]

working fine with me. No problem with offset (standalone client version)

+1
Working fine for me as well.

[JustAnotherGamer]

Does the cooldown reset when you change zone?
If it doesn't, could it be added (or changed) so that it does?

I use the cooldown to skip a hotkey until the flask effect or skill cooldown has expired, but if the cooldown doesn't reset between zones then there's a (rare) scenario where the hotkey doesn't trigger early in a new zone. One might argue that I could just use "player doesn't have flask effect" as a condition instead of the cooldown, but that doesn't play well with e.g. an enduring mana flask and the flask's added effect, because enduring will keep the flask active and prevent the ailment removal - or vice versa, triggered ailment immunity will prevent use on low mana.

[GameHelper]

its been working on standalone for me as well

AutoHotkey Feature Request: Conditions to wait for another trigger to be/or not be on cooldown. Example: Trigger 1 has 3sec cooldown, on the Conditions for Trigger 2 you end up entering something like (Trigger 1) (is not/is) On cooldown

Is this something that could be easily implemented? It would help immensely to mitigate sending an unnecessary amount of inputs to POE, and really open things up in a big way for creativity/customization.

Wouldn’t adding few secs delay on the condition ( not the rule) helps?

Seems that only garena fork has that problem.
I am currently using the v.0350 with the latest garena offset, still have this problem.

Okay, will see if I can fix Garena.

[GameHelper]

Does the cooldown reset when you change zone?
If it doesn't, could it be added (or changed) so that it does?

I use the cooldown to skip a hotkey until the flask effect or skill cooldown has expired, but if the cooldown doesn't reset between zones then there's a (rare) scenario where the hotkey doesn't trigger early in a new zone. One might argue that I could just use "player doesn't have flask effect" as a condition instead of the cooldown, but that doesn't play well with e.g. an enduring mana flask and the flask's added effect, because enduring will keep the flask active and prevent the ailment removal - or vice versa, triggered ailment immunity will prevent use on low mana.

Hmm, valid point, I don’t know the answer, you have to test it. Also keep into consideration that area change takes few seconds. So, let me know if after area change cooldowb stays or not. Don’t use fked up cool downs just for the sake of testing this e.g. 10 second cooldown.

[JustAnotherGamer]

Wouldn’t adding few secs delay helps?

I don't see that working as an alternative, but maybe I'm just not creative enough. :-D
Where do I put the delay that you're thinking of?

I have these two triggers:

        {
          "Conditions": [
            {
              "$type": "AutoHotKeyTrigger.ProfileManager.Conditions.VitalsCondition, AutoHotKeyTrigger",
              "operator": "LESS_THAN",
              "vitalType": "MANA_PERCENT",
              "threshold": 30,
              "component": null
            },
            {
              "$type": "AutoHotKeyTrigger.ProfileManager.Conditions.FlaskChargesCondition, AutoHotKeyTrigger",
              "operator": "BIGGER_THAN",
              "flaskSlot": 4,
              "charges": 5,
              "component": null
            }
          ],
          "delayBetweenRuns": 6.0,
          "Enabled": true,
          "Name": "ManaFlask",
          "Key": 53
        },
        {
          "Conditions": [
            {
              "$type": "AutoHotKeyTrigger.ProfileManager.Conditions.AilmentCondition, AutoHotKeyTrigger",
              "statusEffectGroupKey": "Frozen Or Chilled",
              "component": null
            },
            {
              "$type": "AutoHotKeyTrigger.ProfileManager.Conditions.FlaskChargesCondition, AutoHotKeyTrigger",
              "operator": "BIGGER_THAN",
              "flaskSlot": 4,
              "charges": 5,
              "component": null
            }
          ],
          "delayBetweenRuns": 12.0,
          "Enabled": true,
          "Name": "FreezeFlask",
          "Key": 53
        }

When I used the "player doesn't have effect of flask" condition then I was occasionally getting frozen or ran out of mana. I'm thinking that if the cooldown isn't reset on zone change then I could enter a zone and be vulnerable to freezing for several seconds because the immunity has been reset, but the trigger hasn't.

[JustAnotherGamer]

Hmm, valid point, I don’t know the answer, you have to test it. Also keep into consideration that area change takes few seconds. So, let me know if after area change cooldowb stays or not. Don’t use fked up cool downs just for the sake of testing this e.g. 10 second cooldown.

I was replying while you were editing.
I'll do some testing to see if it resets, but I asked because my feeling is that it doesn't reset.

PS: The actual cooldown is even bigger than 10 seconds because it matches the duration of the freeze immunity. So it's long, but necessarily so.

[JustAnotherGamer]

Tests show that the cooldown persists across zone changes.

[imusya]

Thanks for reply

I downloaded 0.350, but still have same problem
I'm use Garena version