• 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
Epic Laziness

Release Epic Laziness v0.4.25

That is very odd that it put your weapons back on at the end of that. It should not do that until attack is turned off
It happened on and off, I only screenshot a bit. Are the weapons being held on cursor? I never saw them in bag, I have only one bag they can go to. If auto inventoried, they might be going back to primary and secondary so fast and then picked back out of those slots?
 
It happened on and off, I only screenshot a bit. Are the weapons being held on cursor? I never saw them in bag, I have only one bag they can go to. If auto inventoried, they might be going back to primary and secondary so fast and then picked back out of those slots?
That was actually something that I did when i initially wrote the code to remove the weapons. Without thinking I had them autoinv and they went back on. Now it searches for a free slot in your bags and puts them in there (starting at the last slot, of the last bag, and working backwards)

I did add a loop to make sure the dire mob has despawned before reequiping now. Before it was waiting for it to despawn OR fall below 80% health.
 
I added a bit a new code (provided by the wonderful Derple) to give better logging and debugging features. You can set the logging level in the Console tab, as well as having the log messages sent to you macroquest log file. If you are experiencing issues it would be most helpful if you set the debug level to Super-Verbose, and turned on Log to File so that you can provide me with as much information as possible.

Thank you.
 
Running Bst 1.5 when get to Riwwi, it hangs looping and easyfind keeps dying I got the following error. I just paused script went and picked up item in water got out and unpaused it. There was an error that easyfind was putting out but I forgot to copy it sorry.
 

Attachments

  • bst error 2.PNG
    bst error 2.PNG
    20 KB · Views: 0
  • bst error 3.PNG
    bst error 3.PNG
    34.9 KB · Views: 0
  • bst console errors.PNG
    bst console errors.PNG
    19 KB · Views: 0
Even with latest version and latest meshes it is still not able to path to Captain Varns for you? Just sitting there stuck on step 5 after completing step 4? (Saying "take on this task" to Ritald)


Where was your character when attempting to start? It may have been having a pathing issue. Although I cant imagine it would have been. I will double check my end to insure I havent done an oopsiefucky.



Did you happen to save the message that popped up in the message box when you crashed? If not that is fine, I will look into the functions that are used at those steps.



Warrior has not yet been implemented, but it also should not be erroring out this way. I will fix the error asap, and hopefully get Warrior added in the near future.



Some functions were changed so I may have reintroduced this bug on accident. I will take a look at it today and get it cleared up. As to the packageman stuff. Previously I was doing a very sloppy form of version checking, simply checking if the version being ran was more than 18 hours old. I added luasec and socket to the script so that it can check the version in another file online, and determine if there is a newer version the user should be running. With how often bug fixes and version bumps are currently taking place I've got to do what I can to insure users are on the latest version. It makes looking into bug reports much easier, and insures the user is having the best possible experience.



1. I will look into these steps. It should be checking for the presence of all 3 before moving on. So I will take a look at this.

2. I currently have shaman set up to require a rogue to pick rather than possibly falling back on using the key. I've done it this way because there are several locked doors to contend with in POM. The first at the front to the Black Reaver for Ghiosk, the second and third being up above to get to Neh`Ashiir, which to my knowledge can only be picked. And finally the elevator behind the first reaver that can be picked, or use the key dropped by Neh`Ashiir. Since there are doors that require a lockpicker anyways, I currently have the shaman requiring a lockpicker for all 4. This is definitely not optimal, and something I intend to go back to and make a bit cleaner (as well as the entire process of relying on a lockpicker.

When you brought the rogue in to pick the door, was it grouped with you, and selected in the grouping drop down? The script will command the selected rogue/bard (or the first it finds in group if set to Group instead of an individual character) to open the door.

3. The step to farm for the Student's Log is a single step for farming all 6 items (Crier's Scroll, Merchant's Letter, Personal Diary Page, Priest's Diary Page, Written Announcement, Student's Log) so it bases itself in the stables area, and then uses hunter tank to murder everything in a rather large area. It maintains this radius even after the other 5 items have been obtained. I can eventually look into having it use a smaller radius if only Student's Log remains to be looted, but I will need to think a little bit on how to best implement this.

