Oh I spoke too quickly, it seems if you make more than one request at the same time, the "itemvalue" will be overridden in all the wrong sequence depending on the latest retrieval UNLESS you use item get.
I ended up still having to use on item get.
It's ok, I think I understand why this will be an issue.
But kinda still a bug though, lol.
So people, the correct sequence to using Local Storage is:
Check if Key Exist.
If Key doesn't exist triggers, do your shit.
If Key DOES exist, call "get item" for that key.
Trigger happens from get item, retrieve it via itemvalue.
Yes Webstorage does it all in one line but it seems those days are decidedly over now
I've finally bite the bullet and change it, for all of you still deciding, remember, the more you add to your game, the more it is going to be difficult to comb through and remove your webstorage, yes I know you probably group it properly but CAN YOU BE SURE ?
Better fix it while your game is still small, or even if it is big, do you want to fix it when it is Bigger ?