// readme

Carpet FGA Addition

Minecraft 1.21.1 adds the server-side resilientPlants rule for placing selected plants without normal survival support. Minecraft 1.21.1 also adds comparatorThroughBlocks, allowing comparators to read a container signal through configured blocks such as chains or pistons. It also adds the opt-in woodStonecuttingRecipes rule, allowing wood products to be crafted in the stonecutter with bidirectional wood conversion, log-to-stair/slab yields of 4/8, plank-to-stair/slab yields of 1/2, bamboo mosaics, boats, bamboo rafts, and server-authoritative bamboo input counts, with bamboo blocks, stripped bamboo blocks, and 9 bamboo accepted as equivalent bamboo inputs.

Carpet FGA Addition 是一个面向服务器的 Fabric Carpet 扩展，提供假人、掉落物、村民、命令兼容、生命显示和性能辅助功能。除特别说明外，功能默认关闭，通过 /carpet 规则启用。

支持版本

当前版本为 1.5.0，提供 Minecraft 1.16.5、1.17.1、1.18.2、1.19.2、1.19.4、1.20.1、1.20.4、1.20.6、1.21、1.21.1、1.21.4、1.21.5、1.21.8、1.21.10、1.21.11、26.1.2 和 26.2。

文档

全部支持版本提供虚空新区块生成，Minecraft 1.21-26.2 还提供可排队、重启执行的正常地形重生成和全空气区块清除功能

↑ The Undervalued Score +

How much a project earns versus how much attention it actually gets. Above 50 means the work is outrunning its audience. Recomputed nightly from commit velocity, contributor effort, issue resolution, fork utility, release cadence, and project maturity — divided by a logarithmic reach factor.

score  = signal / reach

signal = 0.25·commit_velocity   // commits in last 90 days (cap 30)
       + 0.20·contributor_work  // unique authors × velocity (cap 100)
       + 0.20·issue_resolution  // closed ÷ total issues
       + 0.20·fork_ratio        // forks ÷ stars (proxy for real usage)
       + 0.10·release_cadence   // releases in 90 days (cap 3)
       + age_bonus              // +0 to +0.30 after 6 months
       + homepage_bonus         // +0.05 if homepage is set

reach  = log₁₀(stars + watchers + 10)█
♥ The Health Score +

Is the project alive and maintained right now? A 0–100 pulse recomputed nightly from commit recency, rhythm, how fast issues close, and how quickly PRs get merged.

health = 0.35·recency       // days since last commit (90d decay)
       + 0.25·cadence       // commit rhythm consistency
       + 0.20·issue_health  // closed ÷ total issues
       + 0.20·pr_health     // merged ÷ total PRs█
◷ Health bands +

The colour and label on every card come straight from the health score.

Healthy   80 – 100   active, responsive, regular releases
Stable    60 – 79    maintained, steady, no alarms
Quiet     40 – 59    slowing down — watch this one
At Risk    0 – 39    going dark · candidate for rescue█
// Tags — what each label means +

Tags are independent behavioral signals computed nightly. A project can hold multiple at once. They drive the home page sections.

solo_builder      one person holds > 80% of commits (last 180d)
needs_contributors has open "help wanted" or "good first issue" labels
hidden_gem        < 100 stars · active in last 3 months · documented
legacy_hero       repo > 5 years old · committed this year
fork_magnet       forks/stars > 0.5 · used as template or dependency
release_machine   5+ releases in the last 90 days
under_pressure    > 10 open issues · ≤ 2 contributors · health ≥ 60
community_watch   watchers > stars · devs tracking before the public
community_hub     GitHub Discussions enabled · > 20 discussions
funded            maintainer has active funding channel█
★ Why rank against stars at all? +

Stars are an outcome, not effort. A project with 8 stars and daily commits is doing more interesting work than one coasting on 8k. We measure the building, then divide by the attention already received — so the genuinely undervalued rise to the top.

// stars   = lagging indicator
// commits = leading indicator
// we rank by the leading one█