• 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
Join us with Level 2 access RedCents
Overview Commands Instructions Updates (102) Reviews (4) History Discussion
Status
Not open for further replies.
Cannonballdex updated Easy.lua with a new update entry:

Update

Adjusted delay back down on the Forage. Can confirm this is checking the config file and when double items are foraged. If you have kiss assist running, ninjaloot might be dropping items from cursor. Any kind of other looting program, autoloot, other loot programs may effect the outcome.
Click to expand...

Read the rest of this update entry...
 
I set up some items in the config and had two double forages in a row.
Code: 
--Forage Items to Destroy
_C.FORAGE_DESTROY = {
    "Twilight Orchid",
    "Flarefire Seeds"
}
--Forage Items to Keep
_C.FORAGE_KEEP = {
    "Keep This",
    "Spiritual Luclin Mushroon",
    "Luclinite Laced Larkspur",
    "Luclinite Laced Delphinium",
    "Luclinite Laced Caldium"
}
Untitled.jpg
 
Thought it would be a cool idea if you could add a Bind Wound click box under the forage box . If you have a player targeted and their health drops to the right amount to be able to bind wound then it would start doing that . And then a second option where it would just bind wound on your toon doing that skill if no target is targeted
 
afortner87 said:
Thought it would be a cool idea if you could add a Bind Wound click box under the forage box . If you have a player targeted and their health drops to the right amount to be able to bind wound then it would start doing that . And then a second option where it would just bind wound on your toon doing that skill if no target is targeted
Click to expand...
It is possible, however this would consist of pausing everything else that might interfere with performing bind wound, like any macro running or scripts running that would cause you to navigate or do something else. I did add a begging tab, still working on the details of the Bind Wound.

Do we want to use it while camping mobs, use on ourself, the group or just use it for training purposes.
 
Cannonballdex said:
It is possible, however this would consist of pausing everything else that might interfere with performing bind wound, like any macro running or scripts running that would cause you to navigate or do something else. I did add a begging tab, still working on the details of the Bind Wound.

Do we want to use it while camping mobs, use on ourself, the group or just use it for training purposes.
Click to expand...
I would say probably if u made the bind wound to have it check the group for out of combat status and then do it on group members or self .
 
Cannonballdex updated Easy.lua with a new update entry:

Update

Added the options Begging and Bind Wound.

Begging. Be careful who you are begging. It can get you axed.

Bind wound probably needs tested and feedback.

In theory, if you have bandages and you or a group member drops below 90% hp you will pause macro and bind the toon until over 90% or you get xtarget aggro. I am sure something can go wrong with this if you are running any other LUA scripts or Plugins. Use the Bind Wound function at your own risk.

Also, added checks for Burn function to...
Click to expand...

Read the rest of this update entry...
 
brcyklopz said:
i mean it wont let anything other windows in game open on top of it ... its always ontop
Click to expand...
That is how Lua windows work. The windows are not an actual part of the GUI but an overlay window so to speak. If you had two monitors you could drag it to another monitor. :)
 
Cannonballdex said:
That is how LUA windows work. The windows are not an actual part of the GUI but an overlay window so to speak. If you had two monitors you could drag it to another monitor. :)
Click to expand...
Hey dude, I hate to break it to you but Lua isn’t an acronym, so let’s not scream it in all caps. Also, while I’m here, Lua also doesn’t make windows - That’s ImGui (which actually is an acronym)

The more you know…!
 
brainiac said:
Hey dude, I hate to break it to you but lua isn’t an acronym, so let’s not scream it in all caps. Also, while I’m here, lua also doesn’t make windows - That’s ImGui (which actually is an acronym)

The more you know…!
Click to expand...
That's nice to know. Thanks for clarification.
 
@Cannonballdex hey cbd - your update has icons.Lua but it is already a part of MQ core
 
CWTN/Sic's MQ2Mage, MQ2Enchanter, etc now remove Easy. It's in the output window about removing it. Just thought you should know.

easy.Lua conflicts with this plugin. Unloading it automatically any time it is loaded.
 
Last edited by a moderator:
eye said:
CWTN/Sic's MQ2Mage, MQ2Enchanter, etc now remove Easy. It's in the output window about removing it. Just thought you should know.

