11–20 of 111 posts
You might want some sort of mention in the website copy about it being self-hostable (unless I'm misinterpreting the docs). The website copy talks about your hosting and the related benefits (as it rightly should), but I didn't see any mention of self-hosting so I almost didn't click through to the docs to see that local development is possible.
All of that said, as someone who has developed a card and dice game, using plain html and javascript to create a programmatic version that could be played online, I am still having a hard time figuring out how to recreate that kind of thing, using your system.
Based on the docs, I can see it supports cards. And based on my experience developing the same basic gameplay, I can see that it's general-purpose enough to be suited for a wide variety of games (and my game is simplistic, so it should be possible). Feels like it should be a pretty straightforward build, with a robust enough library, and yours seems to be fairly robust, so my thinking here is that a step-by-step tutorial would go a long way. I know enough to see why you've chosen the abstractions you have (Actions, Flows, selections, conditions, prompts, etc), but without seeing them constructed, it's hard to know where to make the specific changes I would want to make.
Anyway, just one opinion! It may feel more straightforward to other people. But I don't think I would personally make much headway with it, without a tutorial.
Hey this looks great. I'm working on some AI bots for board games and this might be really useful as a frontend for local testing of the bot players. I'll check it out.
I'm looking forward to trying this out! You might want some sort of mention in the website copy about it being self-hostable (unless I'm misinterpreting the docs). The website copy talks about your hosting and the related benefits (as it rightly should), but I didn't see any mention of self-hosting so I almost didn't click through to the docs to see that local development is possible.
Looks very cool, congrats on the initiative! I think it can be great to develop prototypes, but to build a BGA alternative you will need permission from the publishers to implement / distribute their games, and given how big is BGA and that it belongs to Asmodee, that is going to be tough... Hope I am wrong, good luck!
> In short: you can trademark the name, logos. Have copyright on art (even the board itself as art). You can't copyright the mechanics, processes or rules. That explains the Monopoly/Scrabble clones.
https://www.reddit.com/r/gamedev/comments/10f2nov/comment/j4...
which refers to this youtube video:
Looks good! There's a lot of moving parts for such a wide array of functionality, so this looks like a lot of really good work! If nothing else, it's nice to have a game engine that focuses on tabletop games, that doesn't necessarily focus on how to render said games. All of that said, as someone who has developed a card and dice game, using plain html and javascript to create a programmatic version that could be pla…
Earlier quoted context omitted.
Co-creator here. I thought AGPL was ok as well, but Commons Clause specifically tried to address perceived deficiencies in the AGPL although I admit that it didn't really seem to catch on. I'm not super well versed in the technical details. Why would you recommend AGPL?
https://fedoraproject.org/wiki/Licensing/CommonsClause has several links explaining what's wrong with the Commons Clause. The reason the AGPLv3 is my preferred replacement is that the FAANGs are irrationally afraid of it and refuse to let it be used anywhere in the company (e.g., https://opensource.google/documentation/reference/using/agpl... ), but it's still 100% Free Software and Open Source and so allowed to be p…
I tried but couldn’t test right away, is this more like BGA or TTS?
Earlier quoted context omitted.
https://fedoraproject.org/wiki/Licensing/CommonsClause has several links explaining what's wrong with the Commons Clause. The reason the AGPLv3 is my preferred replacement is that the FAANGs are irrationally afraid of it and refuse to let it be used anywhere in the company (e.g., https://opensource.google/documentation/reference/using/agpl... ), but it's still 100% Free Software and Open Source and so allowed to be p…
[flagged]