So basically i want to be able to have individual sprites, on my project, and on runtime i want to use spritebatches for efficient drawing. I know games like space station 13 and factorio that "glue" together the individual quads on initialize.

This enables for using only the quads thay are actually in use, disabling those that wont be used yet, making smaller tilesets and therefore less struggle for the GPU.

Tileset generation: Create an ImageData object of the final size of your tile sheet. Iterate over required tiles, use ImageData:paste() to copy tile data to your sheet. The completed sheet can then be used to create a texture/image with love.graphics.newImage().

This is easiest done when all tiles have the same size. For tiles with varying sizes you may have to think about how to arrange the tiles in the sheet in order to not waste too much space. BSP is a good algorithm to pack tiles efficiently.

Remember to leave border around the tiles if you plan to have zoom in/out functionality.

If you really want to make sure everything is literally seamless if you do want to scale or rotate, then you need to fill those borders with the colors of the inner rows/colums, not just leave them transparent for example, otherwise seams might appear. (In other words, extrude each of the 4 sides by 1 pixel; implementation left to the reader )

Me and my stuff True Neutral Aspirant. Why, yes, i do indeed enjoy sarcastically correcting others when they make the most blatant of spelling mistakes. No bullying or trolling the innocent tho.

Here's a solution for the border problem zorg mentioned, copy-pasted from some old project. This function creates a tileset from an image and adds borders as required. Sorry, it's in moonscript, but should be easy to translate to Lua.

By the way why is the seams happening ? Doesnt the quads get the whole image from the tileset afterwards ? The images are glued together without borders i believe, didn't add +1 to any of the coordinates on :paste()

The calculations are performed by the GPU in floating point. These are subject to rounding errors. The effect tends to appear at coordinates that are near something plus 0.5, because sometimes it's rounded up and sometimes down.