Hi Moraldi. I was AFK, kind of, so excuse the delay. Should be dead easy to convert your Data file format to CS2 level format of the CSP engine. So basicly people could create their levels with your dropper.
Tho, personally I would put both things in one file, the Extra Props just following after the Data block. But ok, it's YOUR business :)
When I said ULD I meant UnLimited Drop.
Excuse me, I've got some stuff to do IRL these days, and I'm in the middle of an art break anyway :), so this may take some time (just saved your format description, of course), but this is definitely very cool. I was looking for somebody to write me a nice GUI for the editor, this way it may be a sideeffect we both can profit from.
Although - In my format there's a coupe more parameters, so ATM it could only be used for the basic setup of a level.
If you'll edit the file format in the future, then I'd suggest to do these things:
add one line for a comment for every object. My engine handles a lot of extensions in such a comment string, using trigger words and stuff.
Try to systematicly wrap the entity, just browse the docs and note every possible setting of an entity.
Example: if you allow to load a texture to a loaded mesh and then scale the texture then you'l be able to make fences etc. from simple quads with a tiling texture. If you can't scale the texture then you'll have to load an individual quad for each individual part of the fence.
Tho, personally I would put both things in one file, the Extra Props just following after the Data block. But ok, it's YOUR business :)
When I said ULD I meant UnLimited Drop.
Excuse me, I've got some stuff to do IRL these days, and I'm in the middle of an art break anyway :), so this may take some time (just saved your format description, of course), but this is definitely very cool. I was looking for somebody to write me a nice GUI for the editor, this way it may be a sideeffect we both can profit from.
Although - In my format there's a coupe more parameters, so ATM it could only be used for the basic setup of a level.
If you'll edit the file format in the future, then I'd suggest to do these things:
add one line for a comment for every object. My engine handles a lot of extensions in such a comment string, using trigger words and stuff.
Try to systematicly wrap the entity, just browse the docs and note every possible setting of an entity.
Example: if you allow to load a texture to a loaded mesh and then scale the texture then you'l be able to make fences etc. from simple quads with a tiling texture. If you can't scale the texture then you'll have to load an individual quad for each individual part of the fence.