(J)RPG Fragments

This is a READ-ONLY snapshot of the Godot Community Forums when TwistedTwigleg was the owner, which is hosted for archival reasons only. The current Godot Community Forums can be found here.

Some links may point to external websites, including the current Godot Community Forums. These websites are not associated with TwistedTwigleg.

mechPenSketch

I'm creating an RPG Engine in small fragments, where one project contains one part of an RPG (such as overworld, battle etc). This way, users can pick which ones would fit into their game project and combine them.

This is one of them: https://github.com/mechPenSketch/Jrpg-Fragment-Overworld JRPG Fragment Overworld

When it comes to editing dialogs, I put the editor at the dock so that the user can easily refer back to the main screen to double-check the context of the dialogs.

The other (Battle System) is WIP. Once I'm done, I'll write a guide on how to combine them into a single project.

I would like others to make their own fragments.

mechPenSketch

An update to the other fragment.

I have completed the battle system here: https://github.com/mechPenSketch/Jrpg_Fragment-TurnBased_Combat

Now I'm waiting for my asset library entry to be approved. In the mean time, I'm figuring out how to combine the two fragments together.

mechPenSketch

I don't know how to handle globals when it comes to combining fragment. Should I have one autoload entry per fragment, or just one for the whole project and teach the users what relevant properties and methods to add into?

The former seems more convenient for the users, but I'm afraid it could accumulate into having too many nodes.

[ADDED] In the end, I chose having one autoload per fragment, as having so many node is not really problematic as long as they don't all run at the same time.