Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Add wayyyy more documentation than is healthy | Thomas Voss | 2022-01-17 | 1 | -1/+8 |
| | |||||
* | Add support for the game actually ending | Thomas Voss | 2022-01-14 | 1 | -0/+1 |
| | |||||
* | Inform the clients of various events via alerts | Thomas Voss | 2022-01-13 | 1 | -0/+1 |
| | |||||
* | Basically make the whole game work | Thomas Voss | 2022-01-13 | 1 | -3/+5 |
| | | | | Too many changes to write a commit message, just read the code. | ||||
* | Be a bit more verbose in message descriptions | Thomas Voss | 2022-01-10 | 1 | -3/+3 |
| | |||||
* | Create a Messages enumeration | Thomas Voss | 2022-01-09 | 1 | -0/+5 |
| | | | | | | | | This enumeration contains all of the different Messages that can be communicated between the clients and the server. The enum names should make the meaning of each obvious enough, but they still have comments besides them explaining who sends the message to who, and what the message actually entails. | ||||
* | Remove useless shit | Thomas Voss | 2022-01-06 | 1 | -50/+0 |
| | |||||
* | Used boilerplate code to restructure project, edited splash.html and added ↵ | MayteApolix | 2022-01-06 | 1 | -0/+50 |
routing functionality |