[Poll Close] Discuss Changes and what not as mentioned in it!

[MeskenasBoii]

Hi.

The Documents were now revealed, so tell us what you think about the incoming/planned changes? Any feedback or criticism?

 

[xNuminousx]

Yes

 

[Jackson]

Yessir. I'm worried about the future of my server and the servers I am staff on.

 

[MeskenasBoii]

Count me in.

 

[MeskenasBoii]

Count me in.

 

[xNuminousx]

The community should be fully aware of what's happening with the plugin. People are invested in this plugin and should know what's happening rather then be left in the dark. I understand wanting a surprise, but people knowing what's happening and getting to give feedback would make this feel like a community rather than the staff doing projects that are kept secret. Seems like some Area 51 stuff going on. #ProjectArea51

 

[Loony]

The community should be fully aware of what's happening with the plugin. People are invested in this plugin and should know what's happening rather then be left in the dark. I understand wanting a surprise, but people knowing what's happening and getting to give feedback would make this feel like a community rather than the staff doing projects that are kept secret. Seems like some Area 51 stuff going on. #ProjectArea51

How can we let the community know what's happening when we don't even have a final version yet and things are STILL subjective to change?????????????

 

[Jackson]

How can we let the community know what's happening when we don't even have a final version yet and things are STILL subjective to change?????????????

They would be subject to change either way based on the communities choices. I gave the option to only show the things that are 'mostly-set-in-stone'. You shouldn't be so quick to say that you don't have a final copy. We know and understand that, but it shouldn't be final without the community's concent anyways. This plugin is for us, and you. We should all agree. It's not just for you. It's not your personal/private plugin. If you want that, make it yourself. That's not how I'm accepting this community to run.

I understand where you're coming from, but I don't think any of us care if it is fully done or not. We want answers, we want to know what it going on. Because if ProjectKorra is heading for the worst, I'd want my server to change accordingly and I'd want to see what I can do about it before it's finalized. I think I speak for a lot of people when I say that we want to know what is going on and we don't want to be kept in the dark.

Now, back to the leaked document:

With the WaterBubble removal, 'it isn't cannon', but then again, keep in mind that it wouldn't kill people in the show. Think about how people got hurt/damaged in both shows.

Where as it isn't cannon, Tornado is one of the most used air abilities in my opinion.

I believe that with AirStream, there are multiple ways, at least 1 in every element, that can get out of it. Although there isn't with chi.

I am upset with the removal of Plant Armor as I thought it was a good quick-to move to protect water benders somewhat.

With TremorSense, highlight the players and mobs.

That's all I currently see, I will probably have more opinions on the matter later in the day/night.

 

[Loony]

We aren't removing WaterBubble. We aren't removing Tornado either. I'm not discussion a document that's false.

 

[xNuminousx]

They would be subject to change either way based on the communities choices. I gave the option to only show the things that are 'mostly-set-in-stone'. You shouldn't be so quick to say that you don't have a final copy. We know and understand that, but it shouldn't be final without the community's concent anyways. This plugin is for us, and you. We should all agree. It's not just for you. It's not your personal/private plugin. If you want that, make it yourself. That's not how I'm accepting this community to run.

I understand where you're coming from, but I don't think any of us care if it is fully done or not. We want answers, we want to know what it going on. Because if ProjectKorra is heading for the worst, I'd want my server to change accordingly and I'd want to see what I can do about it before it's finalized. I think I speak for a lot of people when I say that we want to know what is going on and we don't want to be kept in the dark.

I agree with this completely. Servers should know whether to prepare for a new project korra, not to update or ditch it entirely. Big updates like this, when involved with a community, should involve everybody rather than a few of the majority saying what happens and what doesn't.

 

[xNuminousx]

How can we let the community know what's happening when we don't even have a final version yet and things are STILL subjective to change?????????????

Letting us know of a final version is letting us know what has already happened, as in the update has already been made and no feed back is necessary. I believe we would like to be involved in the process of the update rather than just keep it to yourselves which is what the staff is doing, aside from the leaks and the "spoilers". Present your idea for the update, allow the community to give feedback, then see which of the ideas you'd like to go into the update.

 

[Loony]

I agree with this completely. Servers should know whether to prepare for a new project korra, not to update or ditch it entirely. Big updates like this, when involved with a community, should involve everybody rather than a few of the majority saying what happens and what doesn't.

So we need to ask permission to change things in the plugin we design?

No. No plugin works like this and you can't expect us to. Trust that the plugin is in good hands and we wouldn't add something that would make the plugin worse. We've scrapped additions at last minute when we've seen that it isn't beneficial to the plugin, like making FireBlast a multi ability. The fact that people think we are required to run everything by the community before we change things is ridiculous to me. It wouldn't work. We're hired as concept designers for a reason. We have server owners in the team to get feedback from the community and ask how they feel about certain changes. We took A LOT of the suggestions from the forums to plan for the next update. The community already has a lot of input, but the day where I start having to ask the community's permission before I'm allowed to do my job is the day that I loose all interest in actually doing my job.

