Nice one. I had a very cursory playthrough; lasted 2 days because I didn't realise I was dying >.<

• Gotta start with food. Having none in the beginning means everyone's first playthrough (i.e.: when they're still figuring out the game mechanics) is more challenging than it should be.
• It wasn't immediately obvious what I should do. I suppose that's not a bad thing with this sort of game, but perhaps a quick overview of the controls at least would be handy. For example, it didn't feel immediately obvious that I was on some sort of "overview" map of the world. Maybe that's a scale thing.
• The card turning animations need to be at least a million times faster. They look nice but they're painfully slow.
• It wasn't obvious that I was dying while playing the memory match game. It seems odd to me that this could happen, but it is a nice approximation of the idea of spending more time scavenging for stuff. With that said, a memory game on its own can either be completed, or not - I don't like the implication that I should only have a few tries at it before setting off if I'm not getting anywhere fast. There's a lot of guesswork in these games - especially at first - and you're basically damning the player for playing a memory game the way it's meant to be played - thoroughly.
• This could be alleviated by providing some sort of "cheat" system for the memory game that could be attributed to improving the character's survival skills.

No, it'll do it in real-time, so it will hurt performance as you scale up. A good way to reduce the performance hit is to apply the effect to the entire layer, and then create layers just for the sprites you want to affect.

If you want a truly unique experience, I suppose everything would need to be procedural.

Enemies, power-ups, platforms, obstacles - not just their placement but their look, shape, stats, etc. If you were to go that far, take it further with procedurally generated music and sound effects - textures even.

You'd certainly have your work cut out for you, and I'm sure you'll need a few custom plugins to make a lot of things work. For the enemies I'm sure you could wangle something with Spriter.

That plugin can also display Unix time, which is a very convenient single number that measures time in milliseconds, factoring in all month lengths and everything else (except for leap seconds).

So, whenever a player plants something, assign the current Unix time to a local variable (Plant.TimePlanted or something). Then, provided each plant is assigned another variable (Plant.HarvestLength or something) to determine how long it needs to stay in the ground, all you need to do is a simple check to see if Date.Unixtimestamp - Plant.TimePlanted > Plant.HarvestLength. If so, then it's ready for harvesting.

Here's a little demo to show you the idea in action.

You can use the system condition Compare two values. Use the value Enemies.Count to count the number of enemies present in the layout and choose the appropriate actions based on the result.

It's funny how often this comes up. I really think the manual entry should be amended to include these details.

If you use NW, local storage goes to the "OS:\Users\Username\AppData\Local[i]AppName\Local Storage" folder.

I've only tested this with one game that uses local storage for a high score table, but I tested on five very different Windows-based machines and they all worked perfectly. Not once did I get a permissions popup or anything funny like that.

Is is 100% safe to assume that it'll always work on every PC in the world? I wouldn't be able to make that claim, but I've yet to see a complaint on the forums about NW-based local storage simply not working due to anything other than mistakes by game creators themselves.

Alternatively, there was a thread that came up recently about creating a custom file saving system, which you might want to look at if the stock options worry you.

I've had the same issue for ages. Always figured it was just a driver issue or something and I didn't worry about it too much since it works fine at runtime.

Still, it's a nuisance, so if it could be fixed that'd be stellar.

Apologies if I'm reporting duplicate issues/suggestions here.

• Quick reply box is missing.
• Everyone's avatar is the same (that pink robot).
• No purchased/1st ribbons on avatars.
• Light-blue header for each post is incredibly distracting.
• Sidebar (the bit with the avatar in) seems far too wide, like it's wasting space.
• "Unread" posts are especially distracting. That thick blue line around the post is too much.
• Surely text size can be set in the profile? I can't think of a reason to have the button always visible. Also, it's orange, which is quite distracting.

Otherwise, I'm excited to see a major update to the forums! There have been technical issues here for ages, hopefully this'll see them all sorted out.

delgado, sorry, I have no idea why it's not working for you. It's a very simple example and at the very least the actual click-and-drag action should work, even if the throwing doesn't for whatever reason.

neutrinox, yeah, mixing in the scroll-to behaviour is sure to cause a lot of trouble. I'd suggest rather creating an invisible follow object with the custom movement behaviour that chases the ball, and scroll to that, rather. Or only activate the scroll-to on release of the ball.

delgado, you'll have to provide a little more information. I just tested my example again and it works fine. Not sure what issue you're having exactly.

Thanks for this! It works perfectly, no fuss. Only "issue" is that it only works in a compiled app, not in the CJS Launcher.

Thanks Paradox, that's a really handy workaround!