• 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
Easy.lua

Release Easy.lua BETA v9.8

No permission to download
Status
Not open for further replies.
I have actually seen this error before and thought I had taken care of it. It shouldn't matter what level you are. This is a bad check on the power source.

Ok haha I wanted to be sure it wasnt just me being an idiot.
 
giving it a shot right now...

..... baddaboom , baddabing!

Thanks!
 
new request for modification: please consider to check also for invis b4 casting anything like: mq.TLO.Me.Invis()
[CODE title="checkInvis"]if mq.TLO.FindItem(v)() ~= nil and not mq.TLO.Me.Invis() and not mq.TLO.Me.Moving() and mq.TLO.FindItem(v).TimerReady() == 0 and mq.TLO.Me.FreeInventory() >= 1 and not mq.TLO.Me.Combat() and not mq.TLO.Me.Hovering() then[/CODE]

While running for quests it happens, that I come to an halt even in unfriendly quaters to check, where to head next.
If at this moment the summoning of a cauldron would start, it could end catastrophic.
 
new request for modification: please consider to check also for invis b4 casting anything like: mq.TLO.Me.Invis()
[CODE title="checkInvis"]if mq.TLO.FindItem(v)() ~= nil and not mq.TLO.Me.Invis() and not mq.TLO.Me.Moving() and mq.TLO.FindItem(v).TimerReady() == 0 and mq.TLO.Me.FreeInventory() >= 1 and not mq.TLO.Me.Combat() and not mq.TLO.Me.Hovering() then[/CODE]

While running for quests it happens, that I come to an halt even in unfriendly quaters to check, where to head next.
If at this moment the summoning of a cauldron would start, it could end catastrophic.
Yup, Yup. Looks like I missed the invis check on that one. Thanks for the eye.

Put invis check on the dispensers, forgot to check the cauldron. :)
 
new suggestion to make personalisation easier:
in order to make the settings for peoples own defaults an easy task you may could add 1 parameter for each checkbox at the top of the file like:

[CODE title="Options parameter"]--Default Customized Settings--
local eat_level = 3500
local drink_level = 3500
local get_drunk = 180
local cookie_to_summon = 20
local spiced_tea_to_summon = 20
local warm_milk_to_summon = 20
local brells_brew_to_summon = 20
local cooked_turkey_to_summon = 20
local scoot_distance = 500
local alert_distance = 500
local toon_assist_pct_on = 98
local toon_assist_pct_off = 90
local toon_assist_target_dist = 15
local parcel_zone = 737

--Options --
local bRoguePoison = true -- new parameter for the checkbox[/CODE]

further down you may use this parameter to set the default for this checkbox like:

[CODE title="Rogue Poison UI"] name = 'ROG Poison',
helper = 'Summons Poison Using Leg Slot (Rogue Only)',
selected = bRoguePoison,
action = RoguePoison[/CODE]

this would allow to save all parameters into an external file containing all personal perferences,
After any update of Easy.Lua ,one could easily paste his own values at the head of the Lua and would be ready to go.
Would make it much easier, to get the defaults set to the own preferences.
 
new suggestion to make personalisation easier:
in order to make the settings for peoples own defaults an easy task you may could add 1 parameter for each checkbox at the top of the file like:

[CODE title="Options parameter"]--Default Customized Settings--
local eat_level = 3500
local drink_level = 3500
local get_drunk = 180
local cookie_to_summon = 20
local spiced_tea_to_summon = 20
local warm_milk_to_summon = 20
local brells_brew_to_summon = 20
local cooked_turkey_to_summon = 20
local scoot_distance = 500
local alert_distance = 500
local toon_assist_pct_on = 98
local toon_assist_pct_off = 90
local toon_assist_target_dist = 15
local parcel_zone = 737

--Options --
local bRoguePoison = true -- new parameter for the checkbox[/CODE]

further down you may use this parameter to set the default for this checkbox like:

[CODE title="Rogue Poison UI"] name = 'ROG Poison',
helper = 'Summons Poison Using Leg Slot (Rogue Only)',
selected = bRoguePoison,
action = RoguePoison[/CODE]

this would allow to save all parameters into an external file containing all personal perferences,
After any update of Easy.lua ,one could easily paste his own values at the head of the lua and would be ready to go.
Would make it much easier, to get the defaults set to the own preferences.
I really didn't expect the script to evolve as much as it did with custom settings. As much as I dislike having a separate ini file for 30 plus toons for every macro and script that I run. I may look at the option.

Now after re reading your post. lol I see you meant like one ini file that saves all player data / settings.
 
I really didn't expect the script to evolve as much as it did with custom settings. As much as I dislike having a separate ini file for 30 plus toons for every macro and script that I run. I may look at the option.
How about 1 master ini file like MQ2FeedME.ini, it only lists each character name there with settings. Easy to also copy/paste a new character in that file with the same settings as another.
 
How about 1 master ini file like MQ2FeedME.ini, it only lists each character name there with settings. Easy to also copy/paste a new character in that file with the same settings as another.
Yah, I need coffee, I just realized what the post was about. haha Got kids running around stuff going on, breaking my train of thought.
 
