programming

more entity thoughts : sep 16

crap. crap. crap.

are groups a good idea? they would work well for modding vehicles, but they add
complexity to everything.

scenario.

build golfcart + 2 sticks in max
export it out
add golfcart to map
modify golfcart in max and have it updated in all maps

this kinda sounds like you need a group or external reference or something. maybe
it is insane to provide functionality like this. if you remove geoms or move them
significantly then any pins in the maps that are attached to it will be way off.
maybe there needs to be a more formal definition for attachment points. maybe there
also needs to be a more formal definition for the initial map vs a save/load map.
a save/load map really is the same though. if i want to hang the golfcart by a
rope then you should be able to do that. maybe you should just make sure the
geometry of the golfcart is finalized before you start placing it in maps. there
are some things that should be tweakable later. stuff like how it drives. still you
could modify limits and that could break things. i guess you just have to play it
and find out. so the developer has to have a little discipline. so what.

does the gbASE approach work or should it be changed to an external prototype +
overrides? should geoms, joints, and wires be first class citizens? maybe you could
build the entity stuff in such a way that the code works like a linker. wait lua
is dynamically typed, that won't work.