3.0 Alpha
Found a bug? Please specify in the title what version number via brackets you're using. I.e.
- [2.0.3] - Indicates the issue is in the official latest release.
- [Git] - Indicates the bug is present in the github. Please include a link to which commit you are using if possible.
These rules are for contributing directly towards Doom4Doom via pull requests.
- No DECORATE allowed.
- DECORATE is now considered a thing of the past now that ZScript is on the rise for this mod.
- Detail your commits.
- You must specify all that has changed if you wish to have a higher chance of acceptance.
- Notify us of defects/caveats.
- If you know something doesn't work, or there is a potential issue, tell us. We will port it over into a branch and help you figure out what the problem is, so you can see your code merged with ours even sooner.
- Rejections may not be final.
- If you are asked to change something, chances are the Pull Request may not be closed. It all depends on how big and complex the code is.
- Pull requests may be contested with the primary developers at any time, which may delay the process.
- If a PR is ultimately declined for a specific permanent reason, it is considered final and should be dropped.
- Use a program like SourceTree or GitKraken to upload files.
- Avoid using GitHub directly. With the aforementioned programs, you can commit all your files at once versus one at a time.
- You only need one of these.
- SourceTree: https://www.sourcetreeapp.com/
- GitKraken: https://www.gitkraken.com/
- Use proper indentation.
- Tabs, not spaces, should be used when making adjustments. As such, you should use a programming notepad or SLADE to perform the edits.
- Be Patient.
- We all have lives to deal with. It may take time to go through and sort out all the issues and pull requests, depending. If you have the mail system set up and watch this project, you'll be notified of any activity pertaining to the issue/pull request.
GZDoom 2.5.x
See the Changelog inside the Docs tab for the most up-to-date changes.