Hmm, but that'd be a huge mess to implement :|
And then you wouldn't know what sprites have been edited.

Anyways, I did it this way so no need to suggest more

I want to be able to have a radio button to choose between two different options for sprite 83:

Pre-defined, and manual.

I also needs this for the Lava, because for nibbles 10-11, any value greater than 128 will make the lava go down. So, I want to have a radio button between two value fields (one with a 128 offset, and one without) so I can change the speed more flexible this way.
Also, I would like a limit on the value of the spinner. This will make it so the one without the offset will not exceed 128 and go down.

And: A VERY ANNOYING BUG:
When I create a new field (such as a value, checkbox, list, etc.) and put in something into the options for that field, whenever I click "Save", it saves the new field without the options!
So sometimes I have to retype everything for that field (which can be a lot, like in the example of sprite 83), which is very annoying.

I would appreciate these things to be added/fixed.

EDIT: I would also like the feature to rearrange fields, to make things more organized, so you don't have to delete the field(s), and recreate it.

- For the lava 128 thing, you have to make it a signed value.
- That bug? I don't have it.
- Yes, reordering fields would be a nice addition. But doing it is not that trivial...

Don't have a solution for the Sprite 83? Ok.
I'll take a look at the new sprite DB features when I find time.

Thanks, Dirbaio.

Checkboxes broken:
Setting the mask will not actually set that value when the checkbox is on. It sets it to 1 always.

EDIT:
Feature or bug, about lists:
When you have list A on a nibble, and you manually put a nibble value that is not specified in list A, the list becomes blank.
Then, when you change some other value (e.g. check a checkbox, change another list setting, increase/decrease spinner value, etc) it causes list A to change it's setting to a known setting. Can you change it so it will just say "*Unknown value ASDF*" where ASDF is the nibble value, and so that it automatically doesn't change the value to a known one? It will make discovering new values easier.

EDIT2: The list thing also applies similarly to other field types. Please fix those too.

Mispelling in Sprite DB:
"Nybble" should be renamed to "Nibble", because "Nibble" is the proper spelling.

Not yet implemented on the editor's side.


Nah. Too much work for such a little feature. You can always see that a listbox is blank, and then look for the corresponding value in the raw sprite data box.



Uhmmm, what field types and how?

Also, why are you reporting bugs about the editor on the subforum for reporting site bugs??