@Fulgrim-Turbulent @Bault Some very useful markdown text formatting options are missing, like color & tables. I assume this is just not yet incorporated, but wanted to make sure this is on your radar. Personally, I prefer markdown, but I also like %(#FF0000)[changing font color] for emphasis. I | also | like | using | tables | for | organization |------|------------|----------|--------------|--------------|----------|-----------------------| but | these | don't | work | correctly | at | all I have tried just about every possible way I have seen tables implemented in markdown, and it just looks like you either haven't merged in a tablulation plugin, or haven't written one yet. While I don't hate this code block I typically prefer this one Edit: Hrm, hadn't noticed you used both types of code block, just your implementation looks weird. Single back tick giving monospace font w/ no code block box feels weird & triple giving an inappropriately wide code block box is very odd. I usually expect to see the ultra wide code box w/ the single back tick, while the triple back tick gives a relatively tight code block w/ syntax highlighting (when tagging the fence w/ language, usually). I have also noticed that you can't tag a user using @{username} properly, at least it doesn't look like it on our end. I know I really like that I can normally use this to attribute a quote snippet, and in most implementations also provide a link back to the parent post of the quote as well as a direct link from the @{username} tag to the user's profile. I just found the problem & this is aggravating as hell. If I type a user's exact tagged username id properly, I still have to take my hands off the keyboard to click on their name in the popup box way off to the side. Hopefully this is just due to not adding in the check to see if the exact @{username} string we typed is a valid user & fixing this is on the schedule. @novemsol said in [missing markdown formatting options](/path_2_posts/1): >This is a quote snippet Which is also not working; but again something that I assume is on your feature list. At least I hope so, as this is really core functionality for a forum. --------------------------------------------------------------------------------------------------------------- I hadn't checked for a division line yet, but it appears that hasn't been implemented yet either. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- There is another feature of your markdown implementation that absolutely frustrates the hell out of me, which is removing our inline formatting tags & replacing them w/ the altered text if we reopen the post in the editor. That is absolutely going to piss off anyone that tries to make any kind of guide for other players for publication on the forum. Leave the formatting tags in place please; there is absolutely no reason to strip those tags every time a post is published if you want forum users to actually use the forum for publishing player guides once the game goes live. You are early enough now that it isn't a big deal yet, as there isn't any game yet. But once there is a game, veteran players will want to use Spectrum to help give guidance to other players & you already have the beginnings of the best tool in the industry to do that, especially as this is planned to be accessible in & out of game. If this isn't on your radar, it really, really should be.