I began development on this extension about a week ago, and it’s shaping up nicely. Defold Grid Engine provides grid-based movement, interactions, and utility features to a Defold game engine project.
Grid systems are popular when working with tilemaps because they greatly simplify character movement, pathfinding, collision detection and response, and many other technical challenges. Grid systems also harbor a certain charm, probably due to their iconic usage in classic franchises like Pokémon and Fire Emblem. I have been itching to use grid mechanics in my own games, which led to the creation of dgrid.
I am updating this thread to alert that DGE has undergone a major update. If you’re using this module in any of your projects, please read the new documentation on GitHub. Additionally, I am pushing to perfect grid-based movement. As a result, DGE temporarily no longer supports diagonal movement so I can focus on improving cardinal functionality.
A suggestion is to make use of the “Releases” feature of github.
That way users can stay on a certain release, while you can move ahead on master branch with newer features.
We always recommend users to use specific features, or they might suddenly find themselves in a situation where they don’t know what went wrong.
This is absolutely not a an issue for me; I am just browsing the Asset store for inspiration. So zero issue if it is not fixed. I should really spend some time working out what is wrong myself, so I am not expecting anyone else to do this , in my place.
What I think the real issue is, is that the asset store should have a way of marking assets that don’t work, on the Asset store (and not rely on the github page), or maybe mark ones that do work ‘certified’,…, thorny problem I guess.
Thorny, thorny. Most used frequently assets are always up to date and bug-less. I checked this asset on release and it was working, now I’m not using this asset, but I use other assets by @WhiteBoxDev and those are of high quality.
I checked and there are some issues regarding format, I’ll investigate and create a PR with update
Edit:
There are also some code issues, but I have it working now more or less:
Thanks for taking a look. Open source contributions are fantastic, sometimes they gather a bit of dust, totally understandable. I try my best to ask about status without any kind of negativity. Specially since I am really good at holding on to the wrong end of the stick, if I am not careful .
If you check the asset page for Defold Grid Engine there are 2 different links, one ‘specific version for development and release’ and one for ‘latest version’. The ‘latest version’ seems to work just fine.
I’ll accept PRs, but please ping my account in a public reply here on the forums. I don’t use my WhiteBoxDev account anymore, anywhere.
I believe this library was left in a strange state. Something like, it was being rewritten from scratch (which is what you’ll find in the master branch), but the documentation was never updated to match the rewrite. Not sure. If it’s in a working state, then great!
As a side note, there are only one or two libraries I’d actually recommend using from my GitHub nowadays, since most of them were made when I had much less experience with Lua and Defold, and are better off implemented manually to account for project-specific details.
Thanks for the info. Your stuff is good to have, things being a bit rusty is fine. Figuring out what is wrong is good to do. It would be good if the Asset page could have some sort of a status flag for all assets. The ultimate would be a test for CI to run (on latest builds of Defold), no idea how this could be done though.
Completely agree. I think Defold’s “anybody can add pretty much anything to the Asset Portal without much verification” approach was reasonable when there weren’t nearly as many people releasing stuff, but now that the community has grown over time, it’s less and less desirable. It’s tough to know what’s good and what’s not without personally vetting the code and checking out the author’s history for reputation issues. I mean, you should always do those things to some extent, but it would be nice to have a more reliable system in place.
…or something like that. I’m not wording my thoughts perfectly here, but yeah.
OK, I had that impression I made it to the state when it’s working on main and I updated documentation, I might create a PR maybe to discuss the direction, if it’s cool, if not, I can always make a for anyway
.
I made it to the state when it’s working on main and I updated documentation, I might create a PR maybe to discuss the direction, if it’s cool, if not, I can always make a for anyway 