1.8.0

It is still safe to depend upon the 1.8.0 code-disaster steamworks4j artifact because we did not modify anything in that library, to build this successfully I had to:

1. download the steamworks sdk to ./sdk (version was 152 when I released 1.8.0)
2. cd to cd ./sdk/public/steam/lib/linux64
3. run patchelf --set-soname libsdkencryptedappticket.so libsdkencryptedappticket.so
4. cd ../../../../../server to get to the server directory
5. open up pom.xml and change version to 1.8.0
6. run mvn deploy -Plibs -DaltDeploymentRepository=faceit-nexus-private-releases-repository::default::https://nexus.faceit-infra.com/repository/maven-releases

This will release com.faceit.steamworks4j-server:1.8.0 to the private nexus repo, the -Plibs is necessary to package the .so library files from the sdk into the maven jar.

Note I did not tag this repository properly as a 1.8.0 tag already exists in the upstream repository, which prevented me from tagging 1.8.0 (even though that was the artifact that I released to nexus) so I used 1.8.0-faceit as my tag, the reasoning behind this was that while our 1.8.0 artifact is different I wanted to be able to stay in step with code-disaster in case he released any fixes or improvements.