This PR changes the "export"s in the Array section of the GDScript Exports documentation to the "@export" annotation to be in line with 4.0.
Also slightly touches up the wording when referring to default null assignment and Packed*Arrays.
NativeScript 1.1 has been supported in Godot 3.1 and later, which
means the latest version of the documentation doesn't need to
cover it anymore.
This also improves grammar and writing style.
As per this post (and merge to master):
https://godotengine.org/article/multiplayer-changes-godot-4-0-report-2
The multiplayer annotations have reduced down to only @rpc (as far
as I can tell? apologies if I've miss interpreted this)
- removed the deprecated annotations and replaced with @rpc
- replaced an example that referenced @remote
Makes it more clear that Node is not freed automatically.
The part that states RefCounted as the default was moved to Inheritance
WeakRef example was altered to show a RefCounted object not prevented from freeing.
GDExtensions has been merged into the godot-cpp master branch. The tutorial should specify to use the 3.x branch if the reader is creating GDNative scripts.
Co-authored-by: Hugo Locurcio <hugo.locurcio@hugo.pro>
Minor change to avoid unnecessary confusion by conditional statements not executing properly if a beginner programmer uses square brackets rather than parentheses to enclose a condition.
An Objective-C method call will not be ignored when the object doesn't
define the method. It will crash with a runtime exception.
The author may have been thinking of the way an Objective-C method call
will be ignored when the object is nil. But that's not the case when the
object is there and lacks the method. In that case, the runtime will
call -doesNotRecognizeSelector:. The default behavior in the root class
NSObject is to raise an exception (not the try/catch kind; a similar
case is array bounds checks) and deliberately crash.
https://developer.apple.com/documentation/objectivec/nsobject/1418637-doesnotrecognizeselector?language=objc
Both, the _process() and _physics_process() are not called every time the engine draws a frame like its written here, only -process() does. _physics_process() gets called before each physics step like it's explained on this same page.
