No longer relevant due to refactoring of the system that was completed in 0.9.8.50 @Geez

Resolved already in 0.9.7 I think. So Can be closed too @Geez

Resolved as of 0.9.8.50 with the introduction of ScriptComponent::OnAddedToParent etc. @Geez please close.

Confirmed still an issue in 0.9.8.50

Just checking in to say that currently with 0.9.7 this is still an issue. Crash to death.

That is a fair point, I guess it is very niche, but perhaps worth 2 sentences in the data type biki page to explain that "NaN" exists but should not be used because of these issues.
The ticket can be closed. Thank you, Geez.

Hi @Geez, thank you for starting to include the version number of when a change should be expected to have been merged.

Changes were implemented, we are just waiting for it to arrive in public builds. We should have GET, POST, PUT and DELETE then, as well as the special FILE which is just GET -> response body to file.
No headers yet though

@Geez this problem is fixed in 0.9.7

@Geez this issue was resolved as of 0.9.7.

My suggestion would be: One enum EHttpVerb you pass in for the methods and one key value map or array of strings like {"key=value", "anotherkey=anothervalue"}

Not entirely sure right now, but the problem is 100% that the JSON spawns the bonfire, but bonfires are persistent. So on every restart persistence spawns one back and then the JSON as well. You either need to remove bonfires from the persistence types.xml or set the lifetime so they are never saved - but this would also cause your players to not be able to put any custom-placed one into the basis. They would disappear.

could you please provide some more details on what exactly does not work since the 1.19 patch? Player attaching should only be done through LinkToLocalSpaceOf.
I have briefly checked and for me, it still worked - but of course, I can't easily test all use cases/situations.

Geez, this can be closed and or deleted, turns out it was a misuse of the API after internal feedback. Sorry >.>

@Geez fixed as of 0.9.6

@Geez fixed as of 0.9.6

@Geez this issue is now fixed as of 0.9.6 exp patch.

@Geez this is now resolved as of 0.9.6