• 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

The Addicts Warlander Compile 09.15.2011 (1 Viewer)

MQ2Rez's main purpose is only to accepts rezs. It doesn't cast them. Prior to the fix it did not recognize the 0% rez from call of the wild so the toon would just sit there with the accept this rez yes/no box open. Now it will click yes when a druid or shaman tries to rez them with the Call of the Wild AA.

We fixed it because the 90% druid/shaman rez can not be cast in combat but the Call of the Wild AA can.

The function you are talking about is the /rezzme function that allows you to rez yourself while still in hover mode. That leaves an unrezzable corpse. I wouldn't use that function and actually I am going to disable it next patch.
 
Last edited:
MQ2Rez's main purpose is only to accepts rezs. It doesn't cast them. Prior to the fix it did not recognize the 0% rez from call of the wild so the toon would just sit there with the accept this rez yes/no box open. Now it will click yes when a druid or shaman tries to rez them with the Call of the Wild AA.

We fixed it because the 90% druid/shaman rez can not be cast in combat but the Call of the Wild AA can.

The function you are talking about is the /rezzme function that allows you to rez yourself while still in hover mode. That leaves an unrezzable corpse. I wouldn't use that function and actually I am going to disable it next patch.

A suggestion would be to create a mq2rez.ini which would only contain an rezzme=0. This somebody could change to 1 if they wished to be able to use the /rezzme option.
 
So functionality and capability in this new compile are the same, it's just been rewritten to be smoother/etc?
 
It was rewritten mainly for stability and safety. Warlander now emulates the way EQ actually sends packets much closer so it is safer than our previous methods. All the active hacks have been updated to use the new packet system which is more flexible in handling packets so less crashes.

The main functionality change was MQ2Piggyzone was rewritten to zone everywhere. Our new version can zone through the Void into SoD, into the end zones of UF. We are are still on working on the Morells Castle zone in but that will be finished in a week or 2. NPC teleportors was completely rewritten. It now works again on Magus, Pods and translocators. We rolled MQ2Fippyzone into the MQ2Piggyzone for less confusion.

The Addicts Warlander Code also sets us up for when Viels of Alaris is released for an easier transition.
 
I've been running the new ninjaloot.inc for the past two days with the new compile. They seem to work flawlessly except for ninjaloot on lore items. If the loot is a lore item already in inventory, the character continues to loop about every 4 seconds through looting the mob until the mob rots.
 
I've been running the new ninjaloot.inc for the past two days with the new compile. They seem to work flawlessly except for ninjaloot on lore items. If the loot is a lore item already in inventory, the character continues to loop about every 4 seconds through looting the mob until the mob rots.

What is the name of the item?
What is the item set to in your loot.ini file?
Did you change it at all?
 
Ninjaloot

Elaborate Defiant Fire Bauble=Keep

I've been getting this item in the same spot and using ninjaloot for a year or two. Before this change it would attempt to loot once, leave it on the mob and never go back to it. There have been no changes in the loot.ini file setting and it is still resident in the bank.

Now it loots the mob every 4 seconds until the mob rots.
 
Sounds like it is not adding the corpse to the ignore list after finding lore item. Might be a typo or something in ninjadlot I will look at it today.
 
I've been running the new ninjaloot.inc for the past two days with the new compile. They seem to work flawlessly except for ninjaloot on lore items. If the loot is a lore item already in inventory, the character continues to loop about every 4 seconds through looting the mob until the mob rots.

does it work if you are using the /hidecorpse looted option of the game? if you cant target the mob it shouldnt try and ninja loot it? maybe? just a thought
 
does it work if you are using the /hidecorpse looted option of the game? if you cant target the mob it shouldnt try and ninja loot it? maybe? just a thought

That would be a good temp fix until I have a chance to look into it more.
 
Hey Maskoi set call of challenge=1 as you instructed (/melee callchallenge=1) and its still not clicking it ... havent had time to look at the holyshits yet but did figure out how to get staunch defense to click more often and field armor Thanks for the help!
 
I'm still getting constant crashes from Piggyzone. Some of the zones that this has been happening for regularly are Bazaar, Guild Lobby, Guild Hall. In fact, I have never actually had a successful Piggyzone to Guild Hall, it always drops me to server select screen and dumps me in the lobby. I've been getting a lot more crashes than normal, gonna try disabling some plugins and seeing if that helps. These crashes happen sometimes even with manual zoning, so maybe this could be a technical issue on my end. Gonna be really hard to say for sure.
 
