nineMinecraft is a joke site.
nineMinecraft is in no way affiliated with Modrinth or 9minecraft. (And frankly, who wants to be affiliated with the latter?)
ModpackUtilities

ModpackUtilities

Mod

A (soon) multi-loader, multipurpose mod designed to address common annoyances when making a modpack!

Client Game MechanicsManagementUtility

3 downloads
0 followers

How do I configure this mod?

It's fairly simple, everything happens in one file, modpackutilities.txt (which can be found in /config/modpackutilities/modpackutilities.txt).
This is where you will type the keywords to configure the features' behaviour. Every keyword and command can be found in the category of their respective feature. Do note that the keyword order doesn't matter, as long as they are above any commands.

Copy files & folders

This serves the same function as other mods like Configured Defaults or Your Options Should Be Respected (YOSBR), with a little addition: you can overwrite whatever will be copied if you need to.
Let's look at an example. Let's say you added FancyMenu to your modpack after you released it. Instead of mod creating its own config, you can directly distribute yours!

  • Everything inside /config/modpackutilities/copy/config/fancymenu
  • Will be copied to /config/fancymenu

You can treat the copy folder as if it were the game's folder. This means that if you want to copy the options.txt file from Minecraft, you can. Pretty useful, right?

If you ever need to overwrite files, you can use the overwrite keyword anywhere inside the mod's config file. The function is self-explanatory: next time the game launches, everything inside the copy folder will be copied to its location in the game's folder, even if it already exists.
Keep in mind that this is destructive: the file that gets replaced will not be kept in any way.

Execute commands on world join

There are 4 keywords:

  • once: will execute the commands only the first time the player joins the world (works for each player in multiplayer).
  • everytime: will execute the commands each time the player joins the world (works for each player in multiplayer).
  • client: will execute the commands as if the player typed them in chat (beware of the player's permissions).
  • server: will execute the commands as if they were typed from the server's console, which means it has all permissions. Since the server can't use the @ parameter in a command to define a player, use @player instead to target the player joining the world.

Your attention please, put the commands after the keywords, not before, otherwise it won't work as intended.


Enjoy :)

Project members

Alix_x_X_or_Alixxx_please

Member


Technical information

License
ARR
Client side
required
Server side
unsupported
Project ID