Problem : We have two circle bodies c1 and c2 of radius r1 and r2 (love.physics made) we place these circles such that r1 is above r2 and they are in contact with no overlap. I wish to loosely weld c1 to c2 such that c2 always is attached to the point it is in contact with from creation. Or specifi...

encountered an issue, take the below code local defaultStyling = { bgColor = {12, 183, 242, 170}, -- LOVE blue fgColor = {255, 255, 255, 255}, -- Foreground color tooltipFont = love.graphics.newFont(10), -- tooltips are smaller than the main font radius = 3, -- radius for the outer shapes of compone...

using the set value method on button should accomplish that if my memory serves right, i havent touched love and love frames in half a year though.

I remember playing 'X3 : Reunion' awhile back. My primary goal every time in that game was to be an amazing merchant. I would start by plotting where each station is and what they produce and what prices i can expect. I slowly discovered certain stations prefer certain goods. So i started making man...

At a quick glance the only advantage Traveler poses is the difference of nodes definition and handling. In Traveler its more setup initially to create a world/grid. But it allows customized neighboring nodes and such. Personally id recommend jumper if you want a more reliable and variant solution. B...

GitHub wiki page completed. Give feedback and help me make it more understandable if you wish! Small fix pushed to Git. Version 3.0.0.2 Major notes are : The Demo is now on par with the Git hub wiki Fix to G Cost calculations not working properly when Nodes don't have a parent initially. Its now not...

A total rewrite was done. Moved to using a OOP approach (greatly improved the ease of coding everything and eliminated bugs) Documentation is to come, but the demo shows off well the usage of the library. Im sure all previous functionality and features were kept, in fact new features were added such...

Thankyou, normally id use early exit like that. not sure why i opted for that there. does table contain is wierd atm, it gave me strange issues. I think due to storing my nodes in two tables (as you notice i use a Node[x][y] and FlatNode to store nodes and it was not liking that. Also my heuristics ...

UPDATED! Now faster, more accurate and with more specifications : 1. Users now can specify what tags a node or solver contain. 2. Tags are now compared between the two when determining traversability. 3. Solvers can now use one of three rules when comparing tags, either match any, match all ignoring...

Notice : A total rewrite has been done, currently there is no documentation but it is being worked on. See page bottom for github link and demo > License = DO WHAT YOU WANT* *But please kind append original @author to any modified versions. Source and reference : http://www.policyalmanac.org/games/a...