Unexpected Behavior When Sharing a Simulation Result

[xknRiya]

Issue

When attempting to share a simulation result, if either x or y target position is -0, the Share API returns a 400 Bad Request. Additionaly, the position field inside target_details in the request's payload is unexpectedly set to 0, which may be the cause of the error.

Example Case

amber char lvl=80/90 cons=0 talent=6,6,6;
amber add weapon="dullblade" refine=1 lvl=1/20;

target lvl=100 resist=0.1 pos=-0,0 hp=1 particle_threshold=250000 particle_drop_count=1;

active amber;

Payload

[soloxcx]

it's just "-0" not parsing correctly, not sure there is a reason to devote time into fixing it. just type 0

[xknRiya]

How is the user supposed to know they need to change -0 to 0 if the app doesn’t even show them an error? There is no error message on screen, no feedback to the user. Instead, the only visible effect is an infinite loading state, which could easily be mistaken for other unrelated issues. The 400 Bad Request is only visible through the browser's developer tools. Even then, the only way to pinpoint the cause is to inspect the entire payload, compare it to the input, and notice that, for no apparent reason, -0 is treated differently from 0.

[soloxcx]

I misread the issue so it's a valid point.

[srliao]

it's an issue with the custom parser recognizing -0 but json not. unlikely to get fixed though