Meta

I was always under the impression that instances are created when you zone in and locked when the lockout is triggered. At that point the expiry time is set and anyone zoning in and killing shit should be locked to that instance and that lockout time.

This isn't what's happening (all the time). We have varying degrees of lockout timer fuckups as I'm sure everyone does. It's really annoying.

The GM is a ballbag first for saying it's working as intended. All the other shit afterwards is just meh.

__________________

Distressed

I agree the GM is a douchebag for getting pissy and bringing up the plat and epics shit. Thats just unprofessional and quite gay.

With that said, all persistent timers in the game work the same, with exception of the zone in bug, where you just have someone drop raid and make sure its a good instance before having everyone head in. There is no bug affecting your character in this matter. Your guild started working on SoH 5 days earlier and so their lockout timer got a 5 day head start. You went in late and started your lockout at a different time. If GM's reset peoples instances so everyone could raid with their guild, every swinging dick would be doing SoH non-stop atm. I'd do the PUG SoH raids with my wiz and templar, then do guild raids. I think thats what the GM was trying to avoid is someone exploiting by doing multiple SoH raid zones, even if he was too much of a douche to say anything remotely resembling a coherent reason to not reset yours.

Simplest terms, SoH trash can be 2 grouped fairly quickly, drops way overpowered gear and masters. If getting reset early was an option could do PUG raid in the morning, get 40 chances at great gear, get reset by a GM and then do it again that night,...If life was this easy nobody would be in VP.

__________________

Dunkelheit

I was under the impression the instance is what set the lockout. If you join up with a raid on the last day of their instance, you gain their timer. The timer will then timeout with the rest of the raid that has been there all week...

Carvium

What a Tosser of a GM but woot on Screenshots of him stroking his epeen!!
4*

__________________

Flayedskin

"Do you get locked out of the zone or locked out from killing a mob again for 5 days?"
We entered the zone on say day 0 and killed some trash on an off night (note this was not one of our normal raid nights...just an off night raid we did for fun). We went in day 4 (this is 4 days later) and killed most of the named, but had an issue with one so we left it for another day. The next day I entered with my guild (day 5) and killed the named and got a 5 day lockout timer which locked me to Shard of Hate for 2 days after the instance I was in expired. You do not get locked out of the zone for killing a mob, but you get locked out from killing a mob for the first time in a zone. Persistent zones are not supposed to work this way.

Were you petitioning a bug or trying to get your timers reset so it matched up with other people?
I was petitioning because I and three other guildies in my guild who were in my situation got the lockout timer past the expired instance stage, yet at least 3 others who were in the same situation did not get any lockout timer and could reset their persistent timers that evening after leaving the zone (note they were not in the previous two entries into the zone). I would categorize this as a bug, sony would call this a "feature."

In EQ1 we have timers for raids that are counted per mob in instanced zones. Say we're doing a raid in a zone with 5 loot targets, kill 1 mob its locked out for 5 days. Next night kill 3 mobs, and get lock outs per mob not per instance. Finish out the next night with the last mob in the instance. Is this how eq2 raids work or is it a lockout from the whole zone from killing a certain named?
This is not how it should work, you are supposed to get one lockout for the entire zone that is persistent and is shared among the raid force that enters. It starts either from the inital zone in or killing the first mob/named.

Why would you need your timers reset?
Because 95% of my guild was unlocked to the instance, yet 4 of our raiders were. I wanted to raid with my guild that evening but the lockout timer goof prevented me from entering the new zone. If the entire guild was locked out I would not have cared.

Flayedskin

"Simplest terms, SoH trash can be 2 grouped fairly quickly, drops way overpowered gear and masters. If getting reset early was an option could do PUG raid in the morning, get 40 chances at great gear, get reset by a GM and then do it again that night,...If life was this easy nobody would be in VP."
You are absolutely correct. SoH trash and the first 3 named could be easily 2 grouped. That is why we started the new instance on a down night to save time for harder content on a raid night (we only have 4 big raid nights a week and 2 smaller ones atm on 2 to other nights). But the same could be said for EH back in EoF...you could one group the first bunch of trash mobs in the zone, so often guilds did that to maximize the number of named on the first floor when we went in to do the instance at another time. This is a DESIGN flaw in how easy the mobs are to kill...something that was clearly stated many times on this and other forums. Yes you could possibly exploit the scenario you described by doing what you said...the issue is that this would be clearly obvious to most GM's by looking at the loot won by guilds. However, I said at the begining we were not trying to exploit the zone..just maximize the 5 day reset timer the zone has and hit the zone every 5 days.

Taylen

I can understand them "i've said no so i'm not budging"

But still, he's got the totally wrong attitude..but to be fair, like already said he's an SoE employee and will treat us like shite, i mean we only pay for his wages and shit

__________________
Taylen - Lv 80 Necromancer
Misha - Lv 80 Troubador
Latanya - Lv 44 Warlock

Bingo

As a suggestion.. you can feedback this sort of thing. As well as bug it. My suggestion, and what I did, is feedbacked that they should give GM's Policy's allowing the resets.. which may require dev work to accurately log errors like this.

As far as Hightower, he's rather a nice guy.. may have rubbed him the wrong way.. and he did come across in a way which is not to pleasant. No excuse for it.. but from my dealings with him he's quite friendly.

Apollodon

how you talk to the GM's in the petition and in person determines how they act towards you

why did he freeze you?

that was probally the first thing that pissed him off, if he thought you where ignoring him

first rule of trying to get something from a GM is not to call him an asshat or retard
there like ants they love sugar

Rinion

The way I understand it is the lockout is set on the first mob you kill that is capable of triggering the lockout. Which it really isn't even a lock out. best way to describe it is it triggers a Character Save and saves you to that instance as it is. Usually the first named in the zone is the trigger.

However for shard of hate The Trash mobs trigger the save because trash mobs have some pretty decent random drops in that zone.(Trash mobs trigger the full lockout timer so that guilds cant kill trash, zone out, and zone back in 30 minutes later to clear more trash for loot.)

VP, For example will save the instance for up to 9 days from the time the first namer is killed. So you have up to 9 days to finish the zone but you are capable of resetting it earlier then that, I believe 5-6 days after first kill but you can not reset earlier then that.

What it sounds like to me is that they killed trash, raided something else, came back to kill more trash the next day and so on and so forth and when it was time to kill namers he found his zone locked out rather then saved to him.

You are support to be able to re-enter persistent zones whenever you like. just the mobs wont be up anymore if you already killed them.

But, from what I heard the change to make trash trigger the persistent save is probably what got him.

I assume if they were farming trash every day, like he said, then they were resetting their timers, but since it was patched (yesterday wasn't it?) killing the trash locked them out and if their guild zoned into a new instance but they were saved to the old one from killing trash then it would appear to them they were being locked out.

I remember once getting summoned and frozen by GM whatever the Troll with soul or some such. He stuck me in the white room under qeynos sewers and gave me some speech about how he wouldn't tolerate my language.

I had a mistell to a friend in ooc =/


Anyway.

To the OP: Did you and those few others that you mentioned had the problem go in without your guild to kill trash?

I suggest checking to see if the problem is that you are saved to a different instance then your guild is, in other words try to zone in solo and see if you can.

I really dont know what else the problem could be.

__________________
"Before one can identify anything as "gray", one has to know what is black and what is white. In the field of morality, this means that one must first identify what is good and what is evil. And when a man has ascertained that one alternative is good and the other evil, he has no justification for choosing a mixture. " Ayn Rand