Page MenuHomeFeedback Tracker

Disable multi-account mitigation not working on Xbox.
Acknowledged, UrgentPublic

Description

This information was posted as a comment on another thread. I wanted to make a dedicated report for Xbox, as that is the platform I use.

Currently there is no obvious way to integrate the new multi-account mitigation feature into the config files...as we don't have access to a serverDZ.cfg file...instead we use Nitrado's native config file which is formatted slightly different than a typical config file since its written in .json instead. I believe the issue is that we don't have access to the traditional config file and therefore need a special definition created in .json that can be called to reference this parameter. Nitrado has lots of parameters that translate directly to the vanilla serverDZ.cfg config file, they are just written in .json. I don't think it will work for us at this point without Bohemia writing some code or Nitrado adding another parameter to our web interface...

So...

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...

Neither of those formats agree with the format Bohemia has indicated we use to enable this parameter, and they told us to put it in a file we don't even have direct access to. Either the community isn't understanding here or someone isn't giving us enough information.

In order to add it to the config for console I imagine it would have to be in a format such as those last two I listed.

The line I initially added to the export file was 'disableMultiAccountMitigation = true'.
I tried "disableMultiAccountMitigation": "true" as well as "disableMultiAccountMitigation": 1 none of this worked.

Details

Severity
Major
Resolution
Open
Reproducibility
Always
Operating System
Windows 7
Category
Server
Steps To Reproduce

Write multi-account mitigation parameter into code as "= true".
Sign in with an xbox live account and log into DayZ.
Log Out.
Get 5 second timer.
Sign in with a separate alternate xbox live account and log into DayZ.
Get 4:30 second timer.
Repeat with different variations of source code parameter.

Event Timeline

WithaReazn updated the task description. (Show Details)
WithaReazn updated the task description. (Show Details)
medic_overseer added a subscriber: medic_overseer.EditedJun 2 2023, 8:00 AM

Nitrado on 5/31/23 added the disableMultiAccountMitigation option as a checkbox in the general settings. Its right after enable cfggameplay. However, its not working. I talked with Nitrado and they really have no idea what Im talking about. they think that this option has existed for quite some time and it just stopped working. They kept trying to tell me that they cant change that setting and its in the code and I have to do it. I sent a screenshot and they finally started trying to look into it. The ticket has been open for 24 hours but nothing has changed as far as I know.

My suggestion would be to have bohemia completely disable or remove this timer until the ability to disable it across all platforms has been fixed/created.

Geez added a subscriber: Geez.Jun 2 2023, 9:28 AM

Nitrado on 5/31/23 added the disableMultiAccountMitigation option as a checkbox in the general settings. Its right after enable cfggameplay. However, its not working. I talked with Nitrado and they really have no idea what Im talking about. they think that this option has existed for quite some time and it just stopped working. They kept trying to tell me that they cant change that setting and its in the code and I have to do it. I sent a screenshot and they finally started trying to look into it. The ticket has been open for 24 hours but nothing has changed as far as I know.

My suggestion would be to have bohemia completely disable or remove this timer until the ability to disable it across all platforms has been fixed/created.

Hello, we are aware that the disable parameter does not work right now and we are working on fixing it as soon as possible!

Geez changed the task status from New to Acknowledged.Jun 2 2023, 9:28 AM
This comment was removed by Geez.

This incident is still ongoing

This comment was removed by Geez.
This comment was removed by Geez.
This comment was removed by BIS_fnc_KK.
This comment was removed by Geez.