Yes, that's it. Sorry for being so long-winded; I just wanted to try and spell out everything I thought of/did previously to solve the problem. I'm trying to solve my problems myself and I actually value plain-English correction (or suggested further reading) more than code solutions. I just wanna m...

Hey guys, I decided to spend today working on what I thought would be a simple problem. (Apparently I was wrong.) I wanted to see if I knew how to basically account for unplugging/replugging game controllers, succesfully identifying the exact same physical device, and logically assigning information...

Now that you mention it, taking a screenshot sounds like it would be at least part of the solution. It just occurred to me that I'd almost certainly want to (effectively) freeze the drawing state as the transition begins (so that moving objects stop moving on screen, etc), so I'd probably want to re...

Hey guys, I have a little prototype right now where I have a main menu and two crude little gamestates (via HUMP.gamestate) which I can transition between (menu -> "game"). You can see what I have so far in the .love file attached to this post. Before I go much further on defining the othe...

EDIT: Figured it out. Googled "love2d quit game from menu", blundered into the doc page for love.event.quit(), tested it, does exactly what I wanted. Sorry for taking up your time, Positive07, and thank you very much for your help. To answer more specifically about what I want, all I want...

Quick question: I want one of my menu state callbacks to call love.quit(). Since I called registerEvents() with no arguments in love.load(), I know that I've remapped the default LOVE callback, and now I'll have to define a new way of getting that behavior. My first naiive thoughts were these: (1) D...