• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Official forums for games

Status
Not open for further replies.
Joined
Feb 17, 2012
Messages
833
I'm just curious if official forums for all games are like this.

This is going to be a kind of long post, because I believe things should always be taken in context. When you take things out of context it gets a little crazy.

I'm the guild leader of a guild that has been WW1 in EQ2 for years now. At this point, the devs really don't like us. I'm opinionated, if I think an encounter is poorly designed/broken I'll tell you. I might come across as an asshole, but I don't just go I'm right you're wrong neener neener, I'll actually tell you why it's broken and how you can fix it. The vast majority of the changes to raid content for the past 4-5 years have been based on my feedback. When I feedback an encounter I try to get as little changed as possible that will make it killable while maintaining the flavor of the encounter. Generally when they get changed based on my feedback someone will kill them, but it's a slow stream of kills over a prolonged period of time, not a rush of kills all at once.

I've had a rash of posts getting deleted on the EQ2 forums lately, some of them are laughable. I want to know if you guys think I'm out of line and why, or if some of this is just really laughable moderation.

Context: Beta testing a new raid zone they posted they were only going to give very limited access to very few guilds to test the zone, and only pieces of it at a time. This is after one of the previous zones they released had a mob that literally took 6 months to get fixed. Every time they patched the mob they broke something else. Oh, and that's after when the mob was launched we got told "The mob works fine, you just need more practice." Followed by those 6 months of the mob being broken in numerous different ways. A mob that I told them all the broken stuff before it ever went live for just a couple pulls in that Beta. Said mob spawned 3-4 different very long threads over those 6 months about all the things wrong with it and why it was such a bad encounter.

The following was deleted for the reason that it was "nonconstructive"

"That's a rather cynical point of view. Especially after some of the things lately you'd think the objective would be to get as many eyes on it as possible and make sure it functions in a reasonable manner that people might enjoy."

Context: There is a very very long solo quest line that you have to complete to unlock the ability to loot the current tier token rewards for group/raid. The tokens allow you to buy adorns (stuff you slot in gear) and some group level gear. With the most recent patch they added a second tier of token gear that was basically equal to the current lowest tier raid gear, but requires the previous piece as well to buy it. The stuff from the tokens is heirloom (account bound and you can trade it to your alts). When you equip it is bound to that character. Someone created a thread talking about how it sucks because you can't take the piece of gear off the alt to give it to the character that can actually purchase it, meaning they would have to do the really long and tedious solo quest line again. My response (and I've posted a few times elsewhere about how the solo quest line should not lock group and raid stuff) that was deleted for trolling.

"The endless joys that have come from locking this stuff behind a completely unnecessary absurdly long and boring solo quest line for all things not solo."

Context: The new raid zone previously mentioned that has now been live for about 5 weeks. It's discussing the Challenge Mode (hardest version) of the mob that has yet to be killed. To anyone who has actually done the encounter it's blatantly obvious that the dps check is out of line and just way too high, making the encounter unkillable.

The dev posted the following 2 posts

EQ2Dev said:
I know the trend lately has been to wait till fights get patched to kill them as soon as the patch goes live but I don't think that strategy will work with these. We are addressing issues and fixing bugs as we see/get them reported. I would not suggest just sitting back and waiting if you want to be the first to kill some of those really challenging encounters. Many of the things that are being complained about in this thread have already been fixed and have been on live for a while now.

We fully intend for these fights to remain very challenging. We will not be dropping the difficulty, only fixing bugs. The rewards from the fights are scaled to the difficulty of beating the encounter.

EQ2Dev said:
Barring any bugs, yes. If there are still bugs we will get them worked out and worked out quickly.

Some examples of bugs that have been addressed are the resisting of dispells, pool color change effects hitting same person more than once at a time, urchins killing players when they are too far from healers, Erratic heals from the Talan clone, and a few more in there. We are keeping a very close eye on it but we also are taking care not to interfere with the "figuring the fight out" part of the game as well. We will not be telling you if you are doing a particular part of the fight wrong.

As a note, some of the fixed things weren't problems (urchins killing players too far) or weren't fixed at all (pool color). My following post got deleted pretty quickly for "trolling"

"So the devs believe that the players shouldn't know what changes in the game? Things should just be ninja patched into the game? So you're avoiding patch kills by just not telling players you patched the encounter? That doesn't make it any less a patch kill, it just means that instead of everyone being on an even playing field because they know exactly what changed and how they can adjust they have to guess at the encounter every time they pull it. It's laughable at best.

Have you adjusted the dps check that EVERY SINGLE PLAYER who has posted about this encounter said needs to be changed for the encounter to be killed?

People don't take the devs seriously because of posts like this that are so out of touch with reality. This encounter has been live for a long time now. Do you really expect people to just sit there and pull an encounter every day hoping something has changed because you won't tell them you're adjusting the encounter? You know what that leads to? Burn out. People quitting. No one wants to do that. No one wants to sit there every single day pulling a blatantly unkillable encounter with an out of control dps check because maybe the encounter got changed and isn't in the patch notes.

Intentionally leaving things out of patch notes because it is supposed to promote competition is the most laughable thing I've seen on these forums. It almost reaches levels of everyone just needs more practice on Drinal, it isn't broken at all and is working as intended."

Then later that night after again pulling said mob that they aren't going to include changes in patch notes for I posted the following. As for why so many really's, that's actually directed at the forum admin because if you post something along the lines of "this is abysmally horrible" it gets deleted for trolling. The following post was then deleted for "discussion of moderation" and I got suspended for 3 days. lol.

"Speak the truth, post vanishes. Cool story.

This encounter isn't killable. The War Council has no business healing. This encounter is going to be ridiculously long as it is, the heal is really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really really dumb and completely unnecessary.

The urchins need to change. Something has to give with them. Either you're intended to kill them, in which case they have too much hp and spawn too much. Or you're not intended to kill them, and they spawn to fast and hit people too far away. If you are intended to kill them the heal on the war council is even more out of line.

Not to mention, the urchins haven't been fixed. Like I've said previously, the problem wasn't them killing the person they were on. The change to make them not auto attacked. The problem is they aren't locked to person they are on. They'll drop agro and move 5m towards the raid and then go back. That means you need to be even farther away or it's going to nuke the raid when it does that.

Not including changes in patch notes doesn't make it any less a patch kill. It just makes it a who isn't burned out on pulling blatantly impossible mob kill, that was killed after it got patched without patch notes."

What makes this even better? How could it possibly get better you ask! They then proceeded to backtrack both points I just got suspended for "trolling" about (not putting stuff in patch notes being incredibly dumb, and the mob is not fine it needs to be changed) .
Different EQ2 Dev said:
We'll be making some tweaks to this encounter today. Changes/fixes will be called out in patch notes.




Am I out of line, or is this just laughable? All I can really do is laugh, because at this point I can't help but find it really funny.
 
Status
Not open for further replies.
Back
Top