All versions
2.0.0+neoforge-1.21.1
Release
Arcadia Prestige 2.0.0 (NeoForge 1.21.1)last week 42
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
Arcadia Prestige 2.0.0
Downloads
arcadia-prestige-forge-1.20.1-2.0.0.jar(forge-1.20.1)arcadia-prestige-neoforge-1.21.1-2.0.0.jar(neoforge-1.21.1)arcadia-prestige-neoforge-26.1.2-2.0.0.jar(neoforge-26.1.2)
Performance
- Cosmetic effects stop allocating their own shapes ten times a second — The crown, the halo, the orbit circles, the abyss well, the wings and the pentagram each built their shape table as a fresh array every time they drew, for every player wearing the effect, at ten draws a second. The tables describe shapes and never change, so they are built once now, and the pentagram reuses one set of vertex arrays instead of allocating three per draw.
Performances
- Les effets cosmétiques n'allouent plus leurs formes dix fois par seconde — La couronne, le halo, les cercles orbitaux, le puits abyssal, les ailes et le pentagramme construisaient chacun leur table de forme sous forme de tableau neuf à chaque dessin, pour chaque joueur portant l'effet, dix fois par seconde. Ces tables décrivent des formes et ne changent jamais : elles sont construites une seule fois, et le pentagramme réutilise un jeu de tableaux de sommets au lieu d'en allouer trois à chaque dessin.
Technical
- Hub opener dropped — The dashboard no longer registers a hub opener with the lib. The opener it registered was a call to the lib's own packet, and registering it made the lib believe the hub only existed when prestige was installed. The hub is the lib's.
Technique
- Ouverture du hub retirée — Le tableau de bord n'enregistre plus d'ouvreur de hub auprès de la lib. L'ouvreur enregistré était un appel au paquet de la lib elle-même, et l'enregistrer faisait croire à la lib que le hub n'existait qu'avec prestige installé. Le hub appartient à la lib.
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:bwtWF55T:cgNIDev2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bwtWF55T:cgNIDev2"
}

