ammaarreshi / Generals-Mac-iOS-iPad
Command & Conquer Generals: Zero Hour running natively on macOS, iPhone & iPad — real engine (EA GPL v3 source, via GeneralsX), DXVK/MoltenVK renderer, RTS touch controls. No game assets included.
- Stars
- 1,733 stars
- Forks
- 283 forks
- Language
- C++
- License
- OTHER
- Created
- Jul 4, 2026
- Last push
- Jul 5, 2026
- Updated
- Nov 12, 2026
Admitted to the Repository Index on Nov 12, 2026: 1,733 stars on 2026-11-12.
Star History
133 days recorded, Jul 4, 2026 – Nov 13, 2026 (UTC). Net change +1,734 stars.
The star count of each day is the latest count minus the net stars of the later days.
Add this Star History to a README
The images follow the light or dark theme of the page that shows them, and update every hour.
Add ?theme=light or ?theme=dark
to the chart address to keep one theme.
Star History chart
[](https://awesomerepos.com/ammaarreshi/Generals-Mac-iOS-iPad) Badge
[](https://awesomerepos.com/ammaarreshi/Generals-Mac-iOS-iPad) Timeline
It gained stars on 117 of the 133 days recorded since Jul 4, 2026.
Its largest 7 days were Jul 4, 2026 to Jul 10, 2026: 1,396 stars.
In the 30 days to Nov 13, 2026 it got 67 stars, 12% more than in the 30 days before.
- Created on the Repository Host
- Reached 100 stars, on the day it was created
- +403 stars in one day
- Reached 500 stars, 1 day after it was created
- Largest star day recorded: +486 stars
- Latest push
- Reached 1,000 stars, 2 days after it was created
- +295 stars in one day
- Entered the Repository Index: 1,733 stars on 2026-11-12
The timeline comes from the creation date and the releases on the Repository Host, the Admission, the Star History, and the Observations. Star milestones show only when the Star History records the day. The list shows up to 5 stable releases from the latest 10 releases recorded. When none of them is stable, one item counts the pre-releases. On the chart of net stars each day, a solid line marks each recorded release.
Forks and pushes
From 2 Observations, Nov 13, 2026 – Nov 14, 2026. Forks +1. AwesomeRepos saw a new push on 0 of 1 days.
- Nov 14, 2026: no new push
A filled day: the last push time changed since the Observation before it.
Health facts
Measured facts in four separate dimensions, each with a date and a source. AwesomeRepos does not add them into one score. AwesomeRepos reads the weekly commits, the changelog, and the community files each week for the 5,000 visible repositories with the most stars and for each rising repository. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 1 task for the maintainers of ammaarreshi/Generals-Mac-iOS-iPad.
Improve the Health Facts of the GitHub repository ammaarreshi/Generals-Mac-iOS-iPad. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/ammaarreshi/Generals-Mac-iOS-iPad. A change to the repository can improve each of the item below. Each item gives the measured fact or score, and a task. 1. A release in the last 365 days Fact: No GitHub release (read on 2026-11-12). Rule: The newest published GitHub release (a pre-release counts; a draft does not) is 365 days old or less. A repository that publishes only tags, or only to a package registry, has no GitHub release. The release refresh reads the 10 newest releases after each push to the repository, and at least each 30 days. The index refresh reads the date of the last push each day. Task: Prepare a release, but do not publish it. Find the changes since the newest release, propose the next semantic version and the release notes, and ask me to publish the GitHub release. If nothing changed since the newest release, skip this item. If the project publishes only to a package registry, add a CI step that also makes a GitHub release for each version tag. Rules for this work: - Each file must be true for this project. Do not copy text that does not apply to it. - Do not choose a licence, a contact, or a release version for me. Ask me. - Do not publish a release, change a repository setting, or push to the default branch. Make the changes on a new branch. - Keep each change small, and run the checks of this repository before you finish. - At the end, list each item as DONE, SKIPPED (with the reason), or NEEDS A DECISION (with the question). AwesomeRepos reads these facts again in its next scan. The definitions of the checks: https://awesomerepos.com/health-facts
Maintenance
1 of 4 checks (2 without data)-
Yes: Not archived
GitHub does not mark the repository as archived. Source
-
No: A push in the last 90 days
Last push on 2026-07-05, 132 days ago. Source
-
No data: Commits in the last 13 weeks
No data: AwesomeRepos has not read the weekly commits.
-
No data: Commits in 26 or more of the last 52 weeks
No data: AwesomeRepos has not read the weekly commits.
Releases
0 of 3 checks (2 without data)-
No: A release in the last 365 days
No GitHub release (read on 2026-11-12). Source
-
No data: The newest release tag is a semantic version
No data: no release.
-
No data: A changelog file at the root
No data: AwesomeRepos has not scanned this repository.
Security practice
0 of 1 check (1 without data)-
No data: A security policy
No data: AwesomeRepos has not scanned this repository.
AwesomeRepos has not asked OpenSSF Scorecard about this repository.
Community files
1 of 3 checks (2 without data)-
Yes: A licence
GitHub finds a licence file, but cannot name the licence. Source
-
No data: A contributing guide
No data: AwesomeRepos has not scanned this repository.
-
No data: A code of conduct
No data: AwesomeRepos has not scanned this repository.
Observations
Latest Observation, Nov 14, 2026: 1,733 stars, 283 forks, last push Jul 5, 2026, not archived. One of 2 Observations since Nov 13, 2026.