Adding Collisions and Walls (from Tiled) to your Love2D Game 

Easiest thing to add is animated tiles. You can do this by in your love.update function add "GameMap:update(dt)" gamemap should be replaced with what your level variable is named then in tiled find the animation button and add the animation to your tiled and thats it!

player would bypass collision if we did the opposite

make sure your world:draw() is in the right place, above cam:detach()

Since the wall are static and cannot move, the positions of the walls can't move anyway, so it's not needed. For the player, it would rotate from the player movement I would guess.

draw whatever you want to walk behind, last and remove colliders on it. if that doesnt work then do the reverse

@@The_Codemaster144k What if it's also an item that you want to walk in front of later? I'm trying to make trees you can walk around from a over the top perspective

@@unedited12 well you can set a Boolean (true or false) value to set the rendering order. Other than that I really don’t know

Do the following, put (x - width / 2) in player's X position, this also equates to Y position

@@ATS-uy4vl hey could you explain that in more detail? I don't understand

@@stinkyseastar3560 From what I remember at the time, I meant that if you subtract the X/Y position from half the width/height, the Collider will snap to the sprite

You can create diagonal collisions using polygon. If you just mean the images, you need several image assets to create realistic diagonal walls.

@@stevones718 yeah, two of my layers in tiled where the same name, make sure you draw the right layers to the screen

same, I have no idea what to do.

Good question, the physics engine handles all dt-related calculations, so you don't have to worry about it at all!

​@@Challacade Looking at the source code it does seem like dt is passed to the world:update and that in turn passes it to all of it's children.

@@beegdigit9811 that's right. So since the world automatically takes care of all calculations, we don't have to worry about it whenever we're dealing with velocity

What does the error actually say? One thing you could try is deleting the Wall object layer in Tiled, and creating it again. Sometimes some wall objects with 0 width and 0 height get added by mistake

@@Challacade ty very much it worked now:)

thanks so much this also fixed my problem @@beatrz3

it's okay. newer versions of vscode do that

Yep! I do something similar by creating a polygon object: platforms = {} if gameMap.layers["slopes"] then for i, obj in pairs(gameMap.layers["slopes"].objects) do local polygons = {} local polyObj = obj.polyline for vertNum = 1, #polyObj do local vert = polyObj[vertNum] table.insert(polygons, vert.x) table.insert(polygons, vert.y) end local p = self.world:newPolygonCollider(polygons) p:setType('static') p:setCollisionClass("Platform") table.insert(platforms, p) end end

@@therevillsgames Thanks but for some reason I'm getting an error on the line with #polyObj saying that the length is a nil value. Any idea what could be going wrong there?

@@chromeWarriorXIII In my example I have the polygons in the "slopes" object layer in Tiled, and in the export lua map it looks like this: { type = "objectgroup", draworder = "topdown", id = 7, name = "slopes", visible = true, opacity = 1, offsetx = 0, offsety = 0, parallaxx = 1, parallaxy = 1, properties = {}, objects = { { id = 123, name = "", type = "", shape = "polyline", x = 224, y = 576, width = 0, height = 0, rotation = 0, visible = true, polyline = { { x = 0, y = 0 }, { x = 128, y = -64 }, { x = 160, y = -64 }, { x = 224, y = -32 }, { x = 288, y = 0 }, { x = 0, y = 0 } }, properties = {} } } }, Check your map lua and the objects has a polyline table.

@@therevillsgames I also had my polygon layer named "slopes" but the shapes in my map lua are labeled as "polygon" not "polyline" and the table is polygon, not polyline

@@chromeWarriorXIII Strange, I added polyline only a week ago, but now when I add a new polygon in Tiled it does output the vertices in the polygon object :? Just update the code to read the polygon table :D Edit: ​ @meaningless [C]ode Ahhh - my "polygon" wasnt closed, so Tiled creates "polylines" table instead of "polygons".

world:newBSGRectangleCollider is the choice if you want polygon shape collider.

if u made a backup at ur game before doing this (i did this bc of this error) just create the 3rd backup and do on ur 2nd backup the tutorial, if it works, drop the main.lua in ur own game

SAME

.

.

@@Niko75999 y e s

I managed to get it working with Polylines and Polygons by looking at the structure of the testMap.lua file if gameMap.layers["Colliders"] then for i, obj in pairs(gameMap.layers["Colliders"].objects) do if obj["polyline"] then local lines = obj.polyline for j = 1, #lines do local point1 = lines[j] local point2 = lines[j + 1] if point2 then local line = world:newLineCollider(point1.x, point1.y, point2.x, point2.y) line:setType('static') end end elseif obj["polygon"] then local poly = world:newPolygonCollider(flatten(obj.polygon)) poly:setType('static') end end end

@@MirralisDias thanks bro

you can definitely code your own aabb collision system, that's easy. but then theres making collisions for things that ARENT just rectangles and then you have a problem along with that, your same logic applies to things like: input, audio, or displaying graphics. and also, the whole physics engine isn't really performance intensive. we're in a day and age where games don't have to be that performant, especially 2d ones, as computers have progressed so much.

SAME!!

me too

Double check your line 30 in main.lua. It's saying that on line 30, you're attempting to do a pairs iteration on some table, but it's saying the table you passed in doesn't exist. So check the spelling and capitalization of what you put inside of the parentheses, and make sure that a table with that same name exists in your code

@@Challacade i've got as the layer name Walls but if i write the gameMap.layer["Walls"] then i would give me that error. here is what i wrote walls = {} if gameMap.layers["Walls"] then for i, obj in pairs(gameMap.layers["Walls"].object) do local wall = world:newRectangleCollider(obj.x, obj.y, obj.width, obj.height) wall:setType('static') table.insert(walls, wall) end end

@@alessioturco953 it should be pairs(gameMap.layers["Walls"].objects) Looks like it was a minor typo, where you have .object rather than .objects

@@Challacade sorry to bother again but the objects spelling did solve that error but now i have this one and i don't know what it means Error libraries/windfield/init.lua:745: Box2D assertion failed: area > b2_epsilon Traceback [love "callbacks.lua"]:228: in function 'handler' [C]: in function 'newFixture' libraries/windfield/init.lua:745: in function 'newRectangleCollider' main.lua:31: in function 'load' [love "callbacks.lua"]:136: in function [C]: in function 'xpcall' [C]: in function 'xpcall' again soory for bothering and thank for the help

@@alessioturco953 I think that error normally means there's some wall objects in your Walls object layer that have an area of 0, which is invalid. Try deleting your Walls object layer, and creating it again, placing in only a few walls at a time and testing it out