First off, thanks for taking the time to contribute! 🎉
The following is a set of guidelines for contributing to Server Survival. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
- Fork the repository on GitHub.
- Clone your fork locally:
git clone https://github.com/your-username/server-survival.git cd server-survival - Create a branch for your feature or bugfix:
git checkout -b feature/amazing-feature
This project uses vanilla JavaScript, HTML, and CSS with Three.js. No build step is currently required for the core game, but we use a modular structure in src/.
- Open
index.htmlin your browser to run the game. - Make changes in the
src/directory orgame.js. - Reload the browser to see your changes.
index.html: Main entry point and UI structure.game.js: Main game loop and logic (currently under refactoring).src/: Modularized code.entities/: Game entities likeServiceandRequest.services/: Systems likeSoundService.config.js: Game configuration constants.state.js: Global game state.
- JavaScript: Use modern ES6+ syntax (const/let, arrow functions, classes).
- Formatting: Keep code clean and readable.
- Comments: Comment complex logic, but aim for self-documenting code.
- Ensure your code works and doesn't break existing features.
- Update the
README.mdif you change any game mechanics or controls. - Open a Pull Request against the
mainbranch. - Describe your changes clearly in the PR description.
Bugs are tracked as GitHub issues. When filing an issue, please include:
- A clear title and description.
- Steps to reproduce the bug.
- Expected vs. actual behavior.
- Screenshots if applicable.
By contributing, you agree that your contributions will be licensed under its MIT License.