{"realms": []}[/code:15yo6a9a] is a valid json string, but [code:15yo6a9a]test({"realms": []})[/code:15yo6a9a]is obviously not.

LoadJSON "{""name"": ""test"", ""age"",""xxx""}" at root@'some','kind','of','path'[/code:iu5f956j]
which would exactly achieve what you described without having some nasty parsing. Something like[code:iu5f956j]Set Value "{o_o}" at root@ 'smilies','0'[/code:iu5f956j] should be expected to work

has for sharing things on github, yeah, I should, three years ago I wasn't really using it that much so I didn't have this reflex.

JSON.Value(0, "units", 1, "unitID")
JSON.Value(0, "units", 2, "qty")[/code:1w7j9ogo]

the arguments are to be read as:
1st: 0 = root, 1 = current  (current is used un foreach loops and I think you also have an action to set it)
2nd: "units" is one of the key of your root object's member (if the root were an array , you would use the index)
3rd: the index of the "units" array
4th: "unitId" or "qty" one of the key of one of the object in the "units" array

JSON.Value(0,0,"score")[/code:9b1y66wd]The first 0 means "from root", the seconds means, "first element", and then "key score"

in javascript it would correspond to [code:9b1y66wd]root[0]["score"][/code:9b1y66wd]

Load JSON " {
  ""someText"":""Hello World"",
  ""location"": {
      ""latitude"":"&mylatitude&"
      ""longitude"":"&mylongitude&"
   }
}" at rootyet@[/code:3twjem51]
And trust me, I recently made a manhattan distance algorithm for strategy game prototype using this JSON plugin, and having the plugin spitting out warnings was a big help. I had forgotten some checks and looping through empty data.
Without those warning the data would have been wrongly, automatically filled and I would have had very hard to fix bugs.
You have to like "[url=http://stackoverflow.com/questions/2807241/what-does-the-expression-fail-early-mean-and-when-would-you-want-to-do-so#answer-2807375]failing early[/url]" (:

@grossd
that's an idea, I'll think about it thanks =)

set "Hello World" at root@"0"[/code:2205ryy3]it should automagically do[code:2205ryy3]var root = {};
root["0"] = "Hello World";[/code:2205ryy3]

Whereas[code:2205ryy3]set "Hello World" at root@0[/code:2205ryy3]it should automagically do[code:2205ryy3]var root = [];
root[0] = "Hello World";[/code:2205ryy3]

And I think that's messy and error prone.

So basically your code should look like:
[code:2205ryy3]Clear root@
Set New Object at root@   // so the clear isn't necessary
Set "Hello World" at root@"someText"
Set New Object at root@"location"
Set 10 at root@"location","latitude"
Set 20 at root@"location","longitude"[/code:2205ryy3]

it's equivalent to the javascript:
[code:2205ryy3]root = {};
root["someText"] = "Hello World";
root["location"] = {};
root["location"]["latitude"] = 10;
root["location"]["longitude"] = 20;[/code:2205ryy3]

so yeah bottom line, the json plugin shouldn't automagically create objects for you.
if I'm not wrong, if you try inserting a property/value and the object doesn't exist, you should get the following warning in the console:[code:2205ryy3]invalid path: root@someText[/code:2205ryy3]or[code:2205ryy3]invalid path: root@location[/code:2205ryy3]

This "invalid path" warning allowed me to debug some wrong code many times and I think silencing it would be a mistake. Yes you have to write more actions, but at least you stay in control of your datastructure.
And events using the JSON plugins can get quite messy, 'cause construct2 doesn't have a lot of possibilities UI-wise. (I wish you could use the bracket notation)

Hope I make sense.

In any case you can rip apart my plugin to your heart's content :D  after all it's still in "beta" and if you find good ideas I'd be glad to add them.

But keep in mind I have a more advanced version on my computer since more than a year, but I haven't released it because it's incomplete. I wanted to be able to have references to other object to avoid having to copy things and be able to create fun things like cyclic datastructures.
But it's breaking the JSON serialization so you wouldn't be able to save/load the object's state properly.
I found something from the dojo framework that might be a solution (they have a JSON.stringify that support references) but I didn't have time to rip it apart to just get the usefull bits (I wouldn't want to include the whole dojo library for just a plugin)
(that's the current state of things concerning this plugin :D)