litjson | JSON library for the .Net framework | JSON Processing library

While I cannot provide a definitive answer at the moment due to not having time to fully review the LitJSON code, I did look over it briefly and am guessing that this odd behavior is the result of using static class variables (mostly collections) to cache values during processing. I can't think of anything else that would different from the first execution to subsequent runs outside of:

1. Assembly isn't already loaded into memory on the first run
2. Static class variables are initialized but likely don't contain any values during execution (unless initialization loads data that is simply read on all executions)

Doing such things does usually improve performance, but there is a nuance when doing such things in SQLCLR: AppDomains in SQL Server are shared across sessions. This means that shared resources are not thread safe. This is why typically (i.e. outside of marking the assembly as UNSAFE) you are not allowed to use writable static class variables (you will get an error saying that they need to be marked readonly). However, in this particular case, there are two breakdowns of this rule that I see:

1. changes made in 2015 (and merged 2 full years later) seem to indicate that the desire was to get LitJSON to work in an assembly marked as SAFE, hence all static class variables were marked as readonly, and additional changes were made to accommodate this. you can see those changes here: https://github.com/LitJSON/litjson/commit/1a120dff7e9b677633bc568322fa065c9dfe4bb8 Unfortunately, even with those changes, even if it did "work" in a SAFE assembly, the variables are still static and are hence still shared. For some technical reason it is permitted to add/remove items from a readonly collection, so on a practical level, they aren't truly read-only. This can definitely lead to unexpected "odd" behavior.
2. If the intention of the changes mentioned above were to allow the assembly to work while being marked as SAFE, then clearly something has changed since that SQLCLR-based commit 4.5 years ago given that not marking it as UNSAFE now results in the following error (according to the OP):

   The protected resources (only available with full trust) were: All The demanded resources were: Synchronization, ExternalThreading So, currently the code requires being marked as UNSAFE, in which case, none of the changes made to mark the static class variables as readonly were necessary ;-).

Regardless, I don't think this code is thread safe. In fact, you might be able to see "odd" behavior by doing multiple executions, each one with a different JSON document that varies in structure (at least number of elements).

Again, this is not definitive, but is more likely than not. In which case, I'm guessing that the great performance of the first execution is due to the code doing things that would not actually work in production. Of course, you do have a hard-coded structure (the output row schema is compiled into the code) so I suppose that eliminates the case of passing in different structures, but it's still not clear what the effect would be if two sessions execute this with different JSON documents at the exact same millisecond.

Unity Engine has a specific Order of Execution.

This defines the order at which Unity Callbacks are executed in every script.

For instance, all the Awake() callbacks in your MonoBehaviours will be executed before any Start() callback.

That said, it doesn't mean that it governs the order of execution of individual Start() callbacks from different behaviours.

In your example. It is possible that the Start() callback of the ItemOnGround behaviour is invoked before ItemDatabase's. In which case, you're making calls to an ItemDatabase that hasn't been initialized yet. So here is what I suggest:

Approach 1:

Knowing that Awake() is called before Start() you could initialize your ItemDatabase by changing Start() to:

Your code is actually broken in term of design.

First PlayerPref doesnt support boolean save by default.

It's much the same. No need to deserialise to read the data, just use a JObject:

I recommend using Unity's built-in solution to JSON, JsonUtility.FromJson() and it will autofill the following class scheme(from http://json2csharp.com/#), which should be easier to handle and not require an external library. Of course, this is an alternative, perhaps you may prefer to keep using LitJson, this should read "desc": "en". to implement this you would use...

Was able to solve the problem of calling the method from another script, the problem was that I had to create an object and attach to it API.cs. Then I also had to drag and drop that object in the public field of caller.cs in the inspector.

That doesn't sound right dragging and dropping the script manually in the Editor since your goal is to do with from script. The API script is a MonoBehaviour because it derives from it. Use AddComponent to add the API class then call StartCoroutine on the Login function.

You have an error in your json. The error itself is a little misleading. Every time I've seen it, there was a json syntax issue involved.

You are saving the slider value to the same key resulting in that key is overwritten each time, in your case the value of the first slider in the hierarchy.

The way to solve it is to give each slider an unique PlayerPrefs key.

One quick way to solve it is to change

I'll share to you what is really the error here . There's nothing wrong on my

The line of code below is working perfectly . So let me just explain a bit of it by putting comment lines

LocalizationManager.cs