Godot terminology guide plus my suggestion: Page 2

Godot terminology guide plus my suggestion

Bimbam

I am always tripped by Godot Jargon

Well on the one hand you could submit an idea for a forum improvement to automatically regex all capitalised references to become URL links to the docs where applicable, but tbh this may do more harm than good and be a nightmare to maintain (kinda would be nice though, some questions may even answer themselves lol).

On the other hand, just bookmark this page and over time as you read more of the docs you will become more used to what's available in the API and learn the terminology. Scenes & Nodes are the second link.

Also if people refer to a class or term you don't recognise, it is likely in this list and if not the search function in the top left:

I've been using Godot for about a year, and pretty much will be in the docs on the daily looking something up. There is no shortcut for this, it's the best place to learn.

Ultimately, this is exactly what would happen when learning any other API pretty much ever. I mean, almost nothing in Godot is actually identical to implementations in other engines, as even similar classes will have functions that may differ in name and/or nuances in execution. E.G https://docs.unity3d.com/ScriptReference/Vector3.html vs. https://docs.godotengine.org/en/stable/classes/class_vector3.html vs. https://docs.unrealengine.com/4.27/en-US/API/Runtime/Core/Math/FVector/ vs. https://developer.valvesoftware.com/wiki/Vector vs. https://docs.cryengine.com/pages/viewpage.action?pageId=29448783 vs....

This is not limited to Godot. It's rare that anything ever does and should never be assumed.

As for creating new nomenclature for existing documented Godot terms, this strikes me as the opposite of user/beginner-friendly as your just adding an abstraction layer for seemingly no reason and I (and I imagine many others) would vote no on that. It would only make sense if at an engine level you renamed everything and prefixed it with something, but doing this is just a horrible redundant naming practice in general.

I mean, you wouldn't do this right... class MyClass(): def MyClass_MyFunction(): pass

cloa513

It is not so much what the terms means which is certainly one issue but that the terms are easily confused with non-GODOT terminology.

cybereality

No, they are not easily confused. But if you don't put in effort to learn what they mean, then maybe you'll be confused. It's like, if I want to learn a new language like Japanese. I don't go on a Japanese forum and tell them they have to reinvent all their words to make it easier for me. It makes no sense.

cloa513

@Megalomaniak said: Well in that case, similar to every other engine godot only has 1 "scene" thing and that is the scenegraph. tscn is just a file holding data about nodes that can be instanced into the scenegraph and thats it. The scene graph is the only real scene and it always holds/includes: 1 "root" viewport that rest of your scene data/nodes would live under(i.e. what you composite in the editor) and it has as siblings all your autoloads/globals.

BTW. a tscn file is also known as a PackedScene. So there you go, Scene specifically still refers to exactly the same thing it does in unity or unreal and what you want to have a specific term for has it - a PackedScene.

While that text is good, you just as easy express it graphical using the GODOT Engine view which > @cybereality said:

No, they are not easily confused. But if you don't put in effort to learn what they mean, then maybe you'll be confused. It's like, if I want to learn a new language like Japanese. I don't go on a Japanese forum and tell them they have to reinvent all their words to make it easier for me. It makes no sense.

It is easily confused because people use common English and GODOT terminology all the time- you could advise experienced answerers to avoid using common English especially where it conflicts with GODOT terms. There is a big difference Japanese looks like mostly look like Japanese and sounds like Japanese (and most other foreign languages). Technical languages in English look like English (all sorts of technical languages have this problem).

xyz

All your Gconfusion can be remedied by spending some quality time with Gdocumentation. Gtutorials and Gforums can only get you so far :)

If you don't quite understand what a word means in the context of specific discussion, you can always ask for clarifications. That's just how language works. Most words have multiple meanings. Some are used for dozens of different things. However, you always get several levels of context to deduce the right meaning (sentence, paragraph, chapter, topic, field). Context is as important as words themselves.

Multiple and overlapping word meaning ensures language flexibility. Otherwise you'd need to constantly invent new words which would be far more confusing and extremely tedious.

« Previous Page