|
SoCoder -> Blogs Home -> Blogs |
|
|
|
|
Jayenkai
|
Making my 7,000th level editor.Nngh.. |
|
I like including level editors. Having a level editor included in your game means two things. 1) You can build up levels quicker. 2) You can get away with having less levels in your game, and instead expect others to make their own! The problem is, though, that I've done this hundreds of times already. If mousein((x-1)*16,(y-1)*16,15,15) and mousedown(1) then map(x,y)=DrawWith I can do it with my eyes closed. I'm so sick of rewriting this! I suppose I should develop an all-in-one super editor, and then shove it in as a function. The main problem, though, is that my level data might be the same, but the ingame usage of that data is always changing. I have to keep tweaking bits here and there making my level editors show different things. In this case, the editor must deal with multiple level types built within a single level! The whole Platdude/Mario/Sonic thing means you'll have to flip between all the different views to check your level works with that character. In one mode a brick might be a pipe, or a rope could be a cloud. It's nuts! Why do I keep doing this to myself! |
|
|
|
|
Comments |
|
| Sunday, 13 May 2007, 07:17 | |
Blitz3Dman
|
Yea, I've written a level editor for every game with levels I've made now.
|
| Sunday, 13 May 2007, 09:46 | |
Phoenix
|
Stop doing that kind of games, then!  Or, make the editor in a really odd and original way, so you'll have to think about how you should code it.
|
| Sunday, 13 May 2007, 13:32 | |
JL235
|
I haven't read the whole article, but this is about someones reflections on writing three scripting languages, one for games. You could try writing something similar for designing and editing levels. Where sections which are re-used commonly are in there by default. At the very least you should write a library of common commands. |
|
| |||
|
| ||||