NOTE: This is the first iteration of this file. You're welcome to pull request changes
When creating issues, whether to track a bug or suggest a feature, please try to follow this set of rules:
- When filing a bug report issue, please attach a log file ( Located in
R2Northstar/logs/
). - Short, consise. No-one wants to read an essay on why x should be added.
- When applicable attach a short video / screen shots to better convey what the issue is about.
When creating a pull request please follow this set of rules:
- 1 Fix/Feature should equal to 1 Pull Request. The more you do in 1 PR the longer it'll take to merge.
- Mark your Pull Request as draft if it isnt finished just yet.
- Properly format your code. As we currently don't have a formatter we're very lax on this. That doesn't mean you don't have to try to format your code.
- Mention how to test your changes / add a test mod to make it easier to test
A basic set of rules you should follow when creating a Pull Request
- If you're adding a new file you should add a doc comment noting what the file does and its origin
Alternative to
///----------------------------------------------------------------------------- /// Origin: Northstar /// Purpose: handles server-side rui ///-----------------------------------------------------------------------------
Origin: Northstar
would beOrigin: Respawn
- Each function should have a header doc comment
///----------------------------------------------------------------------------- /// Sends a string message to player /// Returns true if it succeeded ///----------------------------------------------------------------------------- bool function NSSendInfoMessageToPlayer( entity player, string text )
- Functions should have spaces in the parentheses
bool function NSSendInfoMessageToPlayer( entity player, string text )
- If a function need to be threaded off using
thread
it should have a_Threaded
suffix
- Files should use tabs for indentation