I really didn't expect the script to evolve as much as it did with custom settings. As much as I dislike having a separate ini file for 30 plus toons for every macro and script that I run. I may look at the option.

Now after re reading your post. lol I see you meant like one ini file that saves all player data / settings.
An INI file would be great. Maybe not easy to implement.

An easier improvement would be, to swap the "true" and "false" in the UI-part of the source code with parameters defined at the top of the source-code. In my example I added "local bRoguePoison = true" at the top of the source and exchanged "selected = true," with "selected = bRoguePoison,".
Doing it that way, all personal default-values are defined at the top of "Easy.Lua" which would make it much easier to save the own preferences and paste it into the new "Easy.Lua" after an update was downloaded.

An INI saving the preferred values per character for my feeling would be even more comfortable. As I can't estimate the work involved doing it, I wasn't keen to ask for a modification of this type.
 
Cannonballdex updated Easy.lua with a new update entry:

Missed Cauldron/Forage Update

Files moved to the MQNext\Lua\Easy folder.
init.Lua
LIP.Lua
and
First run will create the Easy.ini file with default settings.
A settings section will be created for each toon that runs /Lua run Easy
Any changes made in game using the UI will not be saved in the Easy.ini file

Added Changes for running Cauldron and Forage at the same time.

Read the rest of this update entry...
 
Looks pretty cool @Cannonballdex but the GM part I would remove as it would only work if the GM's want to or forget to hide.
 
Looks pretty cool @Cannonballdex but the GM part I would remove as it would only work if the GM's want to or forget to hide.
This is true. Nothing will detect a GM that is in stealth mode, however to blatantly run automation when a GM is in plain detection mode, would just be kind of foolish. The setting isn't by any means a saving grace, just an alert that says hey there is a GM in zone. Like the other settings, they will only work on a true / false statement. If you select summon cookies and you don't have a cookie dispenser, then this option wouldn't work.
 
This is true. Nothing will detect a GM that is in stealth mode, however to blatantly run automation when a GM is in plain detection mode, would just be kind of foolish. The setting isn't by any means a saving grace, just an alert that says hey there is a GM in zone. Like the other settings, they will only work on a true / false statement. If you select summon cookies and you don't have a cookie dispenser, then this option wouldn't work.
Two days (or so) after NoS went live, I was exploring and went fishing, Easy went nuts on the header letting me know a GM was near. I was logged off and later went back and GM was still there. It was like 10 my time, so way past California 9-5 hours..hehe. I wondered if he was working late or running a 'bot' of his own monitoring the new expansion. I came back the next day, he was gone. :)
 
Two days (or so) after NoS went live, I was exploring and went fishing, Easy went nuts on the header letting me know a GM was near. I was logged off and later went back and GM was still there. It was like 10 my time, so way past California 9-5 hours..hehe. I wondered if he was working late or running a 'bot' of his own monitoring the new expansion. I came back the next day, he was gone. :)
they work from home also and don't do 9 to 5 lol


also devs are marked as GMs and they are always around working on the game.
 
they work from home also and don't do 9 to 5 lol


also devs are marked as GMs and they are always around working on the game.
Gotcha, this one just happened to be visible in a new zone, and rare nowadays for me to see any. Anyways, CWTNfish and EasyShare both did their jobs and let me know HEY Dumdum, gm over there, stop your autobot fishing and....ROLL OUT
 
That's Awesome. That means it worked? As mentioned there is never a fail safe when running any script, but it's always nice to know when DB is around if possible. I always try to add some type of player or gm detection to scripts, it really can't hurt anything. Thanks for sharing.
 
If anyone else actually uses this script and has any issues, please let me know. I usually don't take the time to test every possible scenario when I release an update.
You would be surprised how well a script works when you attune it to your own style of play only to have someone else try it and it breaks. Instead of speaking up or saying something about it, they just don't use it and move on to the next script.
I'm not much of a coder / script writer, but I love making them work. I would encourage anyone else that tinkers with scripts to share their work and collaborate with community. It's all about having fun and doing what we love to do.
Any feedback or suggestions are welcome.
 
Cannonballdex updated Easy.lua with a new update entry:

Clean Up

Cleaned up some duplicate code and did some alignment.
Moved the ICONS to a file in the Easy\lib folder
Moved the LIP.lua file to the Easy\lib folder
You can leave or delete the LIP.lua file from the Easy folder

I believe if you use the updater then
You should have these files in these folders

MQNext\Lua\Easy\init.lua -- Main file
MQNext\Lua\Easy\Easy.ini -- Settings file

MQNext\Lua\Easy\lib\icons.lua
MQNext\Lua\Easy\lib\LIP.lua

Read the rest of this update entry...
 
Have not updated to the version from your post above this, but for feedback:
Ini is working great, kept my individual settings per 12 different characters, was nice to see a few things happen tht I do by hand sometimes like deleting rods on War (/i know I can block the spell) but EasyLua makes it great. On one group, the need for a merc to repop has worked very nice. Great to see the merc pop and get to work without me needing to say. With Kiss, I used that and it works, but this is with a all CWTN group, so nice addition tool ! Thanks CBD
 
