Michatec/wk_wars2x
1
1
Fork 0
mirror of https://github.com/Michatec/wk_wars2x.git synced 2026-04-01 00:16:27 +02:00
Code Issues Packages Projects Releases Activity

Update README.md

Browse Source
This commit is contained in:
Dan
2020-03-06 23:28:47 +00:00
committed by GitHub
parent 2e89ac54f9
commit bd76fc5b27
1 changed files with 11 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
README.md
View File

@@ -11,16 +11,16 @@ It's now installed! When you boot your server you should see a Wraith ARS 2X mes
## Default key binds
Although these can be viewed ingame through the operator manual, the default key binds are listed below.
| Action | Key |
| ------------------- | --------------------------- |
| Open remote | F5 |
| Close remote | ESC or right mouse button |
| Lock front antenna | Numpad 8 (full) / 1 (small) |
| Lock rear antenna | Numpad 5 (full) / 2 (small) |
| Lock front plate | Numpad 9 (full) / 3 (small) |
| Lock rear plate | Numpad 6 (full) / 4 (small) |
| Toggle keylock | L |
| Toggle key bind set | K |
| Action | Key |
| -------------------------- | --------------------------- |
| Open remote | F5 |
| Close remote | ESC or right mouse button |
| Lock/unlock front antenna | Numpad 8 (full) / 1 (small) |
| Lock/unlock rear antenna | Numpad 5 (full) / 2 (small) |
| Lock/unlock front plate | Numpad 9 (full) / 3 (small) |
| Lock/unlock rear plate | Numpad 6 (full) / 4 (small) |
| Toggle keylock | L |
| Toggle key bind set | K |
## Changing the UI file save type
As the UI can be moved and scaled, the system also saves the UI data as it is set by the user. By default, this identifier type uses `license` to name the JSON files saved in the `saves` folder. This can easily be changed by opening the `sv_saving.lua` file, then looking for the following line of code at the top:
@@ -146,4 +146,4 @@ CONFIG.uiDefaults =
If there is an improvement that you think should be made, open a pull request with your modified code, I will then review your request and either accept/deny it. Code in a pull request should be well formatted and commented, it will make it much easier for others to read and understand. In the event that you want to suggest something, but don't know how to code, open an issue with the enhancement tag and then fully describe your suggestion.
## Reporting issues/bugs
Open an issue if you encounter any problems with the resource, if applicable, try to include detailed information on the issue and how to reproduce it. This will make it much easier to find and fix.
Open an issue if you encounter any problems with the resource, if applicable, try to include detailed information on the issue and how to reproduce it. This will make it much easier to find and fix.