A remake of YOSBR for balatro.
This mod is mostly for modpack developers. The average user won't care about it.
https://github.com/WilsontheWolf/yosbr-balatro
Requires lovely
#YOSBR Balatro
vast hedge
wicked grove
amazing
jovial tendon
incredible
vast hedge
Figured @fervent olive @next knot might want to know about this
jovial tendon
might need this actually
fervent olive
A remake of [YOSBR](https://modrinth.com/mod/yosbr) for balatro.
This mod is mo...
ayy, exactly what I was hoping for
fervent olive
A remake of [YOSBR](https://modrinth.com/mod/yosbr) for balatro.
This mod is mo...
one issue though, I only distrubute the Mods folder, so having the config in the root of my Balatro appdata folder wouldn't really work
I don't have a fancy installer like Dim
vast hedge
hmm
fervent olive
his supports my modpack, but I like distrubting releases like I do
vast hedge
honestly I would distribute a zip with the mods and yosbr folder and then getting users to just unzip it in the main folder
but I guess I could make it try loading files from some folder in mods
fervent olive
that'd be helpful for me, but I get if you don't wanna do that. I just think having a Mods.zip that people can unzip too/as their mod folder is the most user friendly way to do it
Basically YOSBR just acting as another mod, which I can host my own version of that includes the configs
I want would be ideal
vast hedge
you should be able to edit this line https://github.com/WilsontheWolf/yosbr-balatro/blob/master/yosbr.lua#L43 to local succ, err = pcall(recursiveCopy, "Mods/yosbr-config", "") or something I think
I don't quite like putting my stuff in the mods folder by default, as its much fuller for normal mods and has special behaviour by lovely and smods, and i can't reliably get my own mod folder for a config file in it
fervent olive
That makes sense. And as long as I can trivially change it on my end, then it's not an issue. And it should be easy enough for me to test by just wiping the actual config file of the mod in question and seeing if it changes back to my defaults instead of the mod defaults
For me the simplicity of just distributing a mods folder, both for me and the user is very appealing. All I have to do to make a release is zip the mods folder from my local updated Coonies-Mod-Pack/Mods
vast hedge
makes sense
you should just be able to zip both the mods and yosbr folders together and just get the user to drop them in the balatro folder
fervent olive
That adds enough complexity that continuing to maintain forks of mods with edited config files would be preferable
It's not that it's a hard install process, it just adds a ton of extra room for user error
Plus it'd make yosbr more transparently optional, and the whole gimmick of my modpack is that by default it's my own exact modding setup
next knot
I will need to read into this for some time after work, amazing stuff at a glance
fervent olive
you should be able to edit this line <https://github.com/WilsontheWolf/yosbr-bal...
I tried this, but it's doing... nothing. The mod loads, but the config file I'm testing it with isn't replaced, and there's no errors I can see in the console or anything
fervent olive
I meant that
I deleted the one I was testing with
The new one generated is from the mod's defaults, not the one I put in Mods/yosbr-config/config/[mod].jkr
fervent olive
vast hedge
it's working for me
if it logged anything it should be really early like before most of the lovely patch logs
fervent olive
huh weird. Maybe the mod I'm testing with does something weird. I noticed the config file repopulates early in the loading process
vast hedge
specifically after the main.lua patch and before any others
fervent olive
yeah, none of the logs from the times I've ran it mention yosbr at all
vast hedge
it shouldn't log anything if it didn't error
add print("[YOSBR]", oldPath) to line 10 in the mod and then run it
fervent olive
It didn't log anything even when I tried changing the way I wrote the path. With a leading "/" and even with a leading "." before it
fervent olive
add `print("[YOSBR]", oldPath)` to line 10 in the mod and then run it
will do
fervent olive
add `print("[YOSBR]", oldPath)` to line 10 in the mod and then run it
but... it still didn't work
I deleted Balatro/config/ceres.jkr before running, and it still populated with the defaults in the Mods/Ceres folder, not the ones there
I know the ceres.jkr file is valid because it's the one I was using before with the mod
wait nevermind I guess
i dtupidly forgot to check the actual file
which did get copied
Did something break steamodded config or something?
I know I haven't been getting the stuff for perk cards with this config file
vast hedge
Not sure
Try deleting the file and the yosbr copy, letting the mod generate it for itslef then change the config in the ui and then exit to the title screen and then copy the config to yosbr
fervent olive
Yeah, it seems to work now
fervent olive
Try deleting the file and the yosbr copy, letting the mod generate it for itslef...
The old ceres.jkr mut have been broken, but for some reason only visually?
coarse rover
A remake of [YOSBR](https://modrinth.com/mod/yosbr) for balatro.
This mod is mo...
ayy, minecraft mod in balatro :o
next knot
I see why this exist now. Wish this will not be needed someday though
fervent olive
I see why this exist now. Wish this will not be needed someday though
kinda curious what you mean here. The function being built in to smodded?
next knot
Yeah if smods can handle configs more elegantly then the mod won't even exist
fervent olive
yeah, true
tbh it kinda just needs to build something similar in imo
where we can provide config file defaults for mods in the mods folder
next knot
If the configs are already there, will they be replaced by YOSBR?
fervent olive
nah, they won't