Skip to main content

Playing with Resources

Took me some time to discover that ScriptableObjects equivalent in Godot are Resources. After researching and asking a bit, I made a quick test last night that went surprisingly well.
I wanted to test the OOP capabilities of GDScript, more specifically, if I could extend the Resource class for my own twisted and evil purposes, the same way I used ScriptableObjects in Unity. That is, to store items, skills, etc. It sort of works. Excuse me if I dont show any code, but Im still not sure that what I did was completely right and I dont want to point anybody in the wrong direction.
But I do can show you at least this. Lets suppose I want to have my items stored as resources, so my first step was to inherit the Resource class:

extends Resource
class_name BaseItem

export(String) var Id
export(Resource) var mesh
****

The base class contains all the info needed in all child classes, as usual. I can even store a Resource inside of another, in this case, the item mesh. Any item type in the game can have its own class:

extends BaseItem
class_name ItemWeapon

And of course, reimplement and override any function from the parent class. But be careful, because any value written to a resource will be replicated to everywhere the resource is referenced. Still havent found a way to create different instances or copies, although maybe I wont need to if I design some way to use them only as data sources, not actual items.
The next step is to learn enough about dictionaries in GDScript to implement my dialogs (and then a dialog editor), which of course, will be stored as Resources.
Labels:

Comments

Post a Comment

Popular posts from this blog

Isometric camera with Godot

Took some effort and some of my sleep hours, but at last, I made it. Here is my first videotutorial: implementing an isometric camera in 3D, with Godot. Useful if you want to emulate the look of old classics like Fallout 2, but with some extra features. Considering that my voice is not so nice, and my english pronounciation is even worse, I also added texts to help you underestand what Im saying. You will also notice some background noise, but cant do anything to solve that. Any suggestion is welcome. Expect another tutorial soon.... or sor tof. This time, will be about my AI system.
Post a Comment
Read more

Unity3d isometric camera tutorial

I had pending this since a month ago, so Im forcing myself to post it today. The goal is to provide a fully functional isometric like system that you can use with few or none modifications in your own game. So, lets get started. Start Unity3d and in your scene, add an empty GameObject, we will call it target . Create a camera object and drag it to target to make it child. The result looks like this: Now select Camera and set the values to this: For a true isometric like feeling, ortho projection is essential. You could use perspective, but it is not the same. Play with Size to suit your needs (we will be using this later, when implementing zoom). Now, lets create an script named CameraController, or whatever, and drag it to target GameObject. Lets implement scrolling, the easier part: go to Update() and add the following code: if (Input.GetKeyDown(KeyCode.W)) {             dir = UP;         } e...
Post a Comment
Read more

Vulkan and open source engines

It is weird, but even when Vulkan has embraced the open source philosophy (open drivers, tools, etc), Im not seeing too much enthusiasm to adopt it in open source game engines. I have been following mostly Godot and Urho3D, yet Ogre3D and Irrlicht doesnt seems to be rushing to implement the new renderers. It is worth to mention that Godot promissed they would delay the long needed refactoring of its 3D renderer until Vulkan release, but now they say they wont be using it, favoring GL ES 3 instead. The other engines seems to be dealing with lack of man power (Urho3D leader left the work on hands of community, as he is not working on Vulkan renderer right now) and base code designed for older APIs, specifically, DirectX 9. Lot of work is required to adapt this code base, not only for Vulkan, but for DirectX 12 too. Well, nobody said that developing a game engine was easy. The advantages of Vulkan have been widely detailed. From engine point of view, it would centralize all renderers...
3 comments
Read more