As to becoming stuck in the water. Which water is it becoming stuck in? The water in the red circle, the yellow circle, or the green circle? If I had to guess I would say yellow, but I do not want to make any assumptions.

View attachment 60348

4. The outline is still a work in progress. I intend to include the current outline step in the general tab beneath the step# and status message. And hopefully will be able to add that soon. Bug squashing has just taken priority over that.



This error message would pop up if you were running a class that is not yet implemented in the script. It should not be crashing out with an error however, so I will be fixing that tonight.

The three modules installed are sqlite, luasec, and socket. Sqlite is used for the database that houses all the information about the quests and their steps. Socket is so that it is able to access a file via http off of a website for version checking. And luasec is used to allow that connection to be handled in https.



Rogue 1.5 is currently about 60% done. It is a VERY long quest (they were punishing rogues for the 1.0 being so dang easy) so it has been taking me much longer to implement than most other quests.
all those tradeskills and hand ins..I really got discouraged. I totally undeerstand.
 
anyone know how to fix the loop where i have sheath of darktidings for sk 1.5 but it keeps wanting to redo the combine which i dont have the materials to do anymore, and wont let me skip, i try to skip to next part and it just stops
"edit after a restart and few more attempts to skip it finally took hold and started at next steps to do turn in" also it did crash after i did the combine so not sure if restarting at that point may have bugged it"
 
Can you describe the issue you ran into in shaman 1.0 and 1.5?


I will take a look at bst1.5 step ~117



Which quest for the beastlord? Pre 1.5?
I'll run it again and make detailed notes. But only to help out not to complain. I think this is a really good program.
 
Not sure if it's previously mentioned but if Auto Loot isn't on it seems to prevent progress. If there's a way to turn it on when the quest run starts it could save some issues.

My SHA didn't have auto loot on so she wasn't picking up Necklace of Perseverance, however she did proceed with the quest and into Storms for the tree, which then didn't spawn because I hadn't looted/handed in necklace. I went back through the quest line a few times before I realized what was happening, once I turned on Auto loot it went fine.
 
anyone know how to fix the loop where i have sheath of darktidings for sk 1.5 but it keeps wanting to redo the combine which i dont have the materials to do anymore, and wont let me skip, i try to skip to next part and it just stops
"edit after a restart and few more attempts to skip it finally took hold and started at next steps to do turn in" also it did crash after i did the combine so not sure if restarting at that point may have bugged it"

That combine was requesting another item which was not present in inventory. I have fixed that in the next version that uploads which should fix whatever crash was taking place there.

In the future if it crashes and you are stuck on a step like that you can use the FF and Rewind buttons to manually adjust the step you are on. In this case you would want to skip to step 57 which is wher the script travels to Sienn Kastane to give her the sheath.

low priority request: Save IMGui position and sizing.

For sure.


Not sure if it's previously mentioned but if Auto Loot isn't on it seems to prevent progress. If there's a way to turn it on when the quest run starts it could save some issues.

My SHA didn't have auto loot on so she wasn't picking up Necklace of Perseverance, however she did proceed with the quest and into Storms for the tree, which then didn't spawn because I hadn't looted/handed in necklace. I went back through the quest line a few times before I realized what was happening, once I turned on Auto loot it went fine.

The script should handle all looting of items it requires. If you could provide debug messages of what was taking place when it was supposed to be looting that would be extremely helpful.

Running Bst 1.5 when get to Riwwi, it hangs looping and easyfind keeps dying I got the following error. I just paused script went and picked up item in water got out and unpaused it. There was an error that easyfind was putting out but I forgot to copy it sorry.

At this step the quest is looking for Gryme the Crypt Guardian to kill him and loot his key so we can make it to the ground spawn item. The respawn on Gryme is ~3hours and the respawn on the ground spawn behind the locked door is ~2h40m.

There should be a step here to wait for him to spawn (that would provide the user with a bit more information as to what is happening) that I left out. I will get that added so as to provide the user with better information.
 
Running Bst 1.5 when get to Riwwi, it hangs looping and easyfind keeps dying I got the following error. I just paused script went and picked up item in water got out and unpaused it. There was an error that easyfind was putting out but I forgot to copy it sorry.

As to the portion with Riwwi, I had some issues with this step as well when testing, but I thought I had corrected them. I will take another look at this step asap.
 
Even with latest version and latest meshes it is still not able to path to Captain Varns for you? Just sitting there stuck on step 5 after completing step 4? (Saying "take on this task" to Ritald)


Where was your character when attempting to start? It may have been having a pathing issue. Although I cant imagine it would have been. I will double check my end to insure I havent done an oopsiefucky.



Did you happen to save the message that popped up in the message box when you crashed? If not that is fine, I will look into the functions that are used at those steps.



Warrior has not yet been implemented, but it also should not be erroring out this way. I will fix the error asap, and hopefully get Warrior added in the near future.



Some functions were changed so I may have reintroduced this bug on accident. I will take a look at it today and get it cleared up. As to the packageman stuff. Previously I was doing a very sloppy form of version checking, simply checking if the version being ran was more than 18 hours old. I added luasec and socket to the script so that it can check the version in another file online, and determine if there is a newer version the user should be running. With how often bug fixes and version bumps are currently taking place I've got to do what I can to insure users are on the latest version. It makes looking into bug reports much easier, and insures the user is having the best possible experience.



1. I will look into these steps. It should be checking for the presence of all 3 before moving on. So I will take a look at this.

2. I currently have shaman set up to require a rogue to pick rather than possibly falling back on using the key. I've done it this way because there are several locked doors to contend with in POM. The first at the front to the Black Reaver for Ghiosk, the second and third being up above to get to Neh`Ashiir, which to my knowledge can only be picked. And finally the elevator behind the first reaver that can be picked, or use the key dropped by Neh`Ashiir. Since there are doors that require a lockpicker anyways, I currently have the shaman requiring a lockpicker for all 4. This is definitely not optimal, and something I intend to go back to and make a bit cleaner (as well as the entire process of relying on a lockpicker.

When you brought the rogue in to pick the door, was it grouped with you, and selected in the grouping drop down? The script will command the selected rogue/bard (or the first it finds in group if set to Group instead of an individual character) to open the door.

3. The step to farm for the Student's Log is a single step for farming all 6 items (Crier's Scroll, Merchant's Letter, Personal Diary Page, Priest's Diary Page, Written Announcement, Student's Log) so it bases itself in the stables area, and then uses hunter tank to murder everything in a rather large area. It maintains this radius even after the other 5 items have been obtained. I can eventually look into having it use a smaller radius if only Student's Log remains to be looted, but I will need to think a little bit on how to best implement this.

As to becoming stuck in the water. Which water is it becoming stuck in? The water in the red circle, the yellow circle, or the green circle? If I had to guess I would say yellow, but I do not want to make any assumptions.


It was getting stuck in what you marked out in yellow.
View attachment 60348

4. The outline is still a work in progress. I intend to include the current outline step in the general tab beneath the step# and status message. And hopefully will be able to add that soon. Bug squashing has just taken priority over that.



This error message would pop up if you were running a class that is not yet implemented in the script. It should not be crashing out with an error however, so I will be fixing that tonight.

The three modules installed are sqlite, luasec, and socket. Sqlite is used for the database that houses all the information about the quests and their steps. Socket is so that it is able to access a file via http off of a website for version checking. And luasec is used to allow that connection to be handled in https.



Rogue 1.5 is currently about 60% done. It is a VERY long quest (they were punishing rogues for the 1.0 being so dang easy) so it has been taking me much longer to implement than most other quests.
The yellow circle is where the shaman gets stuck.
 
Last edited:
On the beastlord epic 1.5 after turning in the letter to Yerika Sisslak to spawn Girplan Spiritleech and after killing Girplan Spiritleech the Rashara’s Warder’s Essence isn't automatically looted and the script gets stuck in a loop. I got another letter to test it and did the turn in again and on the second spawn the Rashara’s Warder’s Essence failed to loot again. I manually looted and the script continued properly.
 
The Creator spends every waking hour it seems improving this Lua. I'm not sure it's possible to make perfect but they are damn sure trying. I would have spent $50 on this not just $15 to get Epics on some of my toons I've been too lazy too.
I just wanted to throw this in there. My 2 cents.
 
Rog 1.5 pre: Step 22 or 23.

Screenshot 2024-04-14 083044.png


I have a cleric that has epic 1.0. It will let me start 1.5 prequest, but it wont let me start 1.5.

1713098075914.png
 

Attachments

  • 1713097927679.png
    1713097927679.png
    19.5 KB · Views: 0
The yellow circle is where the shaman gets stuck.

I am uploading a mesh now that should avoid that water there much more aggressively.

On the beastlord epic 1.5 after turning in the letter to Yerika Sisslak to spawn Girplan Spiritleech and after killing Girplan Spiritleech the Rashara’s Warder’s Essence isn't automatically looted and the script gets stuck in a loop. I got another letter to test it and did the turn in again and on the second spawn the Rashara’s Warder’s Essence failed to loot again. I manually looted and the script continued properly.

I will try to test this before I call it quits for the night. Thank you.
 
Rogue 1.5 is completed and will be released shortly. The quest is done but I have not yet had a chance to finish the outline table.
 
Sham 1.5 , Crashed as soon as used AoC. Did that part manually, then restarted it at step 149 i believe.

Also, maybe a future QoL, possibly have shammys shrink upon zoneing? (pita as its after /travelto maybe have to be broken into sections) but large races get stuck everywhere! bain of my existence :P

Outstanding job though so far, very very impressed!
 
Looking great. Can't wait to try the Rogue 1.5 now. 1.5 Prequest was great. Love how you list all the tradeskill requirements upfront :). Also, note: the outline isn't loaded for it yet. I love that feature as I can follow along as he goes and see what's next on the agenda. Haven't tried the 1.5 yet for rogue, but not sure if no outline will stop it from performing.
 
during shaman step 9,10,11,12 on 1.5
going to kimm mcshannel kept getting stuck under the doc
 
I have not seen anyone report it, but as a just in case, you may want to stop/pause all combines when you have to put things in a special bag for combine. Every time it cannot find things properly and messes up my bags. I leave a blank main inv open, and also have put the combine container in the empty main inv, but same results. I did not mark exactly, apologies. But I believe for both Shaman and Bard different 1.5 and 2.0 very likely. The Lua crashes and gives red text error, and all bags are moved around, some have items all shuffled about to different bags, and 'never finds the combine items'. I have not yet tried Rog, but I saw you finished and noted it is trade skill heavy, so I can try to report that. Just finished another bard 2.0, smile.
 
I have not seen anyone report it, but as a just in case, you may want to stop/pause all combines when you have to put things in a special bag for combine. Every time it cannot find things properly and messes up my bags. I leave a blank main inv open, and also have put the combine container in the empty main inv, but same results. I did not mark exactly, apologies. But I believe for both Shaman and Bard different 1.5 and 2.0 very likely. The lua crashes and gives red text error, and all bags are moved around, some have items all shuffled about to different bags, and 'never finds the combine items'. I have not yet tried Rog, but I saw you finished and noted it is trade skill heavy, so I can try to report that. Just finished another bard 2.0, smile.

It should empty the bag in slot 8, move the combine container you need into slot 8, and then move the items it needs for the combine into the combine container we moved to slot 8.

I will try to check and see what may be causing a crash here.
 
I have added the ability for travel speed AAs to be used to speed you up. It will check yourself, plus any group members you have selected and check them for skills that will increase your run speed. If you have multiple characters that have travel speed buffs it will select the first one it finds in group. So if you want a specific skill used disable the skills on the other classes you do not want using it.
 
At the end of the bst 2.0 there is a 10 minute or so scripted scene that you must sit through before you can say ready and receive the 2.0 however the Lua auto follows Alladnu Araihse and says ready immediately then ends still auto following well before the actual end of the scene.
 
At the end of the bst 2.0 there is a 10 minute or so scripted scene that you must sit through before you can say ready and receive the 2.0 however the lua auto follows Alladnu Araihse and says ready immediately then ends still auto following well before the actual end of the scene.

I will take a look at this. It should be creating an event to wait for in order to say the final string.
 
Paladin Pre 1.5
Part number 13. Paly zones into PoS and just sits at zone in saying.. waiting for Neffiken, Lord of Kelek Vor to spawn. He does not spawn without killing the giants inside the fort and the 5 north of the fort.

Edit: Now I have manually killed the mobs and the Fabled version spawned and I can not target it
 
Last edited:
Release Epic Laziness

Users who are viewing this thread

Back
Top
Cart