The majority of the staff team like it. The people I've gave spoilers to, liked it. Trust we know what we're doing and don't write off the changes before we've even implemented them.

 

[SuperBower118]

Seeing this Google Doc got me thinking. If I made my own ideas about Element Reworks, would it be ok to make a thread that has a link to a Google Doc that has the rework? Since posting multiple ideas in a thread isn't allowed, I think it'd be a good solution.

 

[Loony]

Seeing this Google Doc got me thinking. If I made my own ideas about Element Reworks, would it be ok to make a thread that has a link to a Google Doc that has the rework? Since posting multiple ideas in a thread isn't allowed, I think it'd be a good solution.

Try posting it in general discussion rather than suggestions

 

[xNuminousx]

I completely trust that you guys can do a good job, you already have so far. I am not saying you need our permission before doing anything. I am saying to involve this community in the update. Update us on it's progress, ask us for opinions. Just tell us what's up. Whether that be showing us a list of what you feel MAY be in the update or telling us a little progress update and what you've completed so far.

 

[Jackson]

So we need to ask permission to change things in the plugin we design?

No. No plugin works like this and you can't expect us to. Trust that the plugin is in good hands and we wouldn't add something that would make the plugin worse. We've scrapped additions at last minute when we've seen that it isn't beneficial to the plugin, like making FireBlast a multi ability. The fact that people think we are required to run everything by the community before we change things is ridiculous to me. It wouldn't work. We're hired as concept designers for a reason. We have server owners in the team to get feedback from the community and ask how they feel about certain changes. We took A LOT of the suggestions from the forums to plan for the next update. The community already has a lot of input, but the day where I start having to ask the community's permission before I'm allowed to do my job is the day that I loose all interest in actually doing my job.

The majority of the staff team like it. The people I've gave spoilers to, liked it. Trust we know what we're doing and don't write off the changes before we've even implemented them.

We aren't saying for all updates. We are saying for big and major updates like these. We want to know what's happening. Therefore we should get to know what's happening within major updates at least.

 

[Loony]

We aren't saying for all updates. We are saying for big and major updates like these. We want to know what's happening. Therefore we should get to know what's happening within major updates at least.

Okay let me give you an example. What if we change something, put it out in the public and one guy dislikes it; let's say a server owner. Then that server owner gets all his players to also rage about this change and say they also dislike it. What happens then? Do we not do this change because from an outside perspective it looks like the community dislikes it?
It's very abusable.

I completely trust that you guys can do a good job, you already have so far. I am not saying you need our permission before doing anything. I am saying to involve this community in the update. Update us on it's progress, ask us for opinions. Just tell us what's up. Whether that be showing us a list of what you feel MAY be in the update or telling us a little progress update and what you've completed so far.

But we don't even have a final version yet. Even when we do, it most likely will change at last minute. Also, referee to what I said before your quote. If we updated you guys on what we had planned we would need permission, because if a lot of people hated it then we probably wouldn't do it - which means we're basically asking for permission.

I literally posted spoilers today for the 1.9.0 core, and the doc has been leaked and some ideas in there haven't changed. You basically have seen the plans, even though they've changed.

 

[xNuminousx]

If what you post about the update is going in the direction that Kiam and/or Mist wants the plugin to go, then no, you don't need our permission. That would be a little update, telling us what's going on. However, maybe you guys aren't sure about something so you want some other opinions. You can find many ways in getting the community invloved in the update without asking permission if that's what you're so scared about.

 

[xNuminousx]

Your "Super secret leaked information" was a great idea in getting people involved. You were able to get feedback on those things and you were able to get other opinions on something that maybe you missed.

 

[SuperBower118]

Okay let me give you an example. What if we change something, put it out in the public and one guy dislikes it; let's say a server owner. Then that server owner gets all his players to also rage about this change and say they also dislike it. What happens then? Do we not do this change because from an outside perspective it looks like the community dislikes it?
It's very abusable.


But we don't even have a final version yet. Even when we do, it most likely will change at last minute. Also, referee to what I said before your quote. If we updated you guys on what we had planned we would need permission, because if a lot of people hated it then we probably wouldn't do it - which means we're basically asking for permission.

I literally posted spoilers today for the 1.9.0 core, and the doc has been leaked and some ideas in there haven't changed. You basically have seen the plans, even though they've changed.

Well realistically speaking, generally, servers really don't have all of their community on the PK forums, just so you know. Many people in fact don't even KNOW of this site. But in your case, you're hearing from the perspective of a totally different point-of-view from a bending community that uses the bending plugin. If the players all rage about this one addition, then it should generally be easy to boil down their complaint. You should also keep in mind the configuration differences the server may have, and any addons, which might taint the people's point-of-view on the Bending Plugin itself.