Lopherus

I'm no fan of Alexensual...but this post made me watch the video which prompted this reply, and I think the post's personal attacks against the youtuber go way too far. He mostly just presents reddit posts, etc., others have made, and which include details that made me scratch my head as well - such as, that a known gold-seller on Elysium (per January 8 of this year!) is, or was, now a member of the team. That's just not ok, and I don't understand. It's one thing to bring hackers on board to help you patch security holes, or a good botter to work with them to prevent botting (very often an excellent idea)...but someone who so recently took advantage of this very server? This blows my mind. Alexensual should not have refunded; this was immature and not ok given that he had received said funds for a specific purpose. He also should not have refused to talk, if that really happened. But the team here should not get personal with him either, and strive to be more professional. When a new team-member's integrity is questioned (such as WhiteKidney's in a prior forum post), then the reply shouldn't end with a snarky "P.S.: He's cool." That's arrogant, and doesn't make users feel taken seriously.

It is my understanding that all realms use 1.12.1. talent trees, in worlds otherwise (items, raids, etc.) on earlier patches slowly progressing to 1.12.x. Patch 1.11. introduced Talent Respec Cost Decay. What does this mean for Elysium? Do talent respec costs decay, as they should based on the talent trees used; or will they only in the future, when the progressive world has reached patch 1.11.? If this is up for debate, I would much appreciate some decay - it's perfectly (vanilla) blizz-like. The pre-decay world was unduly harsh on those appreciating both raiding and serious PvP, or those just mis-clicking when choosing a talent. If we use 1.12.1. talent trees, it seems only proper to apply the related decay rules too.

Thanks everyone for clarifying that Elysium currently has patch 1.11. style decay!

Since today, a limit appears to have been introduced such that you can only talk in the same general chat channel (e.g., /world) once every minute - or something similar. This makes perfect sense to reduce spam. However, it was introduced such that after talking in /world, you can also not send private messages, or talk in party, for 1 minute. I cannot imagine that this is intended. To give some examples of awkward consequences: assume you lfg in a general channel, and then get several whispers as replies. You cannot react to them for a while, which is both unfriendly and not helpful; you cannot even welcome in party chat someone who just joined, and ask a possibly important clarifying question. And just generally, there seems no purpose to this restriction. I assume that it is a bug, and suggest the team remove the cross-over restriction (i.e., keep the 1 minute lockout for talking in the same channel, but remove the restriction with regard to whispers and party chat, etc.). Thanks. (in case this differs by realm, which I don't think, this is on Elysium PvP)

Does anyone on the team read what you report? Have anything to say about this? It's not just a small issue. After several hours under this regime - you not group leader, finding the missing tank, and unable to tell your group who to invite - ...this is a terrible solution to the probable intent.

Could you please point me to rules concerning 'wall jumping?' I assume it is about doing this in WSG, say; but there is certain in-game content where people always wall-jumped, just for fun (examples would be reaching the top of the AH in IF, or the dwarven airport). The latter ones are perfectly harmless. I'm terrible at doing this myself anyway, and so unlikely to engage in it, but would not want to break rules I'm unaware of; hence, any clarification would be great! :) Thanks.

I haven't done this yet on Elysium, but 2-step authentication doesn't mean lockout when you use a different IP address to log in. It *should* mean that, upon such an attempt, you receive a text/email and need to confirm by replying that it's really you. If everything works fine here, this should be no problem.

P.S.: I gave up after 2hours and 15 minutes sharp. Considering that it had been out of stock for an unknown time before I started waiting for a restock, whatever the restock timer is...it's way, way off. P.P.S: I read somewhere that on the bug tracker page, there should be a button "Add an item" (or such). Despite being logged in, the page has no such button for me - if someone could transfer this post to the bug section, I'd appreciate. If the button doesn't exist, I suggest adding it.

Kindly remove all but one post. I posted once, or at least meant to, to point out current issues. I don't know why it was posted so many times, making it look infantile.

As the title says.

This might have been discussed, but I didn't see it. The infamous MC within about 11 days of vanilla launch might have been officially celebrated, but it raises questions not only because it seems doubtful that the gear would allow for this (and doing it with a group of many not even 60s). However, far more astounding is that this raid group must have had multiple essences. Obtaining an essence not only means that you are honored with Hydraxian, but already have killed the 4 lieutenants. The person with the leaked stream isn't even close to friendly, in any case. Anyone? How did that work: 1-60(ish) + essences farmed successfully in 11 days, which means at least 1 (2 really with trash quest part) prior trip to MC, or several people hearthing out during the raid after lieutenant kills and being summoned back, already having been about honored prior to this raid, and having been in there before too to do an earlier step (killing some trash)? Note that a hypothetical path through completion on the go, trip to azshara for turn in, includes, in the best possible scenario, two such round-trips (trash + honored, turn in in azshara, then kill lieutenants, turn in in azshara); and that no lieutenant can be touched before the first round-trip is completed, or the follow-up quest to kill the 4 lieutenants is impossible to do in the same run. The person streaming, in any case, had never killed trash before this run as is visible in the early parts of the video. There is nothing to celebrate about such an early clear. This isn't because I'm jealous - I'm a consciously slow leveler, and couldn't care less when future raid loggers get happy however they managed to do this. It just means that a primary goal for many got trivialized under circumstances that make you scratch your head. It also makes you wonder if, maybe, raids are nerfed here, which I, at least, would find regrettable. This prior paragraph aside, I do not understand how the raid could have had enough quintessences. I would appreciate an explanation to further my belief in server integrity.

Thanks for digging this up. This seems to strongly indicate that the mechanism to douse at least is implemented properly, which was what I was concerned about.

Were all your 217 posts just rude, condescending, angry, and non-constructive attempts at put-downs? You must have a lot of spare time on your hands.

Rag and MC, including rep gain, were scripted almost perfectly on Kronos, where I come from (and which died because Nost fanboys deserted it, if you ask why I play here). Just n.b.

While you appear to care about flaming (and I couldn't care less), I care about a correctly scripted server. My hope is that the developers notice what I point out here, and investigate if the act of having to use quintessences is correctly scripted, as well as the way to obtain them.

It's not even remotely easy in the first run ever (and more so if these are all characters who haven't been 60 a week - if they even are 60); and besides, none of this happened in the streamed video.

What if you answer my question, as opposed to just being arrogant? And what does developer twitter have to do with my question? It congratulates to a clear; my hunch is that MC is ill-scripted and does not require dousing (because then I have no trouble understanding what happened). If that is the case, then it is likely unintentional, and should be brought to the team's attention.

No. The first quintessence can have been obtained no earlier than after the last lieutenant died - 3-4 hours into the video. The one hour between douses reference is irrelevant because he for sure was not revered and had an Eternal Quintessence; so multiple simple quintessences were used (and if 1 person had used an eternal essence - earliest use: more than 4 hours into the run -, with 1 hour cd between, then we're talking 11-12 hour raid). That means several people had already satisfied this, and went to Azshara to get essences at the earliest about 4 hours in. It involved summoning back, re-tracing path to old bosses just to douse, and what have you -one shouldn't forget that getting to the alliance FP in Azshara from Darnassus, and riding to the quest giver there takes quite a while. There is simply no evidence for this in the video, certainly not about one person being summoned multiple times. And if it didn't happen, the lieutenants would have to have been killed before - how? I let people add comments now, and be quiet. I made my points. Based on what I've seen, my best guess is that MC didn't require the dousing to summon Rag.

No one can have an essence before the final lieutenant dies. Then, hypothetically, you can start porting+flying+summoning (how unlikely all other requirements being fulfilled is). None of this happens though if you watch the video. People leave to repair and check for new fire res gear. Then the raid continues. The questions about the quintessences I raise are not answered. As to the gear, I have no trouble believing that extremely competent raiders can possibly pull this off. That's not what my post is about.

Server integrity is not a big issue, and best addressed by pooh-poohing it?

Dynamic respawn rates take care of this pretty well, for most quests.

This is the philosophy Blizzard gave the game - dynamic spawn rates were part of vanilla, probably are part of current wow; and quest items were bottlenecks. The queues suck, the dc's suck; but don't give the developers of Ely/Nost shit for implementing stuff blizzlike. Spawn rates are just fine from what I've seen.

My first attempt to get in: 8 hours wait, then dc'ed. My second attempt: 8 hours wait, dc'ed. Managed to get back into accelerated queue to only position 2,500! Made it into the game after only an additional about 2 hours! Clicked the orc portrait to make one! ...and then I get dc'ed, apparently because a patch is applied. Didn't even set foot into the realm. I got back in within only 20 mins after patch! And made it to level 2! ...to be dc'ed again, not getting back in in 5 tries, and daring to step away for 3 mins, so I'm put back into position 2,800-ish when I come back (I have only myself to blame for stepping away for 3 mins). To be dc'ed again, and going back to queue at only <400! Ohmanohman. To get in, and make one character! To start making another...to be dc'ed again! Probably spent too much time in char selection screen (mind you, was clicking to make character), and so afk patch decided I'm no good. To not get past 'Authenticating!' For the next hour or so! Re-entering at position 3,754! Oh man, It's gong to be only 3 hours until I maybe get in this time. I do! I play for a while! Bedtime. ------------------ Next day! I enter queue at around 4,500. Oh man! I get dc'ed in the 2,000s. Now i can't get past 'Authenticating!' It's good to see though in the 'Uptime' section that the server has been up ever since I was in the queue. So much fun! Can't wait for what happens next! ---------------------------------- Edit, next day: It's becoming pointless to document. After briefly getting in today, hot patch puts me back to position 4,000. When almost in, I dc. I get back in to position around 7,000. When almost in, I dc. Now back in queue around 5,000. I mean, seriously...

Please mind your own business, fanboy.

I realize that fanboys will go out of their way to question others, and see no fault in this server. I play on Kronos too, and get not disconnected, with the same client. It's server-side, 100%.