
Modrinth · Minecraft mod
MEOWS
my existing options will survive (default files)
Quick answer
Which MEOWS release matches 26.1?
MEOWS 0.0.1 targets 26.1, 26.1.1, 26.1.2 with Fabric. Installation on the client is optional. Installation on the dedicated server is optional. All 1 required mods have matching files.
Where it goes
Is MEOWS required on the client, server, or both?
Installation on the client is optional. Installation on the dedicated server is optional.
The source marks this as usable on both the client and server.
What else does MEOWS 0.0.1 need?
0.0.1 on 26.1. Every mod below is checked against that same setup.
Install Fabric API first. We found matching files for this game-version and loader setup.
We only count dependency files that match this setup. A file for another loader does not fill the gap.
Before you install it
Add MEOWS without breaking your instance.
Built for MEOWS 0.0.1 on 26.1. Pick another file and the loader, install side or required mods may change.
- 01
Stick to this file
Use 0.0.1. It targets 26.1, 26.1.1, 26.1.2 with Fabric; another release may have different loader, side or dependency requirements.
- 02
Bring the mods it needs
Install Fabric API first. We found matching files for this game-version and loader setup.
- 03
Put it on the correct side
Installation on the client is optional. Installation on the dedicated server is optional.
- 04
Pick the file you checked
Use the “Get this file” button beside 0.0.1. It opens that exact file at the source.
About this project
What does MEOWS add?
MEOWS
my existing options will survive
What?
Similar to YOSBR
or Configured Defaults, this mod provides a way to copy default game
files when Minecraft is started.
This is useful for mod pack creators who need to include configuration files but don't want to reset user changes after
every update.
Different from the aforementioned mods, MEOWS implements an "actions" system, in which certain actions can be performed
during startup, such as overwriting or deleting specified files. Actions will only run once.
How?
Every file in the defaults directory will be copied to their relevant places in the game's root directory. For
example, .minecraft/defaults/options.txt will be copied to .minecraft/options.txt if the file doesn't already exist.
The mod can be configured from the config/meows/config.json file. This includes the current version of the default
files (for actions), and the actions to perform per each version. To use MEOWS like YOSBR or Configured Defaults, these
options can be ignored.
Actions are stored as an array of objects, each containing an array of files to overwrite or delete and the relevant
version. Here's an example that will overwrite the options.txt file:
{
"version": 2,
"actions": [
{
"version": 2,
"overwrite": [
"options.txt"
]
}
]
}
When the game is started, MEOWS will perform these actions if it hasn't already. The local MEOWS version will then be
updated so these actions cannot be performed again.
For overwrite actions, the file must have a corresponding file located in the defaults directory.
{
"version": 3,
"actions": [
{
"version": 3,
"delete": [
"options.txt"
]
},
{
"version": 2,
"overwrite": [
"options.txt"
]
}
]
}
In this example, the top-most action will take precedence. options.txt will be deleted, despite being overwritten in
the previous version.
Note that, if the options.txt file is still included in the defaults directory, it will be copied if non-existent
when the game is next started as actions are only processed once.
Why?
From my experience maintaining mod packs, I've found that similar mods are lacking in one crucial way: how could a mod
pack author control file changes? After all, they only copy files if they don't already exist, meaning that major
configuration file changes or updating files that have already been generated are impossible. MEOWS solves this issue
with its actions system, providing the method of performing one-time operations on files.
FAQ
Will this be ported to more mod loaders?
In the future, probably.
Will this be ported to more Minecraft versions?
In the future, probably.
Why does this use preLaunch rather than serving as a language provider on Fabric?
Ideally, this mod should be absolutely effortless to maintain. As such, I opted for the "right" ways when it came to
many architectural decisions, notably avoiding the hacky language provider method other similar mods use in order to run
as soon as possible. This does mean that some other mods might create files before MEOWS is able to copy their defaults.
However, I've found that these cases are uncommon enough to where it's not much of an issue.
Project description from Modrinth.
Pick your setup
MEOWS by Minecraft version and loader
Choose the version and loader you play, then open the matching release.
26.2
1 loader build26.1.2
1 loader build26.1.1
1 loader build26.1
1 loader buildCheck the dependencies, then try the file in a copied instance before changing a world you care about.
Recent files
MEOWS versions and loaders
0.0.1
meows-0.0.1.jar
9 May 2026
Looking for an older file? The official Modrinth project page is in Resources.