| Display title | Arbitrary Headcount Limit |
| Default sort key | Arbitrary Headcount Limit |
| Page length (in bytes) | 87,270 |
| Namespace ID | 0 |
| Page ID | 64213 |
| Page content language | en - English |
| Page content model | wikitext |
| Indexing by robots | Allowed |
| Number of redirects to this page | 1 |
| Counted as a content page | Yes |
| Number of subpages of this page | 2 (0 redirects; 2 non-redirects) |
| Edit | Allow all users (infinite) |
| Move | Allow all users (infinite) |
| Delete | Allow all users (infinite) |
| Page creator | prefix>Import Bot |
| Date of page creation | 21:27, 1 November 2013 |
| Latest editor | Robkelk (talk | contribs) |
| Date of latest edit | 22:07, 20 September 2021 |
| Total number of edits | 24 |
| Recent number of edits (within past 180 days) | 0 |
| Recent number of distinct authors | 0 |
| Transcluded templates (6) | Templates used on this page:
|
Description | Content |
Article description: (description)
This attribute controls the content of the description and og:description elements. | Trope common in Real Time Strategy games, in which the overall number of units or the count of a particular powerful, but not unique unit are limited by assigning a completely arbitrary Cap to them. This limit is often far lower than what the resources available or the technical limits of the game engine could allow. Particularly ridiculous when the rule can be broken through scenario design or using a perfectly legitimate game feature. Most often implemented as a way to enforce game balance. It can also be a matter of resources; each unit requires not just rendering power but AI, collision, and other intangibles. This can be partially justified by representing the High Command's reluctance to commit too many resources into one battle when you- in theory- have more than enough resources, though this justification does not work as well when you are fighting THE climatic battle and yet there are only so many units you can deploy. |