Originally Posted by haxray
shouldn't a debate about ff2 take place on the ff2 thread... Even if waka started it?
Also, allowing anyone to make stuff leads to low quality content, yes, but also leads to higher quality stuff, and the ability to fix the low quality stuff easily. The problem with ff2 stems more from the amount of bugs and weird features. I seen enough servers running their own fork of ff2 that all have some changes in common. If all of these people are doing the same fix or changes, seems kinda... Stupid not to make them to the main one, the most common example i seen is removing the default damage buff/increaser.
tl;dr: vsh > ff2.
Here's the main problem with BOTH VSH and FF2. You have all this timer soup, and most of you know already how those timers are prone to being unreliable. Even if VSH is far more stable than FF2, VSH itself is prone to having its own issues (*cough* anyone's server hanging with the spawn teleport? *cough*). Then again, i can't blame the current maintainers of both plugins, since the original coder was a novice, therefore, inheriting all of VSH's and FF2's problems.
I appreciate that Chdata and Wliu keeps their respective plugins up-to-date, but tl;dr, it's gonna take a complete rewrite to resolve all of the issues VSH and FF2 has.
Now here's the problem i have with FF2, mainly. Though it's supposed to be far more customizable for the novice user, it's far more limited for those who know what they are doing. Just look at sarysa for example. She's had to write up several workarounds to get around FF2's limitations.
Let me also say something about the natives. As sarysa once pointed out, as she writes for a community whose fork is based on 1.06h (while mine is based on 1.10.4), the fork she writes for lacks many of the features the current 1.10.x has, so it's impossible for her to take advantage of the latest features. Her use of reflection is something to consider to use.
And with Wliu with plans for an FF2 v2, i just can't put up with having to rewrite subplugins and configs just so they work in a version that has too many breaking changes. It's also the reason why after my last batch of updates are released, i'll pretty much be done with public bosses so i can focus on keeping my FF2 fork up to date and to prepare it to be forwards-compatible with v2 bosses, that is, if anyone is willing to take the daunting task to update them.
Now once v2 is released, who will take the task of converting every single subplugin and boss out there to make it work with FF2 v2? It's just something for the FF2 folks to think about. It's a plus if you have server operators that take their time to make the changes themselves, but most server operators just simply want things to just work. What are they going to say when their v1 configs and subplugins no longer work after upgrading to v2?
Why not just simply fix the broken code? Instead of having to reinvent the wheel? Just simply touch what's broken, and don't touch what isn't.
Or at least, if you are re-inventing the wheel, try to keep backwards compatibility with it's predecessor.
That's all i have to say about this matter.