Have not updated to the version from your post above this, but for feedback:
Ini is working great, kept my individual settings per 12 different characters, was nice to see a few things happen tht I do by hand sometimes like deleting rods on War (/i know I can block the spell) but EasyLua makes it great. On one group, the need for a merc to repop has worked very nice. Great to see the merc pop and get to work without me needing to say. With Kiss, I used that and it works, but this is with a all CWTN group, so nice addition tool ! Thanks CBD
I agree, love the merc stuff, never knew before but if a zone gets full they will start de-spawning mercenaries. Nice to have the Pop Merc up as well so when zone population goes down it will Pop a merc. The lazy features are nice to, save a few plat when you get back to a safe zone and forget to turn off a merc. Personally I don't think you should be charged for a mercenary in a safe zone, but oh well.
 
For my feeling the "/autoinventory" every second is too frequent. The default loop-delay is set to 1000. Its hard to hand over items to npcs or pc or shuffle items around in inventory.
Wouldn't it be sufficient to set it to 5000, or possible to add a parameter for "cycletime" to be able to set a personalized delay-time?
 
For my feeling the "/autoinventory" every second is too frequent. The default loop-delay is set to 1000. Its hard to hand over items to npcs or pc or shuffle items around in inventory.
Wouldn't it be sufficient to set it to 5000, or possible to add a parameter for "cycletime" to be able to set a personalized delay-time?
When you have so many things going on at once, it's hard to really set a delay sufficient for everything. I would use the pause on the script before trying to actually grab items from your bag. Having a 5 or 10 second delay would leave stuff piling up on your cursor, if you forage two items, then have cauldron or poison summon added on that food and drink clickies, and not to mention loot items or other stuff.
 
Cannonballdex updated Easy.lua with a new update entry:

Updates

Changed the way the script summons things. This should give a little bit more flexibility picking up items from inventory. The script will only try to inventory items when it calls for actually summoning an item or after foraging.
Put several more checks in for almost all of the functions.
Should no longer try to do things while in combat or hovering (dead) or invisible.

Read the rest of this update entry...
 
For next update. If you have 2 or 5 krono in your inventory the Krono: will not show unless you change
line 2082
Code:
elseif  mq.TLO.Me.Krono() < 6 and  mq.TLO.Me.Krono() > 1 then
 
Getting used to the "pause"-button the cycletime isn't anymore an issue for me. In the meantime, this nice tool got the "always"-up status and along with "Buttonmaster" "LEM" and "Magellan" its loaded at login on all toons. @Cannonballdex: the improvements of the last days have been great.
 
Getting used to the "pause"-button the cycletime isn't anymore an issue for me. In the meantime, this nice tool got the "always"-up status and along with "Buttonmaster" "LEM" and "Magellan" its loaded at login on all toons. @Cannonballdex: the improvements of the last days have been great.
Same must haves I load up, Buttonmaster and Magellan (customized hybrid with easynav built in) and growing fond of QuickHud too. Haven't got around to LEM yet.
 
Prelim testing. Throwing around the idea of adding a Burn routine in the Class tab for each class. Initial testing shows that the WarBurn pretty much takes over all DPS while activated. Just needs a little timing adjustment to slow it down a hair.
 

Attachments

  • Untitled.jpg
    Untitled.jpg
    131.1 KB · Views: 4
Cannonballdex updated Easy.lua with a new update entry:

WAR Burn

Added an option under CLASS for WAR Burn. This option is currently for a level 120 warrior with AA and Abilities. This is really in the testing phase and depending on how things go, may add lower level capabilities.

This option pretty much burns all of your AA and Abilities and Combat Abilities with a few checks.

First run will create an additional default setting war_burn = false
If you have already created an ini file you and you want to save this setting, you will need to add this to...

Read the rest of this update entry...
 
Hey CBD, question about user settings for this.. I've been using this now for the better part of the week, and its working really nicely for me. One thing I notice though, is that for some reason, when i start it up when first logging on and into a toon that I've already previously used this before (I see the settings file thats created with the toon name and whats set on/off) , but it seems like when I first start the Lua (/Lua run easy) it reverts to default settings, and not the ones I toggled previously..

Is there a command to save my settings or maybe to call the ini when starting it up? I didnt see anything in the discussion thread about this, and nothing in the instructions, so I thought I'd reach out to you.

Cheers,
Lordeth
 
Hey CBD, question about user settings for this.. I've been using this now for the better part of the week, and its working really nicely for me. One thing I notice though, is that for some reason, when i start it up when first logging on and into a toon that I've already previously used this before (I see the settings file thats created with the toon name and whats set on/off) , but it seems like when I first start the lua (/lua run easy) it reverts to default settings, and not the ones I toggled previously..

Is there a command to save my settings or maybe to call the ini when starting it up? I didnt see anything in the discussion thread about this, and nothing in the instructions, so I thought I'd reach out to you.

Cheers,
Lordeth
Go in to the Easy.ini file and save the settings there. Then when you run easy.Lua those settings will be used.
 
Release Easy.lua
Status
Not open for further replies.

Users who are viewing this thread

Back
Top
Cart