[Bug] /voicechannels.json can't be parsed when a voice channel uses mode Non-spatial

[Tynopia]

Summary

If I create a voice channel with mode Non-spatial, the JSON from /voicechannels.json can't be read. My JSON viewer stops at the maxDistance field and shows nothing after it, so I never get to the clients array.

If I create the same channel with mode Spatial, the response is fine. The only thing I change is the mode I pass to CreateVoiceChannel.

Issue type

Server

Repro rate

Always

Server build version

FXServer-early-access b129 win32

OS

No response

CPU

No response

GPU

No response

RAM

No response

Storage type

None

Connection type

None

ISP and bandwidth

No response

DxDiag

No response

Network graph

No response

Platform

None

OS version / distribution

No response

CPU

No response

RAM

No response

Using txAdmin?

None

Hosting provider

None

Machine type

None

/perf endpoint output

No response

DDoS protection

No response

ulimit -n value (Linux only)

No response

Docker Compose file (Docker only)

No response

Steps to Reproduce

1. Configure the server so that the /voicechannels.json endpoint is enabled and reachable.

2. Add a small resource:

   voice_repro/fxmanifest.lua

   fx_version 'cerulean'
   game 'gta5'
   server_script 'server.lua'
   

   voice_repro/server.lua

   RegisterCommand('vcreate', function()
       print('channel: ' .. tostring(CreateVoiceChannel(0, 0.0)))   -- Non-spatial
   end, false)
   

3. Start the resource and run vcreate in the server console.

4. GET /voicechannels.json
   The response can't be read past maxDistance.

5. Change the call to CreateVoiceChannel(1, 20.0), which is Spatial. Restart the resource, run vcreate again and request the endpoint again. Now it parses

Expected Behavior

The response should be readable no matter which mode the channel uses, so something like:

[ { "id": 0, "mode": 0, "maxDistance": 0.0, "clients": [] } ]

A Non-spatial channel has no distance limit, so I'd expect 0 or null there.

Actual Behavior

With a Non-spatial channel my viewer stops here and shows nothing after it:

[
    {
        "id": 0,
        "mode": 0,
        "maxDistance":

Whatever comes after "maxDistance": isn't accepted, and since it breaks inside the array I
lose the whole response, not just that one channel.

The same request with a Spatial channel works:

[ { "id": 0, "mode": 1, "maxDistance": 100.0, "clients": [] } ]

Evidence

No response

Additional Context

No response

[wolfram-cfx]

Thanks, we are looking into this.

[Gogsi]

A fix for this issue has been implemented and is available in August 31 patch. Please try again and let us know if the issue persists. Thanks for your help!