easy.lua conflicts with this plugin. Unloading it automatically any time it is loaded.
Click to expand...
Haven't had any complaints about any conflicts. But you can easily rename the easy folder to something else and edit init file where it says easy for config files to your new name.
 
Cannonballdex said:
Haven't had any complaints about any conflicts. But you can easily rename the easy folder to something else and edit init file where it says easy for config files to your new name.
Click to expand...
well there are, and there are conflicts.
please be respectful and don't ask people to that.
like actually seriously don't.
 
eye said:
CWTN/Sic's MQ2Mage, MQ2Enchanter, etc now remove Easy. It's in the output window about removing it. Just thought you should know.

easy.lua conflicts with this plugin. Unloading it automatically any time it is loaded.
Click to expand...
yeah unfortunately when things are willy nilly slapped into a utility that does so many different things they can cause conflicting behavior, like burns, aa usage, and other combat stuff, it causes issues. so same as mq2melee, mq2afnuke, mq2combat, and any other future conflicting things, it conflicts, and we unload them for the same reason.

Cannonballdex said:
Yah ok. Boss man.
Click to expand...
k
 
Sic said:
yeah unfortunately when things are willy nilly slapped into a utility that does so many different things they can cause conflicting behavior, like burns, aa usage, and other combat stuff, it causes issues. so same as mq2melee, mq2afnuke, mq2combat, and any other future conflicting things, it conflicts, and we unload them for the same reason.


k
Click to expand...
I guess I was looking more at what the user would want to do, I had no idea it was interfering with the plugin. My bad.
 
Cannonballdex said:
I guess I was looking more at what the user would want to do, I had no idea it was interfering with the plugin. My bad.
Click to expand...
"ya ok. boss man" certainly doesn't sound like that, and it is your utility, so you do you. zero reasons to be snarky to me about it. I'm not going to ask you not to do something, but I'm going to manage my (and chat's) utility as best we can, which means unloading conflicts.
 
Sic said:
"ya ok. boss man" certainly doesn't sound like that, and it is your utility, so you do you. zero reasons to be snarky to me about it. I'm not going to ask you not to do something, but I'm going to manage my (and chat's) utility as best we can, which means unloading conflicts.
Click to expand...
That is fine, but you don't have to come into my utility and start acting that way towards me. Have a nice day.
 
Cannonballdex said:
That is fine, but you don't have to come into my utility and start acting that way towards me. Have a nice day.
Click to expand...
asking you not to try and circumvent actions i'm taking in my utility is "acting that way"? alright, bud.
 
eye said:
CWTN/Sic's MQ2Mage, MQ2Enchanter, etc now remove Easy. It's in the output window about removing it. Just thought you should know.

easy.lua conflicts with this plugin. Unloading it automatically any time it is loaded.
Click to expand...
Ok. Thanks for heads up.
 
Not sure if this is the right place to ask but since the topic here right now-
Will there be a way to automatically reload easy.Lua after it’s unloaded or will there be a way to choose if won’t be unloaded by Sic and CWTN’s plug-in?
I don’t use easy for anything that conflicts with CWTN. Mainly mod rods, the new plat count, and some other minor things. But CWTN for all things combat related.

Thanks to all three for what y’all provide.

BB~
 
I really like Easy. I use it for the dispenser action, force feed, Dannet, everything zone information. I wonder if the major objection is about the burn functions, Class tab, (combat?). I wouldn't mind a version of Easy without the Class tab. Account, Zone, Clickies, Hunter, and Fav tab seem to be clean? In options tab, I would think maybe begging and bind wound could cause a conflict but unlikely. Camp tab is clean. The merc tab may be in conflict. Maybe a checklist of items could be agreed upon?

Vote with your feet. Of my 16 toons only 3 don't use the CMTN/Sic plugins. I like my wiz though. Great job guys.

By the way, I continue to crash Easy when I select account tab on some of my toons. The only difference is the one with a username of 10 characters works fine and the one with 15 crashes (the name is a random combination of upper and lower case characters).
 
BlueBug said:
Not sure if this is the right place to ask but since the topic here right now-
Will there be a way to automatically reload easy.lua after it’s unloaded or will there be a way to choose if won’t be unloaded by Sic and CWTN’s plug-in?
I don’t use easy for anything that conflicts with CWTN. Mainly mod rods, the new plat count, and some other minor things. But CWTN for all things combat related.

