[CLOSED] Species applications

Oops, I dropped lines on the above text!

I'm ok with this. This is a "human error" fix that'd be rejected by hand. I will see if I can at least get special characters rejected from being submitted as a name as it messes with the system (while everything else can have all the special characters it wants as it doesn't mess with the system.

Apparently naming a entry "null" and trying to edit it doesn't work

I checked and it works just fine, did you make sure to copy and paste the current password correctly when it gave it to you? (It's "2vjvf5tE2U")

On the edit god page you currently have placeholder text instead of info about editing the god

"4. The placeholders are not bugs and will be edited into actual words soon. "
I'll fix that before the next application move.

Box heck.

One of these is a bug while the others are just ok, aka it's the user's choice to do the thing and it's working as intended, the user just is doing something strange but not harmful. I'll fix up the bugs on this one.

What do you mean "too big"

I'll see if I can get applications to be rejected if any entries are unreasonably huge.

First off...

I don't think [Name of Special Trait] is synonymous for [Last Name] (thankfully, it didn't appear as if it autofilled the email anywhere so it might just be Firefox BUT STILL)

Alas this seems to be a baffling firefox issue. It thinks "specialname" = Last Name, but for whatever reason doesn't think "name" = Name which is really weird! You'd think it'd want to autofill name while it was at it. If it becomes a major issue I will change specialname to something else.

NOPE WAIT THERE'S AN ACTUAL BUG. IF YOU HAVE IT AUTOFILL A NAME WHEN YOU SUBMIT THE APP IT AUTOMATICALLY FAILS

This is actually because you do end up giving your email to the site, even though you don't see it by auto filling. Basically the application got flagged as a bot because it gave the site an email when it wasn't suppose to, or be able to.

Actual bugs and/or potential bugs found:
[*]Tags don't check if they close correctly. So you could make the whole application italicised. Or purple. Or both, if it so behoves you.

This is a bug. It will likely be fixed by hand if I can't figure out an automatic system.

[*]You can use unicode sequences like > to get a > symbol in there, or the correct code for any character really. This is probably an intended mechanism, but just letting you know.

Yep, intended.

[*]I don't know which all colors are defined, but it's neither anything (with hexcode) or CSS/HTML list. Again, restricting the colorset probably makes sense; no need for 16 million plus ones.

Yep the colorset is currently restricted to red, blue, green, yellow, purple. I'll put that in a guide when things are spruced up as the limited color pallet can be confusing.

[*]Quotes and everything inside of them disappear in some sections on editing. So if you have a trait named like "test", when you first submit it, it will be fine. If you edit it and don't re-type the quotes, the entire trait will vanish.

Oh that is...weird. I'll see if I can fix that. I'll pm you on discord if I need a walkthrough on how to break it.

[*]HTML tags directly and indirectly don't work. So I sadly couldn't make a trait who's description was a link to the RickRoll video.

This will also be in the guide. Not all tags work, only the basic ones like br, b, i, etc.



=========

Thank you for all of the reports! I'm going to get things fixed up and then open another application section to be tested!