Impacts of Node Versus Node2D For Root Node?

Archive
1
:information_source: Attention Topic was automatically imported from the old Question2Answer platform.
:bust_in_silhouette: Asked By goshot

Are there any? These reddit posts talk about potential issues, but none mentioned seem to exist in Godot 3.1.1:

https://www.reddit.com/r/godot/comments/71qvix/what_are_the_benefits_of_using_node2d_as_the_root/
https://www.reddit.com/r/godot/comments/9xkax8/difference_between_choosing_node_vs_node2d_as/

Even with Node as the root, any Node2D can still be positioned and moved around the viewport. Any Node2D child of a Node that is a child of a Node2D retains its positioning relative to the grandparent Node2D.

The response from MysteryGM in this reddit post suggests that a reason to have a Node2D root is in case you want to position the whole scene inside another scene at a position other than origin of that other scene. Is that a valid consideration?

https://www.reddit.com/r/godot/comments/a0ecra/style_question_every_scene_having_a_plain_node_as/

Doesn’t matter. Just use any. You can quickly switch root node type when you need to position things or run into any kind of problems.

Dlean Jeans | 2019-07-07 21:10

2
:bust_in_silhouette: Reply From: Magso

Node2D root is in case you want to position the whole scene inside
another scene at a position other than origin of that other scene. Is
that a valid consideration?

Yes, Nodes would be better for maps whereas Node2D/Spatial can be used for features within the game but usually things like players and enemies are RigidBody or KinematicBody.