Lol, nice effing patch brehs.
At one point in time, I tossed an offer into IRC to lend my programming skills to the mod. I am currently a senior lead developer on a multi-million dollar FAD (Federal Aerospace and Defense) account. But gawd am I glad chadz was too busy sniffing his own farts in scrubland (Europe).
We in the biz like to deliver quality products, our software is our namesake. This latest patch (among other failures) has really brought forth to the community the professionalism behind the 'Dev Team'.
Just cuz I'm bored I'm gonna throw out a few snazzy phrases/words that we programmers in the professional world use when engaging with customers.
Requirements - One of the most important pieces to the software puzzle. If you don't know what you're building, there is no way to deliver a product to the customer (CRPG Community). Process Architects will visit on site and gather all necessary requirements to please the customer (CRPG Community) and provide them with the most value.
Component Design Documentation - Some form of documentation, most often reviewed with the customer (CRPG Community) to get sign off/acceptance, that shows the desired path to complete the list of
requirements, also multiple solutions may be provided with a risk/reward definitions to give the customer (CRPG Community) options on how to proceed.
Development Cycle - Once a solution is approved and work begins, a solid development team is necessary to ensure the proposed solutions will be achieved with a high quality of work.
Use Cases - As part of the
requirements gathering, a
use case document will be defined as a means to show the solution has successfully achieved a customer (CRPG Community)
requirements. For example: Use Case 1: When a user logs into cRPG he is not flooded with texture fail to load errors. Use Case 2: When a user holds left click and drags their mouse back to perform a stab, the animation does not appear to be a turd. Use Case 3: When a user equips a legacy helmet ITS FUCKING MODEL DISPLAYS.
Test Cases - This is where the developers take each use case, and provide a list of steps that can be used within the solution that will achieve a success on the equivalent use case. Problem here is boys this requires TESTING and obviously nobody tested this turd.
End User Acceptance - After your solution is wrapped up in a neat deliverable and shipped off to the customer (CRPG Community), a phase of end user acceptance will occur, where bugs will be reported, and users are trained on the solution. Eventually giving legal signoff that the requirements have been met. It is possible if a turd solution is delivered, those providing the solution via a work contract would be flirting with lawsuits from the customer. Here is the link to the current bug list, as we are unware of any real ticketing service such as JIRA the 'Dev Team' uses:
http://forum.melee.org/crpg-technical-problems/4-1-bugs-thread/Theres a bunch of other processes that occur in the business world, and it varies from company to company, but thats the jist of things. I asked for a subversion link for the cRPG repository JUST TO LOOK, unless I had commit rights I couldn't even fucking touch their source code. But heaven forbid folks attempt to help this flop.
You guys put that flashy ass banner now, 'MELEE BATTLEGROUNDS THE GAME DERPA DERPA', you really want these tainted builds going on your record when you're actually trying to start a gaming company?
Get some processes established, have code reviews, TEST THE FUCKING CODE IN A TEST ENVIRONMENT BEFORE PUSHING IT TO PRODUCTION. It seems like the new guys attempted to appease the customer (CRPG Community) with some of the item adjustments, and thats a good thing we are somewhat being heard, but for fucks sake with this regression. How does a 'mail coif' thats been in the game for years suddenly not display a model? How do you push a production build with 100s of texture load errors.. it looks like you never even launched the game to test it OTHERWISE YOU WOULD HAVE SEEN ALL THIS SHIT.
edit: added bug list.. please go here and post bugs so this shit may one day be fixed
TLDR: Learn to run a business/program