GW working bots 2024

Quote:

Originally Posted by corey54321 Code: Script Notes: (Weapon Slot-1) Shortbow +15/-5 vamp +5 armor is the best weapon (Weapon Slot-2) Kieran Bow Ideal character is max armor (War/Para) with Knights Insignias and the Absorption -3 rune superior Any char can go into mission if you send the right dialog ID (already in script) You just need the Keiran's Bow that Gwen gives for the right dialog ID

Thanks for clarifying, but even with that fixed, it still crashes GW.

Quote:

Originally Posted by xxGuestXX I have an issue with GW crashing when I try to start the war supply bot. The functionality of the bow button seems to work without issue. Any ideas?

Make sure you uncheck the render checkbox .

Lil' Jimmy Raynor!

Put the month and year in bots you upload. I honestly just name them exactly what they are with respective folders as well. "Voltaic [May 2024]" would be is a good example, the version strings make no sense when you think about it. If you're the only author and someone else maintains or updates the project, will they even know how to use the version strings you set up, or even be bothered to updated anyway? This is why my tagging system works well because a bot rarely receives more than one update from one user a year, let alone a month, and it still works well even if the bot had a quick patch within the same time period. Including the profession in the folder name and at least title of bot script seems like a good idea as well. "[Core]/[Ranger]" are examples. A bot folder when extracted may read "(Core) Kilroy [March 2024]" or "(Ranger) ToC [January 1969]".

I meant to do this a long time ago, this thread... A really well organized with a good file hierarchy and credit where credit is due so that posters feel their work does not end up in a jumbled pit. This makes it easier to read, easier to find, and less redundancy overall. Was well needed! I almost thought a thread just for releases and no questions that are stickied might be the optimal way to go, then have questions below in their own thread, per even type of bot, maybe.

Think I am just getting old too...

I will second correcting the file/folder naming structure. This is an excellent refresh post regardless of what else is done. Thank you again Jim

Quote:

Originally Posted by Hiking Corey Lil' Jimmy Raynor! Put the month and year in bots you upload. I honestly just name them exactly what they are with respective folders as well. "Voltaic [May 2024]" would be is a good example, the version strings make no sense when you think about it. If you're the only author and someone else maintains or updates the project, will they even know how to use the version strings you set up, or even be bothered to updated anyway? This is why my tagging system works well because a bot rarely receives more than one update from one user a year, let alone a month, and it still works well even if the bot had a quick patch within the same time period. Including the profession in the folder name and at least title of bot script seems like a good idea as well. "[Core]/[Ranger]" are examples. A bot folder when extracted may read "(Core) Kilroy [March 2024]" or "(Ranger) ToC [January 1969]". I meant to do this a long time ago, this thread... A really well organized with a good file hierarchy and credit where credit is due so that posters feel their work does not end up in a jumbled pit. This makes it easier to read, easier to find, and less redundancy overall. Was well needed! I almost thought a thread just for releases and no questions that are stickied might be the optimal way to go, then have questions below in their own thread, per even type of bot, maybe. Think I am just getting old too...

I personally use the dating system as you pointed out (thats how I did it in the Master Vanquisher thread) but so many posters use versions so... shrug. I'll take the time soon to reupload all the files with a date attached as a baseline reference.

I've edited the part where I suggest bot makers use a naming convention with a template and 2 examples.
When I reupload the bots it will be TAG_NAME_CLASS_DATE


To everyone:
If anyone uses any of the bots, let me know how it goes, if they work, if they give issues or have remarks (like a mini review of sorts), so I can add that info.

Boreal Chest Runner (2 variant)

its working :handsdown: tested it out all day since its doing well so far (only first 3 skills working though)

Quote:

Originally Posted by bul bul Boreal Chest Runner (2 variant) its working :handsdown: tested it out all day since its doing well so far (only first 3 skills working though)

Been using it too, will update the post. It only uses dwarven stability/dash and IAU if you check the box.

The other variant is derv specific (don't have a derv :( )

Quote:

Originally Posted by JimRaynerd I personally use the dating system as you pointed out (thats how I did it in the Master Vanquisher thread) but so many posters use versions so... shrug. I'll take the time soon to reupload all the files with a date attached as a baseline reference. I've edited the part where I suggest bot makers use a naming convention with a template and 2 examples. When I reupload the bots it will be TAG_NAME_CLASS_DATE To everyone: If anyone uses any of the bots, let me know how it goes, if they work, if they give issues or have remarks (like a mini review of sorts), so I can add that info.

That is a good template. The archive and folder inside (matching name of archive) could use this at the minimum. My idea was to either have the bot display this in the dialogue or window header of the bot (requires more effort and is in a variety of areas depending on bot). I prefer to keep my bot script names themselves simple such as Voltaic, Kilroy, Vaettir, etc. because a few bots rely on the file names themselves to stay the same. But having the same format in three places would really clear things up for everyone and create a chain-of-custody, knowing exactly who had a file, when, and a changelog in their post would their modifications to their contribution. This would make memory effortless and a breeze.

Quote:

Originally Posted by Hiking Corey  Spoiler That is a good template. The archive and folder inside (matching name of archive) could use this at the minimum. My idea was to either have the bot display this in the dialogue or window header of the bot (requires more effort and is in a variety of areas depending on bot). I prefer to keep my bot script names themselves simple such as Voltaic, Kilroy, Vaettir, etc. because a few bots rely on the file names themselves to stay the same. But having the same format in three places would really clear things up for everyone and create a chain-of-custody, knowing exactly who had a file, when, and a changelog in their post would their modifications to their contribution. This would make memory effortless and a breeze.

Updated the Vaettir/raptor/fow/Doa section, should be good like that.

I dont like when i have to pay attention to bots i use, so I made this.

Auto deposit bones and dust.

Now bot stops and closes when u have 1 free slot in inventory and in chest. Before it used to keep farming even if it was full.

It also resigns when there is 1 mob around, as sometimes 1 min is spend in 1 mob when it could restart the whole thing.

anyone has working JQ Bot ? PM me is also fine, thx <333

Anyone running bots in pre, what's the best class to bot with? Currently running 5x ele/mo but the public bots is really bad.

Hello!

Fyi - I've been testing: OmniFarmer 2023 - Working May 2024 EOTN titles.

I tried for Norn, but the bot stop before taking the blessing near verdant cascade.

Quote:

Originally Posted by geneticcleans Hello! Fyi - I've been testing: OmniFarmer 2023 - Working May 2024 EOTN titles. I tried for Norn, but the bot stop before taking the blessing near verdant cascade.

Alright I'll update it. I used that Omni for LB/SS and it worked so figured the rest was also good.

I think this one clean a bit more. But it miss group sometime.
Not mine, not my credit.
PS: It cast all spell.