You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following one occurrence of not getting rewards for random event and I started to investigate the issue. Here's what I've found so far.
Lots of actions (core sampling, transfers) include ResolveRandomEvent call with the following parameters (0x0,0x1, CrewID)
Accepting random events rewards through the UI calls ResolveRandomEvent with parameters (0x1,0x1, CrewID)
How I reproduced the issue
I waited to have one random event available on my crew (0x1809)
Opened Starkscan and I wrote the tx the same way the client does so with ResolveRandomEvent parameters (0x1, 0x1, 0x1809) . I didn't submit the TX, just looked at its simulation. + 30 000 sway were expected.
I rejected the TX
I created a new TX with ResolveRandomEvent with the same parameters found in other actions. So parameters were ( 0x0, 0x1, 0x1809). Simulation returned no sway transfer.
Following one occurrence of not getting rewards for random event and I started to investigate the issue. Here's what I've found so far.
Lots of actions (core sampling, transfers) include ResolveRandomEvent call with the following parameters (0x0,0x1, CrewID)
Accepting random events rewards through the UI calls ResolveRandomEvent with parameters (0x1,0x1, CrewID)
How I reproduced the issue
It seems calling ResolveRandomEvent with the wrong parameters clears the right to get the rewards
The text was updated successfully, but these errors were encountered: