Forums » Impact Engine » Is seperateOnXAxis being updated in next release?

I was trying to create some blocks that I could have the player move around on the level. The idea was to make different blocks not moveable in particular directions.

For example:
Block A could move left, right, down, but not up.
Block B could move right, down, up, but not left. etc.

All of this making for a puzzle device.

In looking for a means to solve this I ran into:
// FIXME: This is a mess. Instead of doing all the movements here, the entities
// should get notified of the collision (with all details) and resolve it
// themselfs.

If this is in fact being updated in a soon to arrive upgrade, I will just wait patiently.

However, if this is not coming any time soon, then, I'll need to try to find a solution another way.

No pressure. Just don't want to solve something the hard way, that the core impact code will make easier later.


ig.Entity.seperateOnXAxis

If you're building a puzzle game like Sokoban or anything similar where you need exact movement of blocks, you'd probably be better of writing your own collision routines.

Impact's entity collisions are quite fuzzy, in the same way as Box2D. As an extreme example, you wouldn't want to build something like Tetris with real collision detection.

The FIXME message in the source is a reminder to fix the structure of the code, not so much how the code works. This is a thing for 2.0 though, as it would change the API quite a bit.

Thanks for the heads up.

I just liked the notion that those functions would be able to be subclassed.

However, when you talk about change the API suddenly it gets a little spooky. Will have to avoid falling too much in love with the current API.

I guess it's "mutate or go extinct."

By the way, I really like the "fuzzy" aspect of the game. Every now and then I'll change a parameter and get an amazing effect that I could not have anticipated. Fuzzy is good imo.