Last edited:
I'm still getting constant crashes from Piggyzone. Some of the zones that this has been happening for regularly are Bazaar, Guild Lobby, Guild Hall. In fact, I have never actually had a successful Piggyzone to Guild Hall, it always drops me to server select screen and dumps me in the lobby. I've been getting a lot more crashes than normal, gonna try disabling some plugins and seeing if that helps. These crashes happen sometimes even with manual zoning, so maybe this could be a technical issue on my end. Gonna be really hard to say for sure.

I've stopped using /zone /gate and /fade, because while I don't crash every time or even most of the time, using them even once means that particular client is doomed and it will eventually crash while zoning either normally or with z/g/f.

I just warp to zone lines now and zone manually.
 
I've stopped using /zone /gate and /fade, because while I don't crash every time or even most of the time, using them even once means that particular client is doomed and it will eventually crash while zoning either normally or with z/g/f.

I just warp to zone lines now and zone manually.

Any problem like this should have disappeared with Warlander. Mq2piggywas was rewritten. Even before I never heard of that happening like you may want to try running Warlander out of a completely separate brand new folder because it really sounds like your setting or something are corrupted somewhere.
 
I'm still getting constant crashes from Piggyzone. Some of the zones that this has been happening for regularly are Bazaar, Guild Lobby, Guild Hall. In fact, I have never actually had a successful Piggyzone to Guild Hall, it always drops me to server select screen and dumps me in the lobby. I've been getting a lot more crashes than normal, gonna try disabling some plugins and seeing if that helps. These crashes happen sometimes even with manual zoning, so maybe this could be a technical issue on my end. Gonna be really hard to say for sure.

The Guildhall has always been a problem even before they change it from an instanced zone. i will add it the to the new functions to see if that solves it.

If you are crashing any where else then your settings are messed up somewhere. Try running Warlander out of a completely separate brand new folder.

If are crashing on manual zoning first I would load eq up then zone like 10 times see if you crash to determine if its an EQ issue. Then look at any plugin that reads new spawns on zoning like mq2spwnmaster, mq2gmchecker, mq2targets etc. One of these may be crashing you when zoning.
 
Doesn't look like a lot changed doing some testing then should have compile up soon if everything works.
 
Any problem like this should have disappeared with Warlander. Mq2piggywas was rewritten. Even before I never heard of that happening like you may want to try running Warlander out of a completely separate brand new folder because it really sounds like your setting or something are corrupted somewhere.

I delete the old MQ folder with every new compile and semi-regularly run full file scans with the EQ client, I dunno man. Maybe it's a bad system file in my Windows install or something. I just know that I will get a run-time error and client crash eventually when i /zone /gate or /fade. This only happens when doing that and never when not doing it.

It's probably for the best because piggyzoning a bunch of times is obviously a giveaway to guild members :)
 
As stated previously patch our entire compile was updated and MQ2Pigyzpne was practically rewritten as the 9-15-2011. If you are experiencing problems now then we need to look at your windows setup permissions hardware whatever.
 
Sounds like an issue on the users end. A friend of mine has similiar issues and its simply because his computer his out of date. what stats does your computer have etc i very rarely crash using piggyzone
 
The only time I ever crashed with piggyzone was when I had all 6 account loaded and was chainzoning all 6 at the same time.
 
Sounds like an issue on the users end. A friend of mine has similiar issues and its simply because his computer his out of date. what stats does your computer have etc i very rarely crash using piggyzone

It's your standard gaming rig, core i5, high end radeon, etc.

I would not be surprised at all if it was my OS or something weird with me like I said, not trying to shit on this compile or anything, was just responding to someone that was also crashing a lot.
 
It's your standard gaming rig, core i5, high end radeon, etc.

I would not be surprised at all if it was my OS or something weird with me like I said, not trying to shit on this compile or anything, was just responding to someone that was also crashing a lot.

I didn't any negative impressions from the posts all. I am just trying to narrow down why you are crashing so we can identify and document it to help anyone else that might have the same issue.
 
is it just the 1 character? or are you boxing a few at the same time?
 
Two boxing usually. If other people aren't experiencing this, it's obviously something to do with my setup, and I wouldn't even know where to begin troubleshooting. Pouring over a DXdiag dump and that sort of thing, ugh.
 
The function you are talking about is the /rezzme function that allows you to rez yourself while still in hover mode. That leaves an unrezzable corpse. I wouldn't use that function and actually I am going to disable it next patch.

Good Call... I once tried the /rezzme function and it left an unrezzable, buggy corpse behind. Basically it couldnt be dragged, summoned, rezzed, or looted and only disappeared after servers came down (also presumably after a zone crash too). It's a very good way to get caught if someone notices a corpse sitting there for days and days and petitions it or something.
 
The Addicts Warlander Compile 09.15.2011

Users who are viewing this thread

Back
Top
Cart