create_dd:blueprintsA 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 | |
|---|---|---|
| Black Blueprint Block | create_dd:black_blueprint_block | |
| Blueprint Block | create_dd:blueprint_block | |
| Brown Blueprint Block | create_dd:brown_blueprint_block | |
| Cyan Blueprint Block | create_dd:cyan_blueprint_block | |
| Gray Blueprint Block | create_dd:gray_blueprint_block | |
| Green Blueprint Block | create_dd:green_blueprint_block | |
| Light Blueprint Block | create_dd:light_blueprint_block | |
| Light Gray Blueprint Block | create_dd:light_gray_blueprint_block | |
| Lime Blueprint Block | create_dd:lime_blueprint_block | |
| Magenta Blueprint Block | create_dd:magenta_blueprint_block | |
| Orange Blueprint Block | create_dd:orange_blueprint_block | |
| Pink Blueprint Block | create_dd:pink_blueprint_block | |
| Purple Blueprint Block | create_dd:purple_blueprint_block | |
| Red Blueprint Block | create_dd:red_blueprint_block | |
| White Blueprint Block | create_dd:white_blueprint_block | |
| Yellow Blueprint Block | create_dd:yellow_blueprint_block |
create_dd
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.