That is not a tile format. You are NOT doing tiles. Tiles use a grid, you are defining positions on the other hand. Free positioning needs a physics lib. This is a tile map: Map={ {1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,}, {0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0...

Your code, show it.

Your first post here was years ago.
How come you still see yourself as a beginner?

If you simply use tiles that is super easy: if tiles[math.floor(x/tilesize)][math.floor(y/tilesize)] then print("collision") Problematic is you either need to init all possible x positions in _tiles_ or put a meta table in it so you wont get a nil access error at the map edges. Also the me...

So i'm an inspiring game dev

i am basically code and pc illiterate

My boy this is concerning.

I think the best way for you is: Go into the folder, mark everything, zip it.
Then you do a right click on the zip and select open with > löve.

If that is just for a test you can simply throw the text into any terminal playback. Basically if we are on löve we replace the playback function with something like function playback(text) io.popen("espeak ".. text) end keypresses of course only work when there is a window. If that bugs y...

I am bread, i need salt. German humor, there where wars over it. In anycase this is called key rollover and you keyboard has a 2 key limit meaning they only guarantee up to 2 keys working. Some 3 ones may work, but not all. Usually modern keyboards have a 3 key guarantee. Good ones have no limit. Th...

Your keyboard has a limit on how much keys it can use at once.
This is a hardware thing, just buy a better computer.

Thing aint even a 10 liner, how do you want to simplify it?

Doing all at once defeats the purpose of doing an asynchronious thread load.