Tags
Creators
Details
3.1.0
Compatibility
Changes
🇪🇸 Español
🗂️ Nuevo sistema de organización de hologramas
Se implementó un nuevo sistema que permite una mejor organización de los hologramas, especialmente en servidores que manejan una gran cantidad de ellos.
Ahora puedes crear subcarpetas o grupos para organizar los hologramas y moverlos fácilmente entre diferentes grupos.
📦 Mover múltiples hologramas a la vez
Puedes mover varios hologramas al mismo tiempo separando sus nombres por comas:
/holo group move holo1,holo2,holo3 spawn_group
También puedes mover varios hologramas nuevamente a la carpeta principal (root):
/holo group move holo1,holo2,holo3 root
🛡️ Borrado seguro de grupos
Si eliminas un grupo utilizando:
/holo group delete <grupo>
o:
/holo delete group <grupo>
los hologramas nunca serán eliminados.
Todos los hologramas pertenecientes a ese grupo serán trasladados automáticamente a la carpeta principal (root) y posteriormente la subcarpeta vacía será eliminada de forma segura.
🆕 Nuevos comandos
-
/holo group create <groupId>o/holo create group <groupId>Crea una nueva subcarpeta enholograms/<groupId>/. -
/holo group move <holo1,holo2,...> <targetGroup|root>Permite mover uno o varios hologramas a otro grupo o a la carpeta principal. -
/holo group delete <groupId>o/holo delete group <groupId>Elimina un grupo y mueve automáticamente todos sus hologramas a la raíz. -
/holo group listMuestra todos los grupos existentes y la cantidad de hologramas almacenados en cada uno. -
/holo group info <groupId>Muestra todos los hologramas almacenados dentro de un grupo.
🇬🇧 English
🗂️ New Hologram Organization System
A new system has been implemented to provide better hologram organization, especially for servers managing a large number of holograms.
You can now create subfolders or groups to keep holograms organized and easily move them between different groups.
📦 Move Multiple Holograms at Once
You can move multiple holograms at the same time by separating their names with commas:
/holo group move holo1,holo2,holo3 spawn_group
You can also move multiple holograms back to the main folder (root):
/holo group move holo1,holo2,holo3 root
🛡️ Safe Group Deletion
If you delete a group using:
/holo group delete <group>
or:
/holo delete group <group>
the holograms will never be deleted.
All holograms belonging to that group will automatically be moved back to the main folder (root), and the empty subfolder will then be safely removed.
🆕 New Commands
-
/holo group create <groupId>or/holo create group <groupId>Creates a new subfolder atholograms/<groupId>/. -
/holo group move <holo1,holo2,...> <targetGroup|root>Moves one or multiple holograms to another group or back to the main folder. -
/holo group delete <groupId>or/holo delete group <groupId>Deletes a group and automatically moves all of its holograms back to the root folder. -
/holo group listLists all existing groups and the number of holograms stored in each one. -
/holo group info <groupId>Displays all holograms stored inside the selected group.
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:v7Mdthjb:GsIhovsZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:v7Mdthjb:GsIhovsZ"
}

