We certainly don't need a tag for hats.
Although cosmetics-customization could do the trick, seeing the scope of the answers, it's not only used for that as it could be used as trophies and/or visual achievement as well.
Even though navigation-mesh is more wordy and describe more exactly what it is, users will not be confused by the term navmesh as it's very commonly used.
I suggest we make navigation-mesh a synonym of navmesh because navmesh is shorter to write, has no hyphen, and is sooo much cooler :P
No, we don't need the free tag.
In my opinion, this is a meta tag which does not inform at all about the topic of the question.
You can't be an expert in free.
The vast majority of the 24 questions with this tag are closed. This is associated to the fact that questions about 'free' stuff are most of the time off-topic/too broad for this site. (E.g. ...
I'd follow this rule:
If the question contains C# code, tag it C#
If the question lacks code, but asks about scripting a feature in (a recent or unspecified version of) Unity, tag it C#
If the question asks about solving non-scripting problems in Unity (eg scene setup, asset management), do not tag it C#
In the first two points, even if the C# language ...
I suggest we make forces a tag synonym of physics because...
... the concept of forces being a subset of physics
... half of the questions tagged with forces are also tagged with physics
... someone is rarely expert in forces, they're more often expert in physics.
This makes it more of a meta tag, in my humble opinion.
I am of the opinion that these tags should be blacklisted.
You would not be able to use the tags by themselves to adequately tag a question, unless the question was only specific to general context. Such context would probably be to broad for our scope.
To more accurately use the tags, you would have to also use the more specific tag to provide context, in ...
I think update is not clear enough and should be deleted.
However, while doing so, the questions tagged with update regarding the topic game update loop pattern could be tagged with game-loop instead, while those with the topic deploy game software updates to players could be retagged with deployment. I feel the other two topics you've covered are using ...
In reference to Josh Petrie's comment, I think entity is silly.
When referring to an entity in the context of an Entity-Component-System architecture, for instance, the role of the Entity is quite agreed upon.
So in the context of the tags entity-system and entity-component, we have a good idea of what the entity there will be used for.
But when we use ...
There is a fundamental difference, but I would like to explore if the difference is considerable enough to warrant a separate tag. It is clear that very few of the questions tagged with hack are on topic, as most have already been closed, and the few that remain present a suitable alternative.
While I agree with the observations made by Byte56, I see a lot ...
I think microtransactions and IAP are two different concepts:
microtransactions deals with the business model
iap deals with an implementation of the business model.
You can very well create a game that has no in-app-purchase but has microtransactions (what if you need to go on the website of the MMO to do the transaction), and you can have in-app ...
Yes, experience should be blacklisted. The name is not specific enough about how it should be used, and even if it were to be used for "experience points", it would be too specific and could be covered by the other tags you mentioned, or by game-design if appropriate.