EZ Server

Due to it being the Holidays and some lingering small issues that have crapped up some peoples play times, I'm enabling Double Loot for the night along with a patch fixing some issues.

I think expeditions are finally completely smoothed over, fixed some things in Abyss and Dranik should update without a hitch, but for crying wolf sakes, I will just say that they are extremely broke, that way your lowered expectations will make them seem not so bad.  ;D

Notable Changes:

• Expedition lockouts are 22 hours instead of 24 hours
• Abyss and Dranik now have soft lockouts of 2 hours once committed by killing the first boss in each
• Folks having issues with tasks updating properly should no longer have those issues
• Trevius: (RoF2) *Hopefully* Fixed looting incorrect items from NPCs.  Please report any issues!
• Trevius: (RoF2) Now able to loot items past the 10th slot on NPC corpses.
• Trevius: Attuned Items can now be auto-looted and will equip properly.
• Trevius: (RoF2) Aug Type 21 no longer shows the "Buy Now" button in the aug slot of items.
• Trevius: (RoF2) Identified the "Copied" item flag with the help of Uleat.

Enjoy

I have emailed you about the summoners bag quest being broken, I have to log for about 3-4 hours but I will be back on later.

Fffuuuuuuuu doubles going back in while im at work?!  Shit if id known that at 3pm i couldve called off >. <  time to go develop a severe illness


EDIT: told the chick im working with i have ebola and need to go home....she didnt buy it.  Working on a plan B

Thanks!

Should be part of the same issue

most generous sir, ty.

Akka,

There is an odd lockup when zoneing. When you zone in and zone loads, you can move for like a second or two but no buff or group shows, then screen locks up for a second or two and then buffs, groups etc.. show and you are free to move. no big deal just fyi.

Was removing the charm upgrades from named in the Mini dungeons done on purpose... I have noticed they are no longer dropping charm upgrades

Also, the main toon that is getting the missions is getting the quest removed before final hail and not receiving berries but gets the quest lockout timer

sounds more like a performance issue now that all trons actually pretty much load at the same time. might want to increase your page file or use a flash stick for added memory

could be, this is on my laptop with i7 sandy  8gb memory and an nvidia gtx460m only 1 toon loaded. page file is also 8gb, using SSD and it does it on other PC thats more powerful. It just started with server code updates so fairly sure its not my PC but anything is possible. and iirc UF does not do this, or did not as of a few days ago.

Does this issue happen to pertain to the task not updating?  Me and a buddy tried it twice for his mage.  We get the unfinished bag but cant move on to the next step.  He has the unfinished bag but the quest still thinks he needs the parts.  We still get the parts as well again and again even though we should be past this.

This actually has to do with the RoF client, it loads a lot of resources on demand so what happens when you zone is that you are seeing a freeze where it is loading race models into the client on demand via memory so it locks up for a quick second. This is purely a client thing which is not really an issue even though it is slightly bothersome in the beginning.

You notice this because you zone so much more faster on EQEmu than you would on EQ Live servers that your toon enters often times before NPC's. Otherwise before your toon is given the 'Ready state', it is sent all the NPC and door positions before it is given the zone to drop into which allows it time to load resources. In this case, you're zoning so fast its happening backwards and then the client loads everything just after zoning.

Hopefully that makes some sense.

Yes, I sure hope its been updating today.

Thank you for the response, makes perfect sense:)

Tried to do mini dranik today. hailed miner accepted. None of my raid members get auto prompt zone into the expedition and no quest given to any toons in my raid.  Tried to #e destroy to get it to prompt and still does not give task or enter instance.  I am still using rof client.  thanks. I once again tried this a couple hours later did a /# destroy and got the quest from nexus miner instead of stone hive and it worked.  dont know if others having issues with stonehive miner. 
Thanks

Xeky

Fixed issues regarding expeditions and Abyss tonight, we should be good.

Let me know if anyone runs into anything else.

While the load on demand could definitely be the cause of the lag spikes on RoF2, I am not 100% convinced that is the issue yet.  I hadn't experienced these lag spikes on my GM char previously, but I loaded a level 1 char and saw the spikes yesterday.  Kayen had mentioned that they come in as the no mercenary messages come in.  So, it may be some kind of lockup related to the merc packets that are getting sent.  I am not sure offhand if EZ gets these messages since Mercs are not enabled there, but I don't think there is anything preventing them, so you may get those messages.

Once most of the RoF2 remaining issues are resolved, I will look into this lag spike issue further to see if it can be resolved as well.  It will be easy to prevent the messages from coming in on servers that don't use Mercs (if you guys even get those messages).  Also, I need to look into why the message is coming in twice, and probably need to prevent it from coming in at all.

Trevius, your help and presence is always appreciated.


-Hate

Trev, I just jumped onto stormhaven for S&G's and played a bit. What I noticed was the clients would tend to lock up for 5-10 seconds when switching to make them the primary screen after a long period of being in the background. I don't know if it helps or not but maybe there is something w/the background FPS and memory or something? I dunno.

