maybe I haven't read the chapters carefully but I am very interesed how you lowered your memory when making the game Prove Thine Worth. usually my love2d games are in the high 20's-30's mb of memory usage and I really want to lower that number. any tips or an article on this topic would be really nice. awesome tutorials anyway! keep up the good work!
How to LÖVE
A downloadable book
Welcome to How to LÖVE. The tutorial that teaches you how to program games with LÖVE (aka Love2D). Written by me, Sheepolution. It's the tutorial that I wish was available when I started learning how to program.
In this tutorial we will be using LÖVE. The reason for this is because LÖVE is very beginner friendly in terms of programming games, but provides the functionality to make professional games 2D games. This makes it a great tool for both beginners and experienced users. Here's a list of all the games on Steam that were made with LÖVE.
Unlike Game Maker and Unity, LÖVE is a framework and not an engine. You will have to do everything with code. There is no built in level editor or anything. The plus side to this is that you will understand exactly what is going on and how it works, because you wrote it yourself. Your knowledge is also easier to transfer to other engines and frameworks. Because while every engine works differently, code always works the same.
This tutorial is written for people without any programming experience. If you do have experience with programming, I recommend you at least read the summary of every chapter, and when it confuses you, you read the full chapter.
If you *don't* have any experience in programming, I hope this tutorial will teach you what you want to know. You probably want to start making a game right away, but I'll have to ask of you to be patient. There are a lot of concepts surrounding programming that you will need to understand before you can start making a game. And it can take a while before you're fully grasping these concepts. There is a good chance that you will be reading this book and not fully understanding what you're reading. In that case my advice is to ask questions (see below) and perhaps to continue with the book, pretending that you know what is going on. Maybe at chapter 12 you're finally understanding what was explained in chapter 8. In any case, don't feel bad or dumb if you don't understand everything right away. Take your time.
When you feel like it, I encourage you to "skip ahead". With that I mean try out things that the book hasn't taught you yet. Play around with what you know already and look up things you want to know. This makes for some great practice and in the end that is what you need. You can read about painting all you want, but to learn you'll have to paint yourself. Same goes for pogramming.
Some chapters will use code from the previous chapter. In that case I will point it out at the top of the chapter.
I'm not done writing this tutorial, meaning there are still new chapters to be released, but I have no concrete plans for when that will happen. By adding this book to your library you will get an update when I add a new chapter.
Log in with itch.io to leave a comment.