Each object has a properties table you can access, so you can give an object properties such as flags to let your program know what can be built there. Right, I understand I need to do that. But I don't understand your documentation because of lack of examples. function tower.PlaceAtMouse(x, y) for...

I'm having a tough time understanding how to implement STI into my game. I'm making a tower defense game and what I have setup are rectangle objects in areas that towers CAN be placed on, and I have a polygon shape object created to specify the path that I wanted enemies to take. I have no idea how ...

Hey, you are on the right track. The change you need is this: When you spawn one of the small particles, you need to give it a random x- and y-velocity once. Then while it is flying do not use any randomness, but only physics. Here are the lines you need to change: function particles.Spawn(x, y, am...

I'm trying to create a sort of sim where you can launch fireworks and they explode and whatnot. I'm avoiding the particle system and physics modules entirely. I can't for the life of me figure out how to make my particles actually, like, fly out however. I really want to just avoid the modules Love ...

Oh you mean going into fullscreen, and then go back to windowed mode?

All buttons work for me the same way they do in windowed mode.

Windows 7 1920x1080

rmcode wrote:What OS are you using?

Windows 7

Another thing I noticed which isn't a huge deal, but if there's a message box open, and you click the game window behind it, the message box gets hidden behind the game window. Is there a way you can force the message box to always stay on top? And what does attach to window do? It attaches the mes...

Buttons in Message boxes are in reverse order. Is it normal? I believe they're in the "natural" order for message box buttons on the OS (whatever that may be), rather than always left-to-right. Maybe think of it like: the first one in the list is the primary button. And escapebutton in Me...

You can probably solve this by doing these two things: 1) In the ball-update do the movement first and then the collision detection. 2) In the collision detection, separate the collision at the top and at the bottom. Something like this: if self.y >= gheight - self.height then self.yVel = -1 * math...