confluence:enchantable/repeaterA tag in a mod's own namespace: its internal classification, used by its own recipes.
The four counts above are corpus-wide and were computed once, across every extraction. The table below is what this database holds — a member whose mod is not loaded is listed and not linked.
| Item | Identifier | |
|---|---|---|
| Adamantite Repeater | confluence:adamantite_repeater | |
| Chlorophyte Repeater | confluence:chlorophyte_repeater | |
| Cobalt Repeater | confluence:cobalt_repeater | |
| Hallowed Repeater | confluence:hallowed_repeater | |
| Mythril Repeater | confluence:mythril_repeater | |
| Orichalcum Repeater | confluence:orichalcum_repeater | |
| Palladium Repeater | confluence:palladium_repeater | |
| Stake Launcher | confluence:stake_launcher | |
| Titanium Repeater | confluence:titanium_repeater |
None in the corpus.
Read out of data/<ns>/tags/** in each JAR. Tag
membership is a fact in a data file; whether two mods actually work together is not
something a tag can promise on its own.