Thread Rating:
  • 2 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Annual public releases of sanitized code
#2
(09-08-2017, 10:27 PM)cyberTripping Wrote: Regular code releases would help mitigate this, allowing for community hobbyist coders to help with bugs that the proper code maintainers may not have the time, energy, or will to fix. Whereas simply having one person tackle an issue may result in a solution eventually, exposing the problem to an entire community who, for whatever reason, may be particularly interested in a particular issue being solved would dramatically reduce the time it takes for such problems. It provides a wider span of perspectives which is a boon to problem solving, and as mentioned, may expose individuals with a vested interest in the broken mechanic to the code, allowing the issue to be taken on by someone with an actual incentive to solving it (eg, being able to play with their favorite obscure nerd toy.)

I agree with this wholeheartedly. Being a single active contributor code-wise for weeks on end is extremely draining and demotivating, and I really wish I had any power in order to fix the particular bug that was caused during a patch mismatch that broke projectiles. 2016 release had no issues when I tested that particular patch, but 2017 had something change about the projectiles that cause a new bug to crop up.
Reply


Messages In This Thread
RE: Annual public releases of sanitized code - by Crystalwarrior - 09-08-2017, 11:38 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)