Originally posted by imameliaMainly, it would really be nice to have some sort of if-then-else system. Quite frequently, I found myself needing to type and copy numerous descriptions and tilemaps that were identical or differed only by one small thing, and it would be useful to be able to do things like "set this 8x8 tile to 4F0 plus the value of bits 4-7" for timed platforms, "say 'falls off ledges' or 'stays on ledges' depending on bit 0, and say 'moves fast' if bit 1 is set" for some ground-based enemies, or "use a different set of offsets depending on whether the sprite goes clockwise or counterclockwise" for circle-moving sprites.
I'm not planning to put in a full scripting engine just for playing with sprite appearances and tooltips in the editor. That's a bit much effort for something relatively static that only affects editor display after all, not the actual game.
Originally posted by imameliaIt would also be handy for some sprites to be able to define some sort of length and width parameters for sprites whose tilemaps involve a long line of the same tiles (such as Firebars) or are large squares (the falling blocks from Yoshi's Island) and just be able to write that instead of a big list of offsets.
Convenient for a few sprites maybe, but only a few sprites are like that.
Originally posted by imameliaFinally, it would be good to make the default setting separate from setting 00, because quite frequently, 00 is a perfectly reasonable extra byte value to use in the level, but it can get confused for one that doesn't have defined parameters in the .ssc file, for instance, if you make a typo and put 1F when you meant 1C in a sprite that doesn't use all 16 possible values of the lower 4 bits. Perhaps if there is both a non-specific setting (such as 20 by itself) and one that specifically references setting 00 (such as 30020), the former could be used for the default instead?
The default isn't meant for catching typos...
If you're doing a lot of that kind of work and it gets too repetitive, you might be better off creating a tool to create and output the sprite settings you want in the .ssc file rather than doing it manually.
Originally posted by Rykon-V73There is a bug regarding Custom Sprite GFX Information (Editor Display Only). I specify the following command for a custom sprite:
This does show SP4=200 for the custom sprite. The bad thing is that it also shows SP4=200 for the regular sprite.
Technically that line would be for a regular sprite with no custom bit set.
But yeah, I see what you mean... it's apparently using the custom GFX information of regular sprites without any custom bit set for all custom bit settings. Thanks, it'll be fixed for the next version.