L2J Changes
Posted: Sun Apr 27, 2014 10:45 pm
A few weeks ago I asked most people related to L2J:
What would you do if they were in my place (Project Leader)?
I’ve got very interesting answers, the most challenging were not from people that was close to the team, but from those that from some (known or unknown) reason distanced from the public development.
The most interesting things that were mentioned to me are:
What would you do if they were in my place (Project Leader)?
I’ve got very interesting answers, the most challenging were not from people that was close to the team, but from those that from some (known or unknown) reason distanced from the public development.
The most interesting things that were mentioned to me are:
- Change the task system.
- Divide tasks between developers.
- Use a task system, other than forum thread.
- Public.
- Get/hire more developers.
- Focus on fixing existing bugs.
- Prevent introducing new bugs.
- Fix exploits as fast as possible.
- Focus on stability .
- Memory leaks.
- Deadlocks.
- Performance.
- Keep up with newer game versions.
- Reduce the time it takes to fix small problems.
- Reduce the time consumed on obscure things, such as code refactoring, code comments, renaming, porting, etc.
- Reduce the time that takes to integrate important features to the server.
- Improve game customization, make it easy to manage and maintain.
- Avoid unanswered threads, at least one person from the team should answer it.
- Reduce long time synchronization between stable and beta branch.
- Less :
- Ranks.
- Talk.
- Inactive developers.
- More:
- Team work.
- Collaboration.
- Code.
- Outdated wiki and documentation.
- To be more flexible.
- Allow unfinished or imperfect work to be committed.
- Allow small commits instead of huge reworks.
- Give the source structure (follow a pattern design).
- Develop 3rd party features.
- Web admin panel.
- Deployment kit.
- Include paid services to motivate developers.
- Server deployment.
- Configurations.
- Custom features.
- Implement an official L2J Server for testing purposes.
- Make L2J run on pure Java.
- Keep L2J as close as retail as possible.
- There will be a forum integrated, public, mandatory task list manager.
- A priority list will be set for the work flow:
- Exploits
- Stability issues
- Bugs
- Small problems.
- Medium problems.
- Large problems, that require a large rework.
- Reworks
- Missing features
- Custom features
- A code standard will be set, public and mandatory.
- An alpha branch will be set up to develop client compatibility with newer game versions. viewforum.php?f=105
- A synchronization date will be set for stable and beta branches.
- Team rules will be set.
- Inactive members will be removed/retired.
- Problematic members will be removed.
- Wiki and documentation will be updated after the source has changed.
- A promotion system will be implemented to increase the feedback.
- A collaboration system between forks and future integration.