Lol @ you @Sim
Not only the wrong word for the intended meaning, but a word from Old and Middle English; suggesting it's simply not in use anymore.
That's the trouble with using older language - contexts are different.
How about stop being a young me and drop the attitude; it ain't gonna help you in this world
Sadly, no such feature exists in stock gRPG v2 (I'll be sure to add it! Though I can't currently provide an ETA)
There are many developers available for hire here who, I'm sure, would be willing to throw some code your way
Hi, welcome to MakeWebGames!
Without any further information concerning your issue, we can only take guesses as to its cause.
Is there an error log available?
To add on to SRB's statement; in some setups, it may be necessary to parse the JSON string into an object before JS will let you use it as such.
let scavengeData = JSON.parse(data);
alert(scavengeData[0].amount);
If I'm reading that right, you should be able to access the `amount` key (presumably repurposed to a context of "days" if applicable) like a standard array.
data[0].amount
Edit; which I see you've tried.
In what format is `data`? Is it a JSON string, or something else?
Your setTimeout call.
If memory serves correctly, you don't need to add the parenthesis for the callable function
setTimeout('showScavageResults', 1000);
I remember experiencing this issue before in multiple other engines and almost every case came down to sessions.
There was one or two cases where a token was being set before it was processed (invalidating the expected key before we could touch it) - check for duplicate calls to MCCv2's CSRF token generation function
Put id="php__container" back into the div from which you removed it.
Change the <a> tag id attributes - they don't need an octothorpe and they must be unique