Initial; Added: notes, part.tscn, *.gd glue scripts

notes.txt

@@ -0,0 +1,21 @@
+Thoughts on the API:
+It needs to satisfy the following:
+ - Being mostly backwards compatible with the old roblox code, maybe using an _ to translate? Also very automatic in nature, networking should just work.
+ - Being 'forwards' compatible with a potential bevy implementation. so all 'objects' need to be fully abstracted. anyways. Being kind to a nellie style implementation. So lots of OOP and abstraction as above.
+ - Allowing access to a lot of weird stuff we didn't have before. (consider the mesh systems) which also means we will need access to some 'services' (that we can expose again through _G so it swings both ways...)
+ 
+ Maybe it would make more sense to have a sort of ID or name for every single type of thing in the
+ api, or 'scene'. That is quite weird, though it would mean that vehicle objects and their
+ properties could also be encoded. Maybe if each vehicle object was a sort of 'package' idk.
+ Although the game code does trace through objects.
+ 
+Part(){
+  
+}
+
+Accessory Ideas!:
+- Different body types: floating limbs
+- Dunce hat
+- Wizard outfit
+- Long coat outfit
+- Combinable faces