This is a community wiki post anyone can edit.
Its purpose is to compile a list of Game Dev SE posts that would significantly benefit from MathJax/LaTeX markup, as part of the use-case argument for enabling MathJax here.
We need a decent body of evidence that MathJax would be worthwhile. RPG.SE and CodeReview responded by gathering a list of posts that ...
Games are interactive, so questions about them are often about interactivity. Stack Snippets allow interactive demonstrations.
Currently, when I write about something interactive (like splashy waves, brushable hair or mouse following), I tend to post a bunch of pictures (often GIFs of my cursor poking things), followed by the code I used to ...
After some further though I don't really see any reason we would not want these. Yes, you can make an argument that it will "encourage" code dumps, but we don't allow those, so the existing moderation venues should handle that just fine.
If anything, perhaps the quality of code dump questions will improve slightly (since the snippet won't run if the code is ...
As you may be able to see, the link colors on Meta.GameDevelopment have been updated. They have been reverted to the standard Meta link colors.
Update July 24, 2017
Chat and GD.SE link colors have been updated and will be updated once production builds out. Once production build, I'll update the post's status.
Update July 26, 2017
Production has been ...
We're going ahead and enabling this, as you've shown plenty of examples of cases where it'd be useful.
As requested, the inline delimiters will be changed to \$ ... \$, and the block-level delimiters are $$...$$ and [...] (which are the defaults, and can't be changed).
Fixed posts broken by this:
Unreal Engine 4.15 Error C++ | ERROR: UBT ERROR: Failed to ...
That's because parallax-scrolling didn't exist before. It does now. And, parallaxscrolling has been merged into it, so anyone trying to use that non-dash-non-sense will be converted to the dash-tastic parallax-scrolling.
This is probably a server-side issue. On StackOverflow, code snippets in questions or answers have a special prettyprint class, eg. <pre class="lang-c prettyprint"> ... </pre> whereas on Gamedev the code snippets are served as <pre><code> ... </code></pre>.
I found this Protection banner missing when I don't have enough rep to answer; closed and locked banners appear in wrong spot, so it seems it's not specific to this stack, but a sidewide problem.
It seems the intended behaviour is to show protected at the bottom where the answerbox is to user that have not enough rep, and show it at the top to users who ...
Thanks for reporting this. Basically, for obvious reasons when you go to that page we filter out any flags about you. No: those 7 weren't for you! However, there was a bug (to do with database nulls) which meant that this filter was also excluding posts by deleted users.
However, the count in the page-header is much simpler and doesn't apply this check - ...
Well it wasn't working for me at first, but after I went to https://sstatic.net/ it gave me that Chrome warning just like in your picture, and after I clicked proceed, it started working for me. If you read the error it says it's a server problem.
Just like with Self Signed SSL certificates, it is most likely an anti fishing protection. (Gone wrong in this ...
The question you're asking about is protected, which means it cannot be answered by users who have less than 10 reputation on the site. The 100-point association bonus doesn't count, so as of right now you'd need to earn 9 reputation on the Game Development site
Questions are generally protected when they become popular and as a result start to attract low-...
We just did a major revamp of how badges are awarded behind the scenes to drastically reduce the load on SQL Server. It now takes advantage of some pre-compute work we're doing to track badge progress in the profile.
However, I screwed up 2 queries, specifically the text names of the badges that prevent duplicate awarding. I was thinking to myself ...
I'm pretty sure that this was fixed a few weeks ago; apologies for not seeing this report sooner.
Unless you've seen more instances of this issue... and if so, please just keep it to yourself (kidding :)
That old edits make questions come up in the reopen queue is by design. If a question has been edited after being closed, it is now eligible for reopening.
In regards to questions showing up multiple times - this has been fixed.
I just went ahead and removed the generated/generation tags from most questions in lieu of procedural-generation. In the cases where prodecural generation didn't make sense I just removed the tag since it wasn't really descriptive enough.