I made the levels a bit smaller and put in fewer monsters to try to avoid the collision limit. I've since then added bullets for the player (fire with WASD). However, sometimes when I hit a monster there's another crash. Process: love [2472] Path: /Applications/love.app/Contents/MacOS/love Identifie...

I haven't added bullets yet and I'm already running up against the collision limit.

bartbes wrote:too many collisions going

Hm, that would make sense, since the crash happens when there are a lot of monsters swarming the player.

Though I set a mask on the player's and monsters' collision shapes to make them pass through each other.

I'm adding pathfinding to my game to make monsters properly chase the player. I have them swarming the player somewhat satisfactorily, except that now I'm getting random crashes that seem to come from Box2D. Process: love [1317] Path: /Applications/love.app/Contents/MacOS/love Identifier: org.love2d...

As far as I'm aware, you can either set a shape to be a sensor, where it will pass through everything but collisions will be detected, or you can set a shape's category and mask to make it pass through certain other shapes without collisions being reported. Is it possible to set a shape so that it w...

C++, which is also pretty similar to lua :huh: I've heard of Horde3D . It is like Ogre3D but smaller and has a pure C interface, so it'd be easy to write a Lua wrapper. There doesn't seem to be that many projects that use it though, so Horde3D is not "proven" like Ogre3D is. On the other ...

To-Do:

• Start screen
• Win condition/level transition
• Monsters
• Bullets
• Power-ups
• Sound and music
• More creative name?

AFAIK this is completelly normal, those triggers always return the shapes in a "random, but orderly" manner. What I mean is that when two shapes collide, you get the hook called for shapes a and b without knowing which is which, however, every time this two shapes collide, the hook is cal...

I've tried adding bodies and shapes meant to be deleted to a list that I can clear later, instead of destroying the bodies and shapes immediately. This gets rid of the crash, but I have discovered that the callbacks for player/key collision and player/door collision seem to be getting called twice. ...

I'm using the physics engine to handle collision detection and response. I have a bunch of coloured keys that players need to collect to open doors. These keys have a physics body and shape set to be a sensor. When players touch a key, the key's physics body is removed from the world. Except that ri...