Two separate issues Trevius. I know for a fact the client is locking up on on-demand resource loading and has for as long as I've used the RoF client, however I don't doubt that the client is hanging for other reasons as well when expecting a particular packet.

I just wanted to say thanks for all the hard work Akkadius on the expeditions before going into the bug reporting  ;D.

I'm still having issues with raids getting the quest and porting in.

1. Inviting/Quest Invitation
I tried in both the Nexus and Stonehive this morning and just could not get the Miner to invite my whole raid or teleport in on first accepting the quest.
I tried reforming my raid several times and both #e leave and #e destroy. He would sometimes give only my main the quest, and other times my main toon and one other bot, but never more than two. I worked around it by manually inviting everyone (which I made a hot button for now), but only after I tried #e destroy, #e invite, and raid reforming and re-hailing the Miner. I noticed that after destroying or leaving the quest the first time, it did not show up on my main's quest log the second and subsequent times I tried to get the quest. After going through the motions to click OK and "receiving" it (without it showing in the quest log) on my main, my bots did get the quest in their log when I did #e invite for them. I had to switch expedition leaders and re-invite my main on a alt bot in order for it to show in my main's quest log.

2. Porting In
This is rather minor, but I just wanted to report it since I'm not sure if this is the new intended method of being ported in or not. After properly ensuring all members in raid were in the expedition, I hailed the Miner again on my main and this time it did show all 13 members before clicking OK to get ported in. The Miner however, only ported in my main and no one else. Of course the quick workaround I used is to just have my raid assist me and everyone /say interested in xxx + a dialog box OK macro button.

Not sure if anyone else is having the same problems as me, but I just wanted to make sure you were aware of it.

I'm going to need you to help me get a little more detail as to what your situation is so I can get to the root of your problem.

Sounds like most are not having a problem but I have heard some things about this occurring.

When this occurs are you in a group or a raid, I know you mentioned raid but I need to know for sure.

Another question is, was everyone in the same zone when you had issues porting in or with your invitation process.

Any specific details you can give me will help

Akk I am unable to currently get the mini dungeon tasks from instanced zones had to get it from public nexus.  This is what i did. Went to guild stone hive tried to get task it did nothing. So i #e destoy the exp. Tried it again same thing.  Went to guild nexus same thing.  Went to public nexus it worked.

Thanks xeky

Same thing happened to me today...did same steps, destroyed expo, left instance and worked like a charm in pub.  Remember our conversation the other night akka when i asked if this could be related to instances vs pub? =3

Next issue that happened i finished dranik. Went to guild stone hive hailed miner. Then Bam all 18 toons disconnect and im talking the disconnect where i had to sit there and wait for my connection to drop . All happened after task was turned in.  Dc'd to the character select screen.

Hey Akkadius, Yes all toons were in the same raid in the same zone standing right next to each other.

As Xeky has mentioned, I tested it more today and he is right. The issues with quest issue/receiving and porting in only occurs in user created instances of the Nexus and Stonehive. I recreated all the bugs today again and as soon as I moved to public, everything went smoothly. All toons got the quest immediately and were all ported into the expedition zones for both Dranik and Mini T5. I think maybe adding a dialog to the Miner to remind people to leave Stonehive/Nexus Instances rather than going in to mess with the code would be sufficient. Then again, it might be a really simple fix.

If it is an instance oriented issue, I'd rather just fix whatever the root of the issue may be.

Can a few others confirm like clockwork this is what is causing people grief is being inside of an instance?

Yesterday I had that happen, where i was able to get the quest in public nexus after not being able to get it from instance.  Today, I can't get it in pub or instance, stonehive, or nexus.  I get the "The entry to your destination has been marked on your compass..." but no port, no quest on toon hailing or any other toon.  I am in raid currently....  

Disbanded raid and tried with a single group and got the same result.  

Edit:  This was for abyss T5 mini
Upon hailing a second time without destroying the instance, only the toon who hailed was ported in... then... when trying to #e invite the remaining group members and bring them in to instance, it says that my main toon (who got the expedition) is already in an expedition and won't let me port the rest in.

for me the issue always happens when i'm in a raid, always. Ever since i started inviting my toons individually, i haven't had any issues regardless of being in pub or instances...actually i've never tried to grab the task in pub, its always been in an instance. ive also been doing the dailies every day since their release.

Akk getting mass Dc'd to character screen when hailing miner to finish mini dungeons. public stone hive

Thnx xeky.

Exact same thing happened to me. Was in nexus GI and tried to get expedition, said I got it and it marked the location on my map. Left the instance, and in public nexus it ported me in, but my group couldnt enter, and didnt show an expedition. Task window on box who got the expedition didnt show the task. Finished, cleared Abyss mini, and no completion, no reward.

Oh, and it locked me out for the day anyway.

Same thing happened when I tried to get the task in Stonehive, public. So....no berries for me today. :P

MANY reporting being unable to complete either task. Either cant get in at all, or if they do killing every mob in the task doesnt complete the task.

Yah...  i can do an expedition... if i #e invite each toon before i zone into it... but the main toon that starts it still isn't getting the quest no matter what i do.

