Post by Deleted on Aug 23, 2020 19:50:51 GMT -5
So I'm mostly saying this from a very odd position, so just forgive me if I ramble slightly at points.
When the Siphon change got introduced, people freaked out. Got annoyed. Not because of the change itself, but because of how it looks intent wise. I know better than to think I'm purposely being targeted, but the way it looks paints a different picture when Lilim and I's battle didn't even have 24 hours on the board before that change was implemented. I found myself personally mixed. I loved the change, yet I hated the timing.
We, as a site, have a very bad tendency of choosing when things are done retroactively or not. A very good example of this is the siphon issue and the token item issue.
A couple months ago, Recoome stole Vash's 10 token item, the Energy Siphon. Not soon after, token items were made unstealable, but Recoome was allowed to keep his siphon. This is fine and dandy, we're not doing retroactive changes, so it was let go after a bit of argument.
However, now we're doing the Siphon changes and things are being retroactively fixed as far back as PAIN and Azazel's battle with the siphon. This is.. well, I don't think it works.
I don't care what the result of the above statements are. They are simply to emphasize the point I want to make here:
I think we need a Beta environment for ADBZ.
A public one at that. Instead of suddenly implementing changes, we need to introduce them in a different manner. Every 2 to 4 weeks, on the update cycle, a list of changes will be put out based on what the site has asked for or what might need to be implemented. From there, we can either test things out (in terms of battle changes to see what can be broken and what should be fixed) or people can publicly give their opinions on what needs to be changed or shifted around. And at the end of the beta cycle, we implement what the final results are based on public opinion. A vote for each change, so to speak.
On top of this, no changes should be added in the middle of a beta cycle. This is to avoid the Siphon issue again. ADBZ has a bad rep of leaving problems problems until certain people are utilizing it and that needs to stop right now. If it's an issue, add it to a list for the next Beta without disabling things, don't be reactionary, let the public choose what kind of game they want to play.
I don't think it's an issue to attempt to cater to the general playerbase on what they'd like to see out of the game and this will allow staff to be much more transparent. No more hotfixes, no more sudden changes for the better, just an environment where we can talk upcoming changes out and figure out whether they'd harm or help the site's health as a whole.
Thank you for reading and I look forward to learning your thoughts on this.
TL;DR: Beta environment. Read for details.
When the Siphon change got introduced, people freaked out. Got annoyed. Not because of the change itself, but because of how it looks intent wise. I know better than to think I'm purposely being targeted, but the way it looks paints a different picture when Lilim and I's battle didn't even have 24 hours on the board before that change was implemented. I found myself personally mixed. I loved the change, yet I hated the timing.
We, as a site, have a very bad tendency of choosing when things are done retroactively or not. A very good example of this is the siphon issue and the token item issue.
A couple months ago, Recoome stole Vash's 10 token item, the Energy Siphon. Not soon after, token items were made unstealable, but Recoome was allowed to keep his siphon. This is fine and dandy, we're not doing retroactive changes, so it was let go after a bit of argument.
However, now we're doing the Siphon changes and things are being retroactively fixed as far back as PAIN and Azazel's battle with the siphon. This is.. well, I don't think it works.
I don't care what the result of the above statements are. They are simply to emphasize the point I want to make here:
I think we need a Beta environment for ADBZ.
A public one at that. Instead of suddenly implementing changes, we need to introduce them in a different manner. Every 2 to 4 weeks, on the update cycle, a list of changes will be put out based on what the site has asked for or what might need to be implemented. From there, we can either test things out (in terms of battle changes to see what can be broken and what should be fixed) or people can publicly give their opinions on what needs to be changed or shifted around. And at the end of the beta cycle, we implement what the final results are based on public opinion. A vote for each change, so to speak.
On top of this, no changes should be added in the middle of a beta cycle. This is to avoid the Siphon issue again. ADBZ has a bad rep of leaving problems problems until certain people are utilizing it and that needs to stop right now. If it's an issue, add it to a list for the next Beta without disabling things, don't be reactionary, let the public choose what kind of game they want to play.
I don't think it's an issue to attempt to cater to the general playerbase on what they'd like to see out of the game and this will allow staff to be much more transparent. No more hotfixes, no more sudden changes for the better, just an environment where we can talk upcoming changes out and figure out whether they'd harm or help the site's health as a whole.
Thank you for reading and I look forward to learning your thoughts on this.
TL;DR: Beta environment. Read for details.
