One of the things I love about Lua(JIT) is that I do not have to have the separation of core engine (e.g. C or C++), scripting (e.g. Lua or Python), and serialized data (e.g. XML, JSON, something custom) anymore. I used to develop in that traditional way, and it was so ugly. Translating between the ...

Nice, I like the smooth movement too.

You sound like someone who wants a game maker [1], not LÖVE. In LÖVE you will have to program almost everything yourself and/or integrate other people's libraries. I do not think LÖVE is a good choice if you just want to make relatively simple games. LÖVE makes more sense for people for whom program...

If there is no way around the window size limit is there a way to draw to an arbitrary sized offscreen surface and somehow save said surface to a file? I ask because that's what I would do with plain SDL. [wiki]Canvas[/wiki]es. And [wiki]Canvas:getImageData[/wiki]. Thanks! Got it working in no time...

Does LÖVE (0.9.0) limit the window size to the maximal full screen resolution? Because it seems that way. I am unable to create a window with a width larger than 1920.. which happens to be the maximal full screen resolution of my system. Please tell me there is a way around this. I used LÖVE as a qu...

If I have, for example, a fast creature that can move 5 times a turn, but only attack once, what do I do when the player moves three times and then tries to attack? Good point, I did not consider how to handle such cases using a typical roguelike interface. In a RPG you simply press "end turn&...

I would. You should separate movement and attack/special ability speed. If you do not, speed becomes a super-powerful uberstat. The fast creature which can move 4 spaces while another can only move one can also attack 4 times while the other can only attack once - that is insanely imbalanced unless ...

pauljessup wrote:It's a map editor/map engine I developed in Love2d and Lua.

I see. Thanks.

pauljessup wrote: And the Greentea happy fun time library.

Link please. I have never heard of it.

nvidia's OpenGL driver in windows seems to wait for the screen's vblank by basically doing a busy-loop until it happens, which will always use 100% CPU on that thread if it can. Other drivers do it differently. One of the links I gave provides a possible workaround for the issue. I already have wor...