Hot answers tagged

6

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 ...


5

When I know exactly the question of which the question is a duplicate, I usually paste the URL of the other question in the text field: And if finds it right away.


5

Yes, this is a bug. Yes, the involving parties are aware of it. However, it is a rather insignificant bug. As such, it is fairly low on the priority order. That said, this is not a problem specific to Game Dev Stack Exchange; While it may seem easy to fix, all you can do is raise the concern. However, you would not raise the concern, here. You would raise ...


3

If you look at the "input-area" CSS, there is a missing image: background: #000 url("//cdn.sstatic.net/gamedev/img/bg-notify.png") repeat scroll 0% 0%; Which makes the background of the input area ridiculously bright.


3

Yes, that shouldn't happen, and will be fixed next time we deploy.


2

The Firefox extension "Facebook Container" causes this behavior. So there's no issue with the site itself, I don't think.


2

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 ...


2

This is true for the whole SE network and the issue has already been discussed several times. A couple instances: Should the 24-hour timeout apply to bounties awarded for “exemplary answer”? Should we still have to wait the 24 hours if the Bounty reason is 'Reward Existing Answer'? The rationale behind the waiting period is to avoid users from easily ...


2

I changed both the question scores and section headers to have a much lighter font color; the fix will be pushed out in the next few hours. Sorry for the delay on this.


2

This has been fixed and will go out in rev. 1340.


1

I think this covers it. I know it's a link-only answer, BUT it is to stack exchange. So if THAT link is dead... What is the story of Jeff Atwood and the pluralization 'Bug'? :)


1

The core functionality of the Edit button has not changed, and you can make tag-only edits within reason. I have previously encountered situations where I only wished to change a tag, but the edit was "too minimal". That said, I was able to submit an edit to a question where I only removed the unityscript tag1. I was required to submit a manual edit ...


1

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 earlier &...


1

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 :)


1

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.


Only top voted, non community-wiki answers of a minimum length are eligible