I know these haven't been working for a while reave and steve, but was wondering if it's something thats a simple fix or if it's a thing with the forum theme, but I thing they're useful to have so applicants can see at a glance if it's a yay or nay.

Besides the fact that it stopped working 100% of the time for some odd reason, it's a better idea in theory than it is in practice. Every time you edited a post (and this has to be done for the formal accept/deny/trials thread marker), it took the new colored 'accept' and 'deny' used in the post(s) and substituted color code in again. (Just the way substitution works, since it's technically the same string as before just surrounded by color tags.) Basically, it makes a mess of the post with 'accept' and 'deny' surrounded by several nested red/green color tags. You won't see it in a normal view of the post (as outer nested color codes take precedence over each preceding inner one), but a glance at the 'Edit Post' box will show the mess they make.


All you should do now instead is just color /accept and /deny manually when you write it. It's easy enough to do and saves a hell of a lot of post cleanup hassle. There's a red and a green built-in. If you want to use the bright green, it's color code lime.



For /accept, you'd type:

Code:

[color=lime][b]/accept[/b][/color]

For /deny, you'd type:

Code:

[color=red][b]/deny[b][/color]

You'll notice I am also using the b and /b tags too. I always use those BOLD tags whenever I color text. You don't have to, but I think it makes it stand out even more.

Shit. I just had to make edits to that above post and the shit is already happening. Ugh.


The substitution string must be wrong somewhere, Reave, since I shouldn't be seeing any tags in the normal post view.

I see what your taking about Steve, it keeps replying itself, clutters the post, and annoying when editing. Removed the word censoring.

The closing bold tag on the deny substitution string needs a slash. That's what's wrong with the substitution text.