Armoured Wizard

Godot - major refactor needed.
Equipment is getting quite complex, and is currently stored as a Dictionary of Dictionaries of Arrays
I'm thinking of making it a Class. But maybe a Resource?
Equipment needs to know:
Playbook/General
Name
Description
Load
is_equiped

Each item can only be instantiated once, and the only bit that ever changes is is_equiped

Advices?

#godot #gdscript #gamedev #godotengine #ttrpg #rpg #BladesInTheDark

Mar 13 at 11:56amWeb
Show threadLuke MillerMar 13
@ArmouredWizard I have had some luck switching from dictionaries to resources but it takes some adjustment mentally as it moves a lot of the game from the code to the instance of the game (eg defining stuff in the editor)
Show threadLuke MillerMar 13
@ArmouredWizard If you do go down the Resource route, you will probably over-engineer it (coming from code) to begin with and also have to redo it a bit so remember to be kind to yourself!
Show threadArmoured WizardMar 13
@upmultimedia I'm currently getting lost in trying to find my way through nested dictionaries to find/alter values. It sort of works, but is a mess.
My instinct is to make a Class, but I think The Godot Way is more Resource/Node focussed.
Show threadthomastc | frozenfractalMar 13
@ArmouredWizard @upmultimedia If a plain class is what you need, use a plain class. Resource is only useful if you want to modify it in the editor and save it to disk. Node can also be used for modularity, but is often overkill if you don't need to interact with the scene tree