• Hello Guest! Did you know that ProjectKorra has an official Discord server? A lot of discussion about the official server, development process, and community discussion happens over there. Feel free to join now by clicking the link below.

    Join the Discord Server

Divide the builds into two parts: Big Bad Bugs (released sooner) and General-Beta stuff (longer)

MeskenasBoii

Verified Member
Nobody likes waiting for a bug fix. Yeah? However, we can patiently wait for new features to come!

Cut-to-the-chase: Bug fixes sooner - Features Later?

Don't know what do you prioritize first: bugs? or features? | but I think it would be better to fix game breaking bugs first (like the bottlebending screw up) and release a build only dedicated for bugs with little (minor) or no features includes. For the sake of the example, let's call them "Snapshots". And the rest plugin stuff with less important bugs and all the new gameplay features could be included after the snapshots, which includes and carries forward the bugs fixes from there to (this, for the sake of example, could be called like how it is already - "Betas")

Proposed idea: split the development/plugin (this could be applied for sub-plugins too) into two downloads:
1. Bug Builds: (dedicated only on gameplay/bending aspect breaking bugs, that really are like must-urgent fixes. I hope you got the idea).
2. Features (carries/includes stuff from the recent Bug Build, but everything else is included: such as new abilities, command changes, ect.)

It's no fun to wait for a build download when your have deal with a really big nasty bug, that ruins important bending aspect: bottlebending.
 
Top