We’ve agreed that our current borders scheme works, but isn’t quite what we need. Let’s see how to make some progress in how we make this dungeon. This pass, we prepare the soil. I have a bit of a theory about what we might do. Let me lay it out and then we’ll look at the code we have and decide what we can do. I’m tentatively proposing a small set of standard floor tile asset names that embody some semantics that both humans and computers can deal with. There are 16 combinations of borders, counting cells with no borders and cells with borders on all four sides. We could give the combinations somewhat meaningful names: Name Purpose F Regular flooring E Tile with border on east N Tile with border on north EN Borders on east and north ENW Borders east, north, west ENWS Borders east, north, west, south Then we could build a dictionary with those keys, pointing to a list of asset file names that could serve in that position. Probably we would have an associated list of weights, which we…
No comments yet. Log in to reply on the Fediverse. Comments will appear here.