Tags
Creators
Details
Licensed CC-BY-SA-4.0
Published 3 years ago
Updated 11 months ago
All versions
0.2.0
Release
Many More Banners v0.2.03 years ago 134
Compatibility
Minecraft: Java Edition
24w11a
24w10a
Platform
Data Pack
Changes
[0.2.0] - 2024-03-15
Added new banner patterns, and patterns are now categorised.
Added
- Curtains: A fancy curtain border.
- Diamonds: A 'Diamonds' playing card symbol.
- Hammer: An icon of a hammer.
- Revolution: An icon of a fist raised in a revolutionary pose.
- Ribs: A skeletal / rib-like border pattern.
- Shield: An icon of a shield.
- Tattered: A pattern reminiscent of a tattered banner.
- Trident: An icon of a trident.
Changed
- Data Pack version is now 35.
- Resource Pack version is now 29.
- Many patterns now require a Banner Pattern item to be used.
- This was done for future-proofing, as the loom was getting crowded.
- Patterns have been split in to 7 categories
- Base: No Banner Pattern required. For basic patterns and borders.
- Creeper: Requires 'Creeper Charge' Banner Pattern. For mob related patterns.
- Flower: Requires 'Flower Charge' Banner Pattern. For patterns related to nature and harmony.
- Globe: Requires 'Globe' Banner Pattern. For block and item related patterns.
- Thing: Requires 'Thing' Banner Pattern. For icon and miscellaneous patterns.
- Snout: Requires 'Snout' Banner Pattern. For patterns related to buildings or places.
- Skull: Requires 'Skull Charge' Banner Pattern. For patterns related to weapons, armour or accessories.
- See README.md for each pattern's category.
Fixed
- Removed stray pixel on the 'Peace' icon pattern.
- Removed excess pixels from the 'Fancy' border pattern.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| many-more-banners-v0.2.0-rp.zip | Required resource pack | 109.33 KiB |
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:Dv9hvreZ:J39ghI6s"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Dv9hvreZ:J39ghI6s"
}

