search

db0 / godot-card-game-framework

A framework which comes with prepared scenes and classes to kickstart your card game, as well as a powerful scripting engine to use to provide full rules enforcement.
http://dbzer0.com/projects/godot-card-game-framework/
GNU Affero General Public License v3.0
892 stars 95 forks source link

Premade tutorial project #172

Open nightblade9 opened 2 years ago

nightblade9 commented 2 years ago

I looked through the installation instructions. A lot of them mention copying things from the core folder into a new folder. It looks like a lot of steps.

Is there any way you can create a premade project that you can just clone/unzip and go? It sounds like you can include any older version of the framework, and users can upgrade by getting the latest version and copying over core.

db0 commented 2 years ago

I've actually had an idea of making a script file which would do the quick-start steps automatically for someone who wants to not bother, but the point of the quickstart is to also introduce some concepts to new players, so that they understand the components. Technically one can simply use the custom folder directly without any copying.

nightblade9 commented 2 years ago

I see; that makes sense. Maybe I can explain my suggestion with context: I'm looking to prototype a card game with your framework, and I'm looking for the easiest possible solution to get it running quickly. For me, a template/script would be ideal. (I read through all the manual steps in depth and looked at some of the code to make sure I understand how things work.)

Thanks for the hint about being able to use custom without copying. I actually thought the right approach is to extend (not copy) core classes, so that you can upgrade them later and get the benefits of upgrading (does that work if you copy them?)

db0 commented 2 years ago

I actually thought the right approach is to extend (not copy) core classes, so that you can upgrade them later and get the benefits of upgrading (does that work if you copy them?)

That is correct. You should always be extending classes or inheriting scenes from the core/ folder, if you want the framework to remain upgradable.

For a quick prototype, keeping the custom/ folder as is and adjusting it from there should work just fine. The scenes and classes in it are already extending/inheriting as needed