Thanks to all three for what y’all provide.

BB~
Click to expand...
You won't be able to reload Easy.Lua if another script is unloading it. As for the choice, you would need to get that information from the script or plugin forum.
 
eye said:
I really like Easy. I use it for the dispenser action, force feed, Dannet, everything zone information. I wonder if the major objection is about the burn functions, Class tab, (combat?). I wouldn't mind a version of Easy without the Class tab. Account, Zone, Clickies, Hunter, and Fav tab seem to be clean? In options tab, I would think maybe begging and bind wound could cause a conflict but unlikely. Camp tab is clean. The merc tab may be in conflict. Maybe a checklist of items could be agreed upon?

Vote with your feet. Of my 16 toons only 3 don't use the CMTN/Sic plugins. I like my wiz though. Great job guys.

By the way, I continue to crash Easy when I select account tab on some of my toons. The only difference is the one with a username of 10 characters works fine and the one with 15 crashes (the name is a random combination of upper and lower case characters).
Click to expand...
The scripted was designed to give the user a choice of what functions they wanted to perform in one control panel so to speak. Not much different than downloading 100 Lua scripts and then running them one by one as you desired.
The problem that can arise when running many scripts at one time is they can conflict with each other.
My intention was to create a script that even if you checked every single box in every tab it would play nice together without conflict. Easy.Lua only initiates actions based upon you the user selecting a check box.
Easy.Lua does not have the ability to predict what other plugins, macros or Lua scripts you have running and therefore may cause unintended conflicts.
If you get any errors or conflicts within Easy.Lua feel free to post them and I can address the issues to the best of my ability.

If you could send me the error you get with the name crash I can look into it. The name with upper and lower case characters? Is this on a test or live server?
 
Cannonballdex said:
The scripted was designed to give the user a choice of what functions they wanted to perform in one control panel so to speak. Not much different than downloading 100 lua scripts and then running them one by one as you desired.
The problem that can arise when running many scripts at one time is they can conflict with each other.
My intention was to create a script that even if you checked every single box in every tab it would play nice together without conflict. Easy.lua only initiates actions based upon you the user selecting a check box.
Easy.lua does not have the ability to predict what other plugins, macros or lua scripts you have running and therefore may cause unintended conflicts.
If you get any errors or conflicts within Easy.lua feel free to post them and I can address the issues to the best of my ability.

If you could send me the error you get with the name crash I can look into it. The name with upper and lower case characters? Is this on a test or live server?
Click to expand...
I think a solution here would be to de-conflict the two resources in a way that leaves the features in place, but where it disables them intelligently. For example, if you were to check to see if a specific class had their class plugin loaded (A Shadow Knight running MQ2Eskay for example) , you could disable the conflicting features preventing the two things from fighting over who's going to do what when. With that change the restriction could be lifted because the conflict is self solving.

One way would be to try the following. Pardon my lack of Lua knowledge as I don't know what you can and cannot do in Lua, so I'd ask you interpret the information and convert for the language you are using.

Code: 
bool IsClassPluginLoaded() {
    switch (${Me.Class.ID}) {
    
        case 1://Warrior
        return !${Plugin[MQ2War].IsLoaded};
        break;
    
        case 2://Cleric
        return !${Plugin[MQ2Cleric].IsLoaded};
        break;
    
        case 3://Paladin
        return !${Plugin[MQ2Paladin].IsLoaded};
        break;
    
        case 4://Ranger
        return !${Plugin[MQ2Ranger].IsLoaded};
        break;
    
        case 5://Shadow Knight
        return !${Plugin[MQ2Eskay].IsLoaded};
        break;
    
        case 6://Druid
        return !${Plugin[MQ2Druid].IsLoaded};
        break;
    
        case 7://Monk
        return !${Plugin[MQ2Monk].IsLoaded};
        break;
    
        case 8://Bard
        return !${Plugin[MQ2Bard].IsLoaded};
        break;
    
        case 9://Rogue
        return !${Plugin[MQ2Rogue].IsLoaded};
        break;
    
        case 10://Shaman
        return !${Plugin[MQ2Shaman].IsLoaded};
        break;
    
        case 11://Necromancer
        return !${Plugin[MQ2Necro].IsLoaded};
        break;
    
        case 12://Wizard
        return !${Plugin[MQ2Wizard].IsLoaded};
        break;
    
        case 13://Magician
        return !${Plugin[MQ2Mage].IsLoaded};
        break;
    
        case 14://Enchanter
        return !${Plugin[MQ2Enchanter].IsLoaded};
        break;
    
        case 15://Beastlord
        return !${Plugin[MQ2Bst].IsLoaded};
        break;
    
        case 16://Berserker
        return !${Plugin[MQ2Berzerker].IsLoaded};
        break;
    }
}