By the way....dont know if this helps or not, but I didnt have any issues at all til I tried getting an expedition in an instanced version of nexus.

Haven't been feeling well so I haven't gotten to dealing with this again, if its bad enough I will disable them again until I can look at them

Have had ZERO issues with expeditions so long as i REQUEST the task in pub...usually nexus...but has worked in pub stonehive as well.  And so far turning in has shown no issues regardless of instance vs. Pub.  All requests have been made with 9 or 10 toons all in raid at time of request.  Have not had to use #e invite for anything as of yet

Requested pub nexus no issues.

Requested instanced stonehive no issues.

No idea what players are doing or script to have this fail

My warrior (which is also the raid/team leader) had the same problem earlier, i.e. did not get the quest, thus unable to complete it. While the rest of my toons will get the quest and able to complete it. This happens to the warrior for the past few days. FYI, my group is in pub instance.

I did this and it seems to fix the problem.

1) Had my warrior ungroup. Request the quest in the pub instance, it did not get the quest, and zone my warrior into the instance.

2) Use the "#e destroy"

3) zone back out to pub, group/raid my whole group in. Request the quest again from my warrior, this time...all my toons, include my warrior received the quest....and able to complete it later.

Give it a go, might work for you....assuming if you has problem.

Cheers.

Still getting unsually high ping on some toons when zoning into new zones.  Only fixes by zoning again or camping out.

Thanks Xeky

Why do I feel like I'm getting massively trolled

I was getting it earlier today in T9, soon as I zoned back to stonehive it went away.

I would think T9 would have its own latency incurring problems by the nature of the zone and how many updates are being sent for position updates and such.

It is very much appearing like this is a raids issue and synchronization with the database.

Because when an expedition is requested, it is using the database entries of the raid to actually send the invites. If these are not in sync then that would be the problem.

If someone can reliably reproduce the issue where it gets out of sync I will give you credits for saving me a headache.

Ha be nice if that were true.

I just got expedition from miner gave to me and 1 toon invited other 4 in group and 3 outside of group to test. Zoned the 1 group in and pulled the first area of dranik. Then i pull the 2nd area upon ae killing the group i dcd on all 6 toons in dranik (no zone crash) and it gives me a lockout on the other 3 outside group and when i log back in task is gone and i have lockout on group + still in instance.

Can confirm it is not being in a group vs being in raid same issue either way

Not sure what special with this morning reboot. None of my toons were able to get the quest for mini abyss. Was working perfectly for the past 2-3 days.

Did the above steps again....and wah-la...All good again. All toons received the quest and zone in.

FYI.

Cheers.

Yep, something is wonky now.  Was able to complete the quest yesterday, but today only 1 of 3 could complete the Dranik.

All were in public instanced Nexus.  War started the quest.  He and Pally were moved into the expedition.  Zerk was not.  War added Zerk and all 3 ran the quest without issue... until hailing miner.  Zerk was the only toon to get berries.

oh my god frustrating...

4 of the 6 people in my group got credit, and it DC'd my entire group twice and caused my entire group to crash once.  I've been back to EZ for 1 week and have crashed more this week than years and years of playing in 2013 and prior.  I can't even zone into my Guild TOFS instance it insta freezes on any client.

Still unchanged for me.  Have not been able to earn berries in  quite some time now.

I did two or three yesterday, got berries on characters. Can we start getting specifics?

in example:

Yes, those are my character names and, no, that did not happen yesterday.


-Hate

This happened to me this morning too. Made one with Tank, invited grp. Everyone but War and Pally got the task.

When we zoned over to "C" whole grp went LD. wasnt just me, GF on her pc was in grp and went LD also. Was able to log back in from Char menu.

def still an issue i just did what someone else suggested about requesting in an instance doing #e destroy zoning my group into pub and getting the expidition. ... i did notice that if i have more than 6 toons in the zone it wouldnt work for me ... did this method the last 3 days

Fixed the issue regarding getting Expeditions.

It had to do with the zone controller that handles expeditions (This entity is invisible) not being present during the process of inviting and adding players to the task.

This was predominant in instances because the controller had not been spawned yet, as well as a fresh new nexus or noticeable upon server reboot.

This will no longer be an issue, however:

There is still an outstanding issue I'd like more information on, or have a player that can help me reproduce (While I am online) not getting task credit at the end.

Maybe some information on the task credit issues, were not all toons in zone? Were you in the instanced version? What expedition were you running?

Please help me get to the bottom of this, I want to get these issues squared away this weekend.

Catacombs:

All 6 chars was able to get task when main char hailed and stuff. All Zoned in at the same time from Nexus.

Floor A went smooth no problems.

Floor B 5 of 6 chars was able to zone in the 1st try. The War(char who got task in nexus) was lost, had to Task Manger the EQ window and relog him in.(after wipe I zoned chars 2 at a time and had no problems.   wiped when pulling the last bug. SOme how everything past the locked door for the 1st boss aggroed and the whole floor came to me. Recovered and moved on.

Floor C went smooth no problems. I did zone in my chars 2 at a time from B to C and had no problems.