Originally Posted by Frieza_Prexus
[You must be logged in to view images. Log in or Register.]
Well said, but the issue between classic and not classic and what to do about it is really blurred by the emergent gameplay both here and on live. Where we should land on the "what to do about it question" is up for debate, and there's not a perfect answer. No matter what is done in any particular situation, both sides for or against a particular change can validly jump up and down while screaming not classic. It's almost a complete impasse. I think the most reasonable situation is what I mentioned earlier which Falkun echoed (though I think he misread my post; I was agreeing with you!). All classic mechanics should be reproduced in their entirety, and changes should be made only under two circumstances:
1) It's an obvious bug or unintended/emergent gameplay that does NOT add value to the game then (1999), or now. Examples being the Paladin epic 1 million damage dot, the Wavecrasher bug, and being able to forage dropped loot in certain zones. All of these are clear-cut situations where the developers intent would be ascertainable with almost absolute certainty had they known of the issue at the time.
OR
2) The problem here is such that it effectively prevents any modicum of classic EQ, and to leave the situation as it is would render the situation more non-classic than it would otherwise be.
These are both very difficult standards, you either have to know with 99% certainty what the Devs would have done, or you have to prove extreme detriment to the gameplay of the server. Note that the standard is the gameplay and not the effect it has on the interactions of players. These are both rare and difficult situations that can occur, but should be met with caution. That's why I think that there is a presumption that the server should strictly adhere to the timeline, and that any deviation must first overcome a presumption that strict adherence is in the server's best interest.
Many of the supposed problems are not really problems at all. For example, SoulFire is currently used in two fights: Trak and VS. Trak is, in my opinion, not at issue because of the SoulFires. Sure, they help, but pulling off a Trak kill that otherwise wouldn't happen without them is actually a very rare and specific circumstance. SoulFire is also used to tank VS while your crew assembles. VS doesn't proc often enough in my opinion, and that fix would be more than enough to make SF tanking that much more difficult. SoulFire wouldn't be as much of an issue if the server were more classic ironically.
Might SoulFire one day be a problem? Absolutely, it could perhaps trivialize some gameplay, then again perhaps not. However, no matter what happens, the burden to change it is on the ones requesting it. That burden has yet to be met in this particular case.
|
07-22-2013, 05:19 PM
Threaded Mode