This is one example, If switches aren't available you could do something similar by pushing everything in a vector or array in order of the class IDs and then doing a single return !${Plugin[${ClassPluginList[${Me.Class.ID}]}].IsLoaded}

I realize macros don't play out exactly like shown here but felt this was easiest way I could communicate the thoughts to you in a way we both understood.

So then you'd use the function to determine if the plugin was loaded and if so disable the conflicting features. This would allow the features that don't conflict to continue to operate and be available to the player without causing any conflicting behavior solving the issue.
Again, it's not our intention to remove stuff without consideration for the impact it could have on players, but we do choose to disable things that conflict to avoid unexpected behavior either through the users lack of knowledge or otherwise. Going a collaborative route where only the conflicting features are disabled would allow it to be temporary (soon as the plugin is unloaded it would free up those behaviors in your Lua) and allow both tools to be in use at the same time.

I also just kinda slapped this together off the top of my head and there would still ofc be worked needed by yourself in order to get this to play nice with the plugin, so ultimately up to you if you want to add any additional effort. Unfortunately we're not able to disable specific features of the Lua, so for now we've opted to use the option available to us.

eye said:
I really like Easy. I use it for the dispenser action, force feed, Dannet, everything zone information. I wonder if the major objection is about the burn functions, Class tab, (combat?). I wouldn't mind a version of Easy without the Class tab. Account, Zone, Clickies, Hunter, and Fav tab seem to be clean? In options tab, I would think maybe begging and bind wound could cause a conflict but unlikely. Camp tab is clean. The merc tab may be in conflict. Maybe a checklist of items could be agreed upon?

Vote with your feet. Of my 16 toons only 3 don't use the CMTN/Sic plugins. I like my wiz though. Great job guys.

By the way, I continue to crash Easy when I select account tab on some of my toons. The only difference is the one with a username of 10 characters works fine and the one with 15 crashes (the name is a random combination of upper and lower case characters).
Click to expand...
Basically anything that moves, clicks, memorizes, casts, uses a clicky, ability, discipline, skill, removes buffs, targets etc. Any of the passive features that don't require action be taken by the character should be non-conflicting.
You reference clickies, the plugin does clickies, but because you are using the plugin for automation the plugin will use the clickies without conflicting with itself.
If you have two things trying to do two different things (or even the same thing with different end results) then it's conflicting behavior.
So if the plugin is trying to cast a buff on itself and memorizes a spell and then easy memorizes a spell then the plugin wants to fix the memorization that's incorrect...
The plugin wants to pull and easy would like to cast a clicky...
The plugin wants to burn one way and easy wants to burn a different way.
The plugin wants to travel and easy wants to collect a shiny.
etc as some examples.

An alternative to all this if you would like to use easy would be to unload the plugin. If the plugin isn't loaded, it won't conflict with easy, and then easy can do whatever it is you want easy to do.
 
Last edited:
Cannonballdex updated Easy.lua with a new update entry:

Update

All automations of the script are set to off (false) by default with the exception of UseDanNet. You have the option to set UseDannet to false in the custom ini file, however this will also disable any functions that require DanNet to work.

Added a zone that was missing (753) as a non safe zone.

Added mercenary information under the merc tab. Merc info will be displayed if you have an active mercenary.

Added animation to the battery level of your power source...
Click to expand...

Read the rest of this update entry...
 
Is this Lua not working anymore? when i type /easy ui it comes up with the EasyFind menu instead
 
Release Easy.lua
Status
Not open for further replies.
Next unread thread 🦁

Users who are viewing this thread

Total: 1 (members: 0, guests: 1)
Back
Top
Cart

Cart

Total -