this post was submitted on 01 Aug 2024
22 points (100.0% liked)
Godot
5884 readers
1 users here now
Welcome to the programming.dev Godot community!
This is a place where you can discuss about anything relating to the Godot game engine. Feel free to ask questions, post tutorials, show off your godot game, etc.
Make sure to follow the Godot CoC while chatting
We have a matrix room that can be used for chatting with other members of the community here
Links
Other Communities
- !inat@programming.dev
- !play_my_game@programming.dev
- !destroy_my_game@programming.dev
- !voxel_dev@programming.dev
- !roguelikedev@programming.dev
- !game_design@programming.dev
- !gamedev@programming.dev
Rules
- Posts need to be in english
- Posts with explicit content must be tagged with nsfw
- We do not condone harassment inside the community as well as trolling or equivalent behaviour
- Do not post illegal materials or post things encouraging actions such as pirating games
We have a four strike system in this community where you get warned the first time you break a rule, then given a week ban, then given a year ban, then a permanent ban. Certain actions may bypass this and go straight to permanent ban if severe enough and done with malicious intent
Wormhole
Credits
- The icon is a modified version of the official godot engine logo (changing the colors to a gradient and black background)
- The banner is from Godot Design
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
https://gdscript.com/tutorials/classes/
Are you familiar with object orientated programming?
Basically you could create a class called Spell that acts as a blueprint. Add a variable for each property the blank spell needs to hold.
Then, in other classes, you create an “instance” of the Spell class, maybe called MyUniqueSpell and set its properties based on user input. You can have many different instances of the Spell blueprint; each with their own unique attributes.
In Godot, they say that Scenes can kinda behave as classes/blueprints too.
Of course, you can ignore OOP best practices and just use the code examples here: https://docs.godotengine.org/en/stable/tutorials/io/saving_games.html For small projects, ignoring the rules is okay.
will this allow me to create an execution stack?
You mean a stack of Spells to use? Yes. You can create an Array or List of Spell Objects and easily go through them. https://docs.godotengine.org/en/stable/classes/class_array.html