# The Sinfar EE Test server is officially live!! **Please read this carefully before you try connecting:** - Only the latest NWNEE 8193.37-15 build is supported. - There is no SinfarX client, and none of the Sinfar client modifications are available (So your characters will look ugly for now. Deal with it) - There is still a lot of work I need to do to optimize things so expect things to run slowly - Expect crashes and broken stuff everywhere - Turns out talking to Rodrick will crash the server... So don't do that for now :stuck_out_tongue: - The server should restart automatically after it crashes so if it stops responding, disconnect and reconnect When you find a bug or crash - please record it here: https://git.sinfar.net/public/issues/issues (log in with your nwn.sinfar.net login). If all you can tell me is that something is broken - I can't fix it. I need to know exactly how you broke the thing, the specific steps to reproduce the issue and any screenshots or other details you can provide. To direct connect to the server: `nwn-test.sinfar.net:5121` The builder site for the test server can be accessed at: https://nwn-test.sinfar.net (The website is bright purple to make sure you don't accidentally make changes to the 1.69 server) ## Builders/Scripts **To ensure you don't lose any work please read and understand this entire section** The test server will periodically be refreshed with the scripts, areas, etc from the 1.69 server. What that means is your changes on the test server may get overwritten unless you do them correctly. ### For Scripts Generally speaking, make changes to files on the test server for testing/development purposes. Once you have identified the change that needs to be made and actually saved long term - those changes will need to be made on the 1.69 scripts. There are lots of script changes however which either won't compile, aren't compatible, or just don't make sense for the 1.69 server. In those cases we have special preprocessor tags we can use: ```c void main() { // This code runs in all cases SendMessageToPC(OBJECT_SELF, "A message for everyone!"); // #NWNEE-START# // // This code will only run on the EE server // PrintString("This server is running NWNEE"); // #NWNEE-END# // #DIAMOND-START# // // This code will only run on the 1.69 server PrintString("This server is running 1.69."); // #DIAMOND-END# } ``` You can define blocks of code which will be ignored by the 1.69 NWScript compiler, but will be used by the NWNEE compiler. In the example above: - `SendMessageToPC(OBJECT_SELF, "A message for everyone!");` will be seen by both compilers - The code between the `// #NWNEE-START#` and `// #NWNEE-END#` will only be seen by the NWNEE compiler. Please note that all of the NWNEE specific code **MUST** be commented out as shown in the example - The code between the `// #DIAMOND-START#` and `// #DIAMOND-END#` will only be seen by the 1.69 compiler. This code should **NOT** be commented out ### For everything else For all other types of resources - if there is something that needs to be fixed do it on the 1.69 server. If it can't be fixed on the 1.69 server because it is an issue caused by EE - let NelaK know and we will try to fix however that resource is being handled by the server rather than changing that resource. ## Common troubleshooting - To view the server logs: http://nwn-test.sinfar.net:6688/ The username is `sinfar` and the password is `pass` - To get builder/dm access to the server - simply ask any DM