Posso aprender slang do Reddit com o SubRead?

Sim. Leitor calmo: abra um thread, destaque uma frase, obtenha explicação e salve como cartão.

O que é Language Lab?

Pacotes curtos (tempo, hedging, slang, reações) como se escreve no Reddit — depois pergunte ao Iggy.

Serve para ESL / nível intermediário?

Sim: posts e comentários reais em vez de diálogos de livro, com IA quando o tom ou slang não está claro.

Preciso de uma conta?

Pode ler sem. Entre para salvar cartões, favoritos, chat com Iggy e perfil.

r/godot · u/stonehead741 de ago. de 2026, 16:06

How can I reference a node in a resource?

I have a game with a Level class that can have different objectives, one of which is to defend a specific character. I have an abstract Objective class that the Defend objective class extends. This Defend class has a reference to the specific character that must survive.

In an effort to make it easier to develop multiple levels, I'm converting the Objective class to extend Resource, so that it can be defined in the editor instead of just in code.

My problem is, the I can't export a reference to a Node in a Resource. I did some searching, and I found the NodePath, but that gives a string that's relative to the Level object.

Is there some way to give a Resource a pointer to a node from the editor? There seems to be no problem with these objects storing references to nodes, only with exporting them to the editor.

The only other option I can think of is to give Objective both a Character and a NodePath, and have the Level go through every Objective in its _ready function, look up the node path, and assign it to the Character of that Objective. Is there a better solution than that?

Comentários

u/Bob-Kerman11 de ago. de 2026, 16:19
I wouldn't use resource for this. It sounds like it belongs to a specific scene/level. So I would just write a class that extends node, and has all the variables exported. Drop it into the level, and set the objective with an exported node reference. Otherwise, yeah you would have to use either a node name, or node path. Both of which are prone to mistakes, and breaking from changes. Maybe groups? Would avoid some possible mistakes.
- u/stonehead7411 de ago. de 2026, 16:29
  I can do that. Is it best practice to use Nodes for things that don't end up using position, \_ready, \_draw, or things like that? I guess I just assumed that would be wasteful.
  - u/thecyberbob11 de ago. de 2026, 17:33
u/Silrar21 de ago. de 2026, 16:22
You don't. Resources explicitly are not meant to hold node references like that. If you need a node reference in the editor, put it on the node the resource is on. Thing is, does it have to be a resource? The objective is tied directly to the level, which makes it unusable anywhere else. It would make a lot more sense as a Node to begin with. Yes, I know it's counterintuitive, and it feels wrong to have something that \_should\_ be just data in the tree like that, but I've come to realize that this is really the best solution in most if not all these cases. Resources are great for when you actually have things you want to reuse. For example, you could have an "Objective" Node with an "ObjectiveParameter" Resource and an Array\[Node\] as targets. The Resource would then be a "DefendObjectiveParameters" Resource or a "EscortObjectiveParameters" Resource, or a "KillObjective Parameters" Resource, and so forth, and the logic would mean that you need to fulfill the parameters on the targets.
- u/stonehead7411 de ago. de 2026, 16:27
  Several different levels have the Defend objective, so it is reused across different nodes, just with different parameters. I can make it a node, but nodes have a position, ready, process, draw, and a whole lot of other functions that this. It seemed wasteful to put all this on an object whose purpose is to hold a few functions that the level can call. Is it common to use Nodes for objects that don't *do* anything themself?
  - u/[deleted]11 de ago. de 2026, 16:41
  - u/Silrar11 de ago. de 2026, 16:43
  - u/Silrar11 de ago. de 2026, 16:50
u/NotXesa11 de ago. de 2026, 16:22
Resources don't necessarily live in a scene tree so they can't have direct references to a instanced node. What you can do instead, is to have the Objective class extend Node, or Node2D/3D, and a ObjectiveResource class. The Objective class can be configured via an ObjectiveResource for the stuff that is not dependend of the scene tree, and use exported variables for the stuff that depends on the scene tree.
- u/stonehead7411 de ago. de 2026, 16:31
  That could work. Is there a reason to use ObjectiveResource for static configurations like turn count instead of exporting that from the Objective class?
  - u/NotXesa11 de ago. de 2026, 16:54
u/billystein2511 de ago. de 2026, 16:23
You can export a NodePath and run get_node using that path (get_node is on scope Node so you need to run it from the node this resource is attached to) or export a Node on the node that the resource is attached to and request that reference.
u/[deleted]11 de ago. de 2026, 16:29
[removed]
u/dfx8111 de ago. de 2026, 17:09
You can't assign node references to resources as resources technically are something saved to the disk. Best you can do is node path. What can you do is to have the Objective class extends Node (not Node2D/Node3D, regular Node have no rendering/positioning) and put them in the scene. You can also disable the node process entirely if it's not needed, but Node is lightweight enough so it won't matter anyway. If you want something even more lightweight, you can go lower into RefCounted or even Object but these will need to be instantiated and held by your level script since there's nothing to add to the scene at all.
u/partybusiness11 de ago. de 2026, 18:16
I think NodePath is the most likely solution. If you look at ViewportTexture for an example, that is a Resource, because it inherits from Texture2D. But it needs to be able to access a given Viewport in the scene. The viewport_path property is a NodePath. The other possibility is make your Objective class extend Node instead of Resource. Resources can exist outside of any Scene file which can be convenient in some cases but if your Objectives need to be tightly coupled to things inside of a given scene file, you maybe don't need that.
u/TehRoboRoller11 de ago. de 2026, 20:18
Other than the solution of simply making it a node with exportet values instead of a resource, you could inject a reference to a node (for example a reference to the player or the scene tree or whatever), and using that node could then let the resource get access to other modes via things like groups. In the nose that holds the resource, you could do something like whatever_resource.owner_node = self.