base on PayDay 3 Server Emulator Attempt # PayCheck3 PayDay 3 (Live/Master Branch) Server emulator ## Disclaimer - You must own a legitimate copy of PAYDAY 3 to use this software, which can be purchased at https://www.paydaythegame.com/payday3/#buy - The contributors of PayCheck3 in no way support piracy, and actively ensure that PayCheck3 does not work with an illegitimate copy. We're sorry to have caused any confusion that this could be used for piracy. - This project is in no way affiliated or endorsed by Starbreeze Entertainment. # How to use the server ## Hosting PayCheck3 locally **The certificates created by `PayCheck3CertificateGenerator.exe` expire exactly 1 year after being generated. If you use this software, and it stops working 1 year after you made the certificates, you need to regenerate them and reinstall them.** 1. Download the latest release of PayCheck3. 2. Unpack the latest release and run `PayCheck3CertificateGenerator.exe` to generate the required **self-signed** SSL certificates. 3. On Windows: Double-click on the `cert.crt` file and click the "Install Certificate..." button. In the dialog that appears select "Current User" and click "Next". In the new dialog, select "Place all certificates in the following store" and click "Browse". In the "Select Certificate Store" dialog, choose "Trusted Root Certification Authorities" and click "OK". After choosing the certificate store, client "Next" and "Finish". If a dialog appears asking if you want to install the certificate, click "Yes". 4. Once the certificate is installed, add ```127.0.0.1 nebula.starbreeze.com``` to your `C:\Windows\System32\Drivers\etc\hosts` file. **To stop the game from using PayCheck3, remove this line from your `hosts` file**. 5. Run `PayCheck3ServerApp.exe` and PayCheck3 will start. ## Hosting PayCheck3 on a public facing server 1. Download the latest release of PayCheck3. 2. Edit `config.json` and change the `SSLCertificatePassword` value to the password of your server's SSL certificate. (If `config.json` does not exist, run `PayCheck3ServerApp.exe` at least once). 3. Put your server's SSL certificate, in PFX format, in PayCheck3's install folder and name it "cert.pfx". 4. Run `PayCheck3ServerApp.exe` and PayCheck3 will start. ### How can players connect to my server? For players to be able to connect to your public-facing PayCheck3 server, they will need to make the following edits to their PAYDAY 3 `Engine.ini` config file. **TODO** ", Assign "at most 3 tags" to the expected json: {"id":"2266","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"