SolarStrike Software

That could be pretty tricky to debug from here on. There's a ton of things that could cause that and there's no simple instructions I can really give you to just solve it. Would you possibly trust me to borrow your account for a bit? I don't have a Champion/Rogue to test with, but I'm sure I could p...

I wonder if it may not even be detecting the skill at all. Try turning on the debug option for skill discovery: <option name="DEBUG_SKILLDISCOVER" value="true" /> Now when you start the bot, it should scan the game's memory looking to extract the skill information. It will print ...

Sorry that's not working for you. Lets see what we can do. First, if you change your classes to just Champion (drop the Rogue for now), does the skill work? Either with the original ID and buffnames, or with your changes. Please let me know the results of this test. Next, try turning DEBUG_SKILLUSE ...

I looked into this back in 2008. There likely isn't going to be any such hack. If I remember correctly, the server does not even send you any information about hidden characters unless they are very close to your normal detection range anyways. So technically you can hack it and make it easier to ta...

Can you please link to the script you're talking about?
Also, please explain *what* isn't working about it. If I can't reproduce the exact issues you're seeing, it likely won't be fixed.

The game had an update awhile ago that moved where an item's cooldown is stored. That made it really difficult to keep track of. It looks like I put that temporary fix in to just make it work while I had patched up all the other changes and then just forgot about the item cooldown. I just pushed up ...

I just tested this out myself. As far as I can tell, it works just fine. To test, I first got the address of monster. Then, I just plugged it into the function like so: local followtgt = 0x4B747800; telefollow(10, followtgt); When ran, my character continually teleported a few steps forward until re...

Following up on this again -- the issue OluxZarjaNebesnogo was having has been resolved and the fix is in the most recent script update.

I'm not able to reproduce the Warden Briar Shield issue; mind if I borrow your character again? Since I assume you changed your password (and you should have!), I'll need you to change it again and send me the new password. The "Exit early" thing is an easy fix and I'll take care of that w...

The "Exit early" thing was a debug statement I accidentally left in. It's harmless and you can ignore that. For the other issues, I'll need to find some time to investigate those. Been pretty busy lately, so can't commit to anything at the moment. Can you confirm if you're playing on the G...

Following up on this, OluxZarjaNebesnogo and I had worked out a solution in PM. The fix has been released; use the updater to get the fix.

About skill IDs. Example for the warlock/priest class: "PRIEST_RISING_TIDE" has an elite skill that removes casting time and now this skill has new IDs in the warlock/priest class combination. The bot continues to use the skill, but the console displays: Use MACRO: PRIEST_RISING_TIDE => *...

Thank you. Just pushed up another fix for that. I only have 2 pets to test with, but it should be fine.

Found the problem. The address was out of date, and nothing useful in the autoupdater for it.
Go ahead and update your scripts and eggpets should begin working for you.

As it turns out, we might not necessarily need to do anything fancy with the IDs; the bot generally doesn't care about them too much. I've done some debugging and changed the skill ID for Rogue Shadowstab to one of the other variants, and the bot continued to use Shadowstab for me. It checks if you ...

So it would seem that each subclass has a variant for some skills. That's a pain in the butt. There's two ways I can see to get around this. First, is an easy solution: add a new skill line for each variant. Like so: <skill name="ROGUE_SCOUT_SHADOWSTAB" id="492329" range="50...

You would need to refactor the waypoint 16 code. We can actually simplify it a bit as a result. Simply iterate over the full list in nameTable and send the stones. This is untested, but it should look something like this: for counter = 1, #nameTable do repeat player:target_NPC(110793) -- Mailbox yre...

So what's likely going on is that it thinks the skill cast is failing due to how the bot is waiting and checking on various things. Try this: <skill name="DIYCE_SKILL" range="180" type="damage" casttime="0" cooldown="1" target="enemy" prior...

But with running it like this MM only press the skill button x3 times and pause and press x3 again

Is that 3 times really quick, pause for a second, and then again, or is the delay longer?

This might sound counter-intuitive, but what if you set the cooldown to 1 instead of 0, does that help?

For the Thunder skill, is it a ground-targeted AoE by chance?