-
Hail, we're RedGuides. We want you to play six (yes, 6!) EverQuest characters at once. We have scripts and a friendly community to help, please join our playstyle and say hello! 👋
- Thread starter Lisie
- Start date
- Seller
- #362
Lisie updated Epic Laziness with a new update entry:
Bug fixes
Read the rest of this update entry...
Bug fixes
Read the rest of this update entry...
- Seller
- #363
It would have exited at this step anyways due to being unable to loot the head, but the way it did so is a bug, I will upload a fix for it in a moment.
To skip past that step you have two options. You can use the fast forward/rewind buttons to move forwards and backwards in steps. Or you can go to the outline tab, and click on the next step in the quest (in this case it would be step 19, Travel to The Scarlet Desert and give Jimmic Adle the talisman of the Plasmatic priests (returned). Kill the mobs that spawn and loot head of high priest Valon)
- Seller
- #364
This is a bit of a bug, and a bit of odd behavior. The bug is that it was getting stuck searching for the murkglider leader. but that bug has been fixed in the latest version. The odd behavior is that for that step, if the Murkglider School Leader is already up in the zone, as the normally spawned raid version, you must kill it before talking to Kupiop and spawning the version for you epic. This should not have been an issue, but there was a bug causing it to search endlessly in the function where it found mobs to kill.
- Seller
- #365
This was another bug that has since been corrected. Sorry about that! Same function as the previous bug too. It now excludes corpses from its search.
In the code reworks i did a couple of nights ago I wrote a new function for searching for NPCs that it wants to kill, that would pick the closest by navigation distance, rather than closest by distance as the bird would fly. This was important for things like the discordling step because sometimes the nearest mob was actually a large distance away when pathing to it was considered. It bugged the heck out of me.
- Seller
- #366
- Seller
- #368
Oops! Pal 1.5 is not supposed to be available yet. I've not finished it. Sorry about that
worked great so far though !
/Lua run epiclaziness
thanks
tampa03cobra
Member
You are killing it Lisie!
This is amazing and I am so happy to be among the testers of this software. I'll keep running it through the motions and report the bugs. This is the definition of a game changer!
I quit the Lua a week ago because the shm 1.5 was buggy around step 92. I come back today am outside the guild lobby and run the Lua... I notice a shiny new UI with steps and other cool stuff. Allright let's rock! I click the start button and it says traveling to and I'm not going anywhere. Figured I'd just start on step one and let it ride. Hit start and still just sits there. I'm jinqxed
been playing with this on test recently and for the most part loving it ... UNTIL today go to do the combine for my sk 1.5 sheath STEP 50 (eye of dark god, blessed unicorn hair, and gloom nightmare hide) when all of a sudden CTD now i have no sheathe and a return to farming fear for 1 drop that is ugh
Per the Overview page:
Currently the following quests have been added to the script:
- Bard:
- Pre-1.5 - 1.5 - 2.0
- Beastlord:
- Pre-1.5 - 1.5 - 2.0
- Cleric:
- Pre-1.5 - 1.5 - 2.0
- Paladin:
- Pre-1.5
- Rogue:
- Pre-1.5
- Shadow Knight:
- Pre-1.5 - 1.5 - 2.0
- Shaman:
- 1.0 - 1.5 - 2.0
oh my bad haven't been on overview since inception lol thanks guys
I got my Cleric pre1.5 in no time whatsoever
But the tracking issues with Shaman ,1.0 and 1.5 are just impossible.
I tried it on my Berserker and it wouldn't run.
I've gotten pretty far into the Bard pre 1.5 over half way.. with the tracking issues I have to /quit
Then restart the game me over beyond whatever sticking point and restart the Lua
Even with the trouble I'm having I can see getting Epics. So I love this. Just wish the tracking was a little better if that is even possible. Maybe I'm doing something wrong.
But the tracking issues with Shaman ,1.0 and 1.5 are just impossible.
I tried it on my Berserker and it wouldn't run.
I've gotten pretty far into the Bard pre 1.5 over half way.. with the tracking issues I have to /quit
Then restart the game me over beyond whatever sticking point and restart the Lua
Even with the trouble I'm having I can see getting Epics. So I love this. Just wish the tracking was a little better if that is even possible. Maybe I'm doing something wrong.
I was running the Shaman epic 1.0. I ran into a few spots where I ran into problems:
1. In the sparkling gem part of the quest, a wandering spirit gets Marrs Promise, Woe, and Envy. Somehow, I didn't have Envy. All 3 must be traded in at the same time. Manually, I went back to kill Glarion to loot Envy and did the turn in.
2. In the City of Mist, where you must kill Lord Ghiosk. You need to kill at a Black Reaver and need the key or a rog to pick the door. I had the key but it didn't try the key to get through door. I then had a rog pick the door but it didn't advance through the door.
3. Loot Students log in CoM. Dropped by spectral courier who spawns around the "stables" area. All the place holders are in the stable area. The shaman was wondering all around the castle killing npc. I think the cwtn plugin was set for hunter tank and the radius is set too large. The shman kept falllng into a pool at the center of the CoM. My mesh may need to be updated but the point is it shouldn't be in that area for the Student log.
4. The checklist written as part of the Shaman is a good example of the type of information on each step which the Lua module should give. Towards the end it got too difficult to figure out what the module needed to do and what the quest required. I finished the last part of the quest manually.
As a beta it is great and holds a lot of promise. I'm going to try the 1.5 and 2.0 shaman epic
1. In the sparkling gem part of the quest, a wandering spirit gets Marrs Promise, Woe, and Envy. Somehow, I didn't have Envy. All 3 must be traded in at the same time. Manually, I went back to kill Glarion to loot Envy and did the turn in.
2. In the City of Mist, where you must kill Lord Ghiosk. You need to kill at a Black Reaver and need the key or a rog to pick the door. I had the key but it didn't try the key to get through door. I then had a rog pick the door but it didn't advance through the door.
3. Loot Students log in CoM. Dropped by spectral courier who spawns around the "stables" area. All the place holders are in the stable area. The shaman was wondering all around the castle killing npc. I think the cwtn plugin was set for hunter tank and the radius is set too large. The shman kept falllng into a pool at the center of the CoM. My mesh may need to be updated but the point is it shouldn't be in that area for the Student log.
4. The checklist written as part of the Shaman is a good example of the type of information on each step which the Lua module should give. Towards the end it got too difficult to figure out what the module needed to do and what the quest required. I finished the last part of the quest manually.
As a beta it is great and holds a lot of promise. I'm going to try the 1.5 and 2.0 shaman epic
Running Lua script 'epiclaziness' with PID 3
[Epic Laziness] if you encounter any nav mesh issues please ensure you are using the latest mesh from https://github.com/yb-f/meshes
[Epic Laziness] Settings saved.
...Installed Games\Redguides\Next\Lua\epiclaziness\init.Lua:182: attempt to index a nil valuestack traceback: ...Installed Games\Redguides\Next\Lua\epiclaziness\init.Lua: in function 'step_overview' ...Installed Games\Redguides\Next\Lua\epiclaziness\init.Lua:731: in main chunk
Ending Lua script 'epiclaziness' with PID 3 and status -1
I encountered the above error on a different computer with the latest version of epiclaziness. I'll try it on my other computer where it worked previously and see if its the new version.
Epiclaziness was just installed on this computer and it needed to load three modules. The first module was sqllite. The second module was Luasocket. I'm not sure about a third.
Tried it on my other computer the version was from 4/11 6:45. I updated the version and it started to load modules just like the first. I got a similar error message and stopped the module. I started it again and it continued loading the modules. It finished and worked fine. This computer had a version working previous the 4/11 version. It worked. The computer I loaded the module for the first time is missing something.
[Epic Laziness] if you encounter any nav mesh issues please ensure you are using the latest mesh from https://github.com/yb-f/meshes
[Epic Laziness] Settings saved.
...Installed Games\Redguides\Next\Lua\epiclaziness\init.Lua:182: attempt to index a nil valuestack traceback: ...Installed Games\Redguides\Next\Lua\epiclaziness\init.Lua: in function 'step_overview' ...Installed Games\Redguides\Next\Lua\epiclaziness\init.Lua:731: in main chunk
Ending Lua script 'epiclaziness' with PID 3 and status -1
I encountered the above error on a different computer with the latest version of epiclaziness. I'll try it on my other computer where it worked previously and see if its the new version.
Epiclaziness was just installed on this computer and it needed to load three modules. The first module was sqllite. The second module was Luasocket. I'm not sure about a third.
Tried it on my other computer the version was from 4/11 6:45. I updated the version and it started to load modules just like the first. I got a similar error message and stopped the module. I started it again and it continued loading the modules. It finished and worked fine. This computer had a version working previous the 4/11 version. It worked. The computer I loaded the module for the first time is missing something.
Last edited:
Gnome-eater
Active member
if rogue 1.5 and 2.0 are added..I might even start playing again. "Epic" program, nonetheless. I commend you.
- Seller
- #386
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.
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.
@Lisie Just want to say thank you. I have completed many of the ones you have done so far, with some bumps obviously, but can see as fixes happen. Love it.
With your work, I have
Bard pre1.5, 1.5 and 2.0 done. Working on a 2nd bard now.
Bst about to start on a new bst.
SK pre1.5, 1.5 and 2.0 done. Working on a 2nd SK now.
Shm pre1.5, 1.5 and 2.0
Its a fun ride. Will be happy to do more soon.
With your work, I have
Bard pre1.5, 1.5 and 2.0 done. Working on a 2nd bard now.
Bst about to start on a new bst.
SK pre1.5, 1.5 and 2.0 done. Working on a 2nd SK now.
Shm pre1.5, 1.5 and 2.0
Its a fun ride. Will be happy to do more soon.
- Seller
- #389
Lisie updated Epic Laziness with a new update entry:
04/13/2024
Read the rest of this update entry...
04/13/2024
CommitsRead the rest of this update entry...
Back again and first the good My 2nd Sk and clr have both completed their 2.0s Thank you!
now working on my Bst 1.5 and I'm in Gulf of Gunthak for step 117 farming for Swirling Feral Essence there are 3 ph camps that you set us up between nice parking using CTWN im switched to hunter tank. What im observing is we are not killing the Ph's. ive tinkered with the camp radius & pull radius increasing them both to 999 even and got nothing what I did find is if I returned the other settings back to yours and increase the pullzhigh/pullzlow options to 100 each I now am able to "look away" while the ph's are taken down.
also may want to have them cast a shrink when they zone to Blackburrow for step 170 (jagged pine forest) taller classes get hung up on a lower wall in the tunnels.
now working on my Bst 1.5 and I'm in Gulf of Gunthak for step 117 farming for Swirling Feral Essence there are 3 ph camps that you set us up between nice parking using CTWN im switched to hunter tank. What im observing is we are not killing the Ph's. ive tinkered with the camp radius & pull radius increasing them both to 999 even and got nothing what I did find is if I returned the other settings back to yours and increase the pullzhigh/pullzlow options to 100 each I now am able to "look away" while the ph's are taken down.
also may want to have them cast a shrink when they zone to Blackburrow for step 170 (jagged pine forest) taller classes get hung up on a lower wall in the tunnels.
Last edited:
Logged in my BL this smorning and tried to start his Lua and got the following:
Running Lua script 'epiclaziness' with PID 3
[Epic Laziness] if you encounter any nav mesh issues please ensure you are using the latest mesh from https://github.com/yb-f/meshes
[Epic Laziness] Settings saved.
D:\REDGUIDES\Lua\EPICLAZINESS\INIT.Lua:119: attempt to compare num with NIL
stack traceback
D:\REDGUIDES\Lua\EPICLAZINESS\INIT.Lua: in main chunk
Worked fine last night. restarted and updated the Lua and got the same result.
Running Lua script 'epiclaziness' with PID 3
[Epic Laziness] if you encounter any nav mesh issues please ensure you are using the latest mesh from https://github.com/yb-f/meshes
[Epic Laziness] Settings saved.
D:\REDGUIDES\Lua\EPICLAZINESS\INIT.Lua:119: attempt to compare num with NIL
stack traceback
D:\REDGUIDES\Lua\EPICLAZINESS\INIT.Lua: in main chunk
Worked fine last night. restarted and updated the Lua and got the same result.
- Seller
- #392
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?
- Seller
- #394
Alright I will see what I can find. Unfortunately I have made major changes since the last version that was uploaded so the line numbers are skewed quite a bit.
- Seller
- #395
I see the issue. I changed the versioning system in the last 20ish minutes. A new version should hit the site in about 15-20 minutes that will correct the issue. Sorry about that!
- Seller
- #396
I will add something to adjust the zhigh and zlow settings on startup. When I tested this I had increased them elsewhere for testing something and forgot to remember I had done so.
As for the Blackburrow step. I have some code that someone sent me to use MQ2Autosize when the script becomes stuck, either because we are too small to get out of water, or to large for a passageway. I have unfortunately not had the opportunity to implement it yet.
- Seller
- #397
Lisie updated Epic Laziness with a new update entry:
04/13/2024
Read the rest of this update entry...
04/13/2024
Read the rest of this update entry...
- Seller
- #398
Lisie updated Epic Laziness with a new update entry:
Manual update
Read the rest of this update entry...
Manual update
Read the rest of this update entry...
Good Morning!
Bard 1.5
Dire killing steps: Upon zone in, would be nice, dependent on level, to see weapons offloaded from hand slots before arriving to the mob, or at least mentioning it in MQ window that it will happen.
I know this is more user vanity/sanity check, but I remember reading you made the change but upon seeing the first dire I was sweating it to see what would happen. First two Dires was flawless.
Third one was mostly flawless until one 'unlucky' bit of damage:
As I arrived to the Kodiak, I did see the weapons disappear from both hands, but I had my bag open and never saw them go into the bag. As you can see in the pic, I was slash and pierce up top, then punch and an unlucky kick of 30K and at the end, back to pierce and slash. It was dying fine at the beginning and I saw the hp going well, then it insta died and left me alone in the woods for 6 hours to try again.
Another issue, When traveling through The Warrens, there is a water area for a very short bit we fall into and have to get back out of. Most characters get stuck upon the get back out part. This would apply to any epics traveling through Warrens.
Bard 1.5
Dire killing steps: Upon zone in, would be nice, dependent on level, to see weapons offloaded from hand slots before arriving to the mob, or at least mentioning it in MQ window that it will happen.
I know this is more user vanity/sanity check, but I remember reading you made the change but upon seeing the first dire I was sweating it to see what would happen. First two Dires was flawless.
Third one was mostly flawless until one 'unlucky' bit of damage:
As I arrived to the Kodiak, I did see the weapons disappear from both hands, but I had my bag open and never saw them go into the bag. As you can see in the pic, I was slash and pierce up top, then punch and an unlucky kick of 30K and at the end, back to pierce and slash. It was dying fine at the beginning and I saw the hp going well, then it insta died and left me alone in the woods for 6 hours to try again.
Another issue, When traveling through The Warrens, there is a water area for a very short bit we fall into and have to get back out of. Most characters get stuck upon the get back out part. This would apply to any epics traveling through Warrens.
- Seller
- #400
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. I will look into this and see if I can clear it up.
As for the unlucky kicks. They are the bane of my existence. I am probably eventually going to have to switch to higher level bards memming a lower level (80ish) dot song, and facing away from the mob to prevent 125's one shot riposte kicking the mobs to death.