User Details
- User Since
- May 26 2023, 2:30 AM (77 w, 6 d)
May 26 2023
Fair enough. I just started this stuff about 6 months ago. My patience are wearing pretty thin, already. It's unfortunate but it is what it is, best of luck to you! Hopefully they get it it figured out soon enough. I agree it is a ripoff plain and simple, why I still participate is beyond my understanding but I care about the community and enjoy the comradery that the game facilitates with a good group of people. It's a good game, it's just a shame it gets taken care of so poorly.
I've added this line to the server config export through nitrado thinking it might work and achieved nothing. My files validated and worked fine, the line of code did nothing. I also tried to add it to the cfggameplay file but it doesn't belong there. It belongs in a file like serverDZ.cfg which is a file we don't have direct access to, we have access to server configuration parameters stored in a file on the Nitrado Web Interface, the file can be located as an export through the general settings of the web interface. The issue may be that the formatting is different between the two files, the traditional .cfg file reads as: 'disableMultiAccountMitigation = false'. When you export the Nitrado config file the parameters are formatted as such, instead: "nolog":"true" or "disablePersonalLight":1...
There should be a way to patch this into the server config export on the Nitrado Dashboard. If a person was to download the config file export (the one that contains server name, where you enable cfggameplay file from) they might be able to figure out a way to enable it through that file. That's the only place it could realistically go on console, unless there is a place for it in cfggameplay.json we don't know of yet.