>>all levels should have access to a default.obj (with generics) and a level.obj (with specifics).
I agree, everything in the current obj file is a generic, this was my point about having a seperate look up for the scripts on a per tile basis.
>>layer then becomes a string, not an integer that defines the object class and the input parameters
I think you're over complicating it, if you just had the string holding the overwriting script it would be a done job. And if you had the complete script in the string then you could do away with level.obj file.
Infact... (Thinking as I type) Once we have a compile level function in the editor we could make it so it puts the generic scripts onto the script layer and then the game doesn't need any obj files at all.
And what do you think about the idea of a "cannot reach the ceiling" flag on the collision layer?
I agree, everything in the current obj file is a generic, this was my point about having a seperate look up for the scripts on a per tile basis.
>>layer then becomes a string, not an integer that defines the object class and the input parameters
I think you're over complicating it, if you just had the string holding the overwriting script it would be a done job. And if you had the complete script in the string then you could do away with level.obj file.
Infact... (Thinking as I type) Once we have a compile level function in the editor we could make it so it puts the generic scripts onto the script layer and then the game doesn't need any obj files at all.
And what do you think about the idea of a "cannot reach the ceiling" flag on the collision layer?