Got halfway through round 5 just by running to the right. I think the enemies need better reaction time, or slow down the player movement speed. I like the concept though, good work.

I share that pain too. For the last 6 months or so I've been working on an engine for a cinematic platformer (which started out as a learning project for construct 2) and recently I discovered that the thing I've been building upon, iterating and molding just doesn't work when it comes to making something worthwhile; it was just too damn buggy and unreliable haha.

So I'm currently rewriting the engine, with all new knowledge and understanding of the engine that I've gathered over the past 6 months of development. And so far it's almost bug free - because I built the engine on the same basic idea as the old one, so fixing any shortcomings was a piece of cake for this one, I'm also writing the new engine so that it's easier to implement new features because it's structured in a much more intuitive way: grouping, functions, compress the amount of variables as much as possible etc.

And also, agreed with TiAm, those three points: can't stress it enough, I have post-it's everywhere with reminders to "keep things simple" and the like, it's surprisingly easy to fall into old, bad habits. And also: comment early, comment good. Make sure that your code is readable after returning from vacation or long breaks. It's much more fun to work on a project when you don't go "*sigh*.. Aalright, let's take a look" whenever you want to implement some new feature and such.

Those are the things that I'd say works for me. Often, the hard part for me is not that the passion for the project has died off but that all of the seemingly miniscule problems (like unorganized pieces of code, uncommented code etc) pile up into an unmanagable behemoth that's just too much to care about. So yeah: "organization, organization, simple, simple".

Very good feeling you've got. Keep it up!

I'm currently rewriting my engine after stumblinng upon a few problems but anyways.

My biggest flaw was that the engine didn't check for trigger points before performing actions, so for example when you stepped forward, the game would not check if there's even a surface next to you, but instead would check what kind of surface is below you after you've moved. This proved to be a very stupid way to do things when I wanted to implement pits and ledges. As the project went on I had to do some crazy workarounds that would produce countless bugs. Oh well. Lesson learned.

Good thing I now have a grasp on how the engine is supposed to handle stuff so rewriting it has been very smooth thus far. I might actually put up a .capx for it later for people to see how I personally did it. Maybe.. We'll see.

I don't think this is a bug per-se but more like an oversight so I'll post it here, if I'm wrong a mod can move the thread to the right place!

So!

When you reload sprite frames from a source it doesn't update any duplicates of that frame in the animation and you can't update them individually since the option to reload is greyed out for any duplicates for some reason. This makes you delete any duplicate frames and re-import and rearrange them. It's not a game breaking issue but it is noticable when doing lots of tweaking with animation frames and such.

Is it possible that in future updates you can either reload every duplicate individually or that when you reload a frame, every other duplicates gets updated as well?

Thanks!

You could add the objects to a family and do this:

is [family] on layer? then [family] set collision enabled/disabled

It's an issue that has to do with pixel rounding, the .capx that was provided in the thread you linked had pixel rounding on, which disallow objects to be drawn between pixels hence why it stutters. Toggle pixel rounding off and the problem is fixed.

I used the .capx in your mention and did some quick monitoring with pinning vs positioning every tick. Pinning the object resulted in a cpu usage of 1-3% while positioning every tick gave me a stable 4%, sometimes 5%.

Wouldn't it be less intensive to just pin them?

allen Since almost all cinematic platformers are grid-based. You lock animations within the timeframe of one step, or of any other motion you want the player to perform. That said it's pretty easy to build you animation system around that idea, whether is climbing, running, crouching, throwing etc. Another important thing is that all animations end on an Idle frame, else it gets a bit jerky.

16Bit Tileset - Grasslands — Now for sale in the Scirra Store!

https://www.scirra.com/store/royalty-free-game-tilemaps/16bit-tileset-grasslands-681

<p>A high quality tileset that allows for seamless, complex terrain structures.</p><p>Content:</p>

• A variety of terrain pieces
• Grasstops for extra detail on the surface
• Water
• Cave texture
• 26 plants and rocks
• 3 tree types (that allows mix and match)
• 2 sky colors
• 3 clouds for both sky colors
• Shadow tiles for darker areas

<p>Specifications:</p><p>Tile size: 16x16</p>

Use this topic to leave comments, ask questions and talk about 16Bit Tileset - Grasslands

http://c2rexplugins.weebly.com/rex_moveto.html

http://c2rexplugins.weebly.com/rex_platform_moveto.html

This is a plugin I use quite often and it works very well. The description is pretty self-explanatory.

EDIT: Added the platformer specific one as well.

Logic and creativity are not mutualy exclusive. I believe the question is framed wrong. It shouldn't be "abstact vs concrete" but how can those two qualities complement each other? I think the most common misconception that people have is that creativity means artistic, that's not completely true. Creativity is the ability to rethink and/or invent solutions to complex problems, and those problems can be whatever have you: math, music, physics, art, literature etc.

Asking whether a high IQ will help you develop games doesn't really say much because it's an arbitrary number without context outside from the test. Making games require a huge amount of different media that are all interconnected.