Void Highlord's Challenge Bot V5 (Grimoire 3.8)

[sexyberries]

Hi guys.
I am currently in the midst of getting my Void Highlord class and have been using the v4 bot a fair bit.
A lot of the comments in that thread are pointing to a problem with the archfiends favor section in particular, where if you reach 300 nulgath's favor before 300 archfiend's favor, it skips archfiends entirely. This means the bot will loop continuously with no resolution.
In my version, I have rectified this problem.
There was also a problem with the drops, in which Unidentified 10 was discarded and not collected. The other drops from the quest to form the set are also no included (likely to save space) but this was not a problem for me as i have tonnes of space. If this is a problem for you, just remove them from the drop list.

So to list the fixes I have implemented:

• Fixed archfiend's favor skipping bug
• Fixed unidentified 10 bug
• Fixed other drops not being collected from the quest
• Fixed tercess black screen glitch

To use this bot, you need to replace the name in the packet move command to your own. If you simply open the gbot file in a text editor, find and replace "playername" for your characters username, save, then launch the bot, everything will work. This step is crucial


As with the last version patched by @Koyte,

Requirements to run the bot smoothly:

• Headen Onyx of Nulgath
• Nation Round 4 Medal to get Emblems of Nulgath (you can run the bot without but it's safer to have this with you while botting)
• Level 50
• Rank 3 Spellcrafting or higher

Notes:

• The Skills are set for ArchPaladin make sure to edit for your class
• You should have around 15-20 inventory spaces
• If you see the bot spending a lot of time fighting Mana Golem. That's normal he's either farming the Voucher of Nulgath (non-mem) or Uni 13 and sometimes it takes a lot of time.

Again, thanks to @Koyte for building off the previous version.
Thanks also to @AhmedRaslan, who in his latest bot created a workaround for join bugs. This workaround involves using packets to move rather than join commands.
Here is my contribution, and I hope it can fix some bugs people have been having.

If for whatever reason it does not fix these bugs or has created new ones, leave a comment and I'll get right to it.

Thanks,
Berries

I have updated scans for the new file, please wait for the re-approval
@Dab

Scan 1

Scan 2

[arishat]

Invalid Attachment specified. If you followed a valid link, please notify the administrator.

[sexyberries]

Invalid Attachment specified. If you followed a valid link, please notify the administrator.

You have to wait for it to be approved by a moderator. Shouldn't be too long

[azndkflush]

What about the bug that happens when you try to join tercessuinotlim and it goes black screen ?

[Dab]

File approved

[sexyberries]

What about the bug that happens when you try to join tercessuinotlim and it goes black screen ?

I haven't encountered this yet. Are you able to reproduce this bug even with this version?
If you are, let me know what causes it and I'll take a look at it

Edit: I was able to find the bug and I have fixed it using a workaround implemented by @AhmedRaslan in his latest bot. This workaround involves using packets to move rather than join commands.

[Dab]

file approved

[StarixCrown]

I have found a problem with the bot, whenever it needs to go to farm Dark Makai and the room is full (which is basically pretty much all the time) it simply stops. I do not know how to make it check and loop if it is not in the correct zone so I would appreciate if you could update it.
So far what I do is simply change the join command from 9999 to 9989 or any similar number.
Regardless , its a great bot and thank you for taking the time to make it.

[Faz3]

Yay Fixed THANK YOU

[bunnyfight209]

When you turn in for tainted gem it's too fast so I got dc'ed every time

[Trash]

When you turn in for tainted gem it's too fast so I got dc'ed every time

Add a delay of 500ms

[JibjabOfCrC]

well i found many bugs , i guess the old one is better

[sexyberries]

I have found a problem with the bot, whenever it needs to go to farm Dark Makai and the room is full (which is basically pretty much all the time) it simply stops. I do not know how to make it check and loop if it is not in the correct zone so I would appreciate if you could update it.
So far what I do is simply change the join command from 9999 to 9989 or any similar number.
Regardless , its a great bot and thank you for taking the time to make it.

Hi, thanks for your comment and the bug find. The code to check a map is in the following example:

{
        "$type": "Grimoire.Botting.Commands.Map.CmdJoin, Grimoire",
        "Map": "tercessuinotlim-9999",
        "Cell": "Enter",
        "Pad": "Spawn"
      },
      {
        "$type": "Grimoire.Botting.Commands.Misc.Statements.CmdMapIsNot, Grimoire",
        "Tag": "Map",
        "Text": "Map is not",
        "Value1": "tercessuinotlim",
        "Value2": ""
      },
      {
        "$type": "Grimoire.Botting.Commands.Map.CmdJoin, Grimoire",
        "Map": "tercessuinotlim-1e99",
        "Cell": "Enter",
        "Pad": "Spawn"
      },

If you change the code out using a text editor, this will fix that.
Thanks again for testing out the bot and finding a bug

- - - Updated - - -

well i found many bugs , i guess the old one is better

Can you elaborate on which bugs you have found? I would like to do my best to fix them. The old one was very good, yes. However I beleive it had more bugs that would completely seize the bot and prevent recovery. This bot fixes the two main bugs, those being the Archfiend's favor and the tercessuinotlim black screen glitch.
Thank you for your comment and I await your suggestions for improvement

[kiranvanek]

Got VHL using the v4 entirely, no need for v5 imo

[sexyberries]

Got VHL using the v4 entirely, no need for v5 imo

That's great! However there were some massive issues in the bot that only pop up under relatively unique circumstances, like if your archfiends favor somehow dropped slower than the nulgath stuff. This is fixed in this version among other bugs, which i feel requires a new post.