The issue with Mystery Boxes can be fixed with Extra Machine Config, if you're fine with a dependency. Technically this is also an issue with the Golden Coconut because of the hat it can produce. Coupled with Automate you can get a bunch of those hats, which isn't intended but also has no effect other than wasting space. Otherwise that's a limitation of the way SDV is written and probably won't ever be fixed because it would require massive rewrites.
Edit: Investigating an issue with this currently, will edit again when I figure out what went wrong.
Edit #2: Figured out what's wrong, let the author of EMC know but not sure if they're gonna change the documentation. In the meantime I have an example on the validator site. My example also includes the Golden Coconut.
hi! i made a blacksmithing mod that also overhauled the geode crusher as part of the features, and with extensive help from the sdv discord's modding community, i was able to figure out the issue with mystery boxes :) if you'd like i can help you with that part of your mod! my discord is @altroquinine, and i'm also in the sdv server
I just downloaded this mod and it's not seeming to activate. Is there anything special I have to do to activate it, or should it activate on download? I'm not seeing any errors in SMAPI on load.
First of all, I wanted to thank you for creating this mod! I have a question, do the blue mystery boxes only produce bombs? I use SVE and some mods, could it be these mods' fault?
working on addressing this. mystery box contents are coded differently than artifact troves/coconuts/geodes, so the geode crusher seems to not be handling them well
I remember looking into this some time ago for my own reasons. The stickler with opening geodes was that they were seeded, meaning that if you opened them in a particular order, whether through Clint or the Crusher, you would always get the same results. When artifact troves and coconuts were added, they used the same mechanic. Essentially, everything was pre-rolled and it would just churn through the random numbers like going down a list. Like they used rng.next().
I haven't investigated 1.6 much, but it was made clear that a new RNG method was implemented and possibly the boxes use a different hook for progressing their RNG tables such that it triggers when Clint opens them but not when the table is read. If so, that would explain why the boxes will always give the same thing over and over.
The Stardew Predictor has boxes separate with their own table so there is some credence to this theory. Their github might give you some pointers. Other than that, it may be beyond the capability of Content Patcher to fix. Good luck!
Both my mistery boxes won't work with the crushers, wether I put them manually or in a chest with automate. The rest works fine. Is there anything missing on my end? Thanks for the awesome mod
27 comments
-
1
-
2
JumpOtherwise that's a limitation of the way SDV is written and probably won't ever be fixed because it would require massive rewrites.
Edit: Investigating an issue with this currently, will edit again when I figure out what went wrong.
Edit #2: Figured out what's wrong, let the author of EMC know but not sure if they're gonna change the documentation. In the meantime I have an example on the validator site. My example also includes the Golden Coconut.
I just downloaded this mod and it's not seeming to activate. Is there anything special I have to do to activate it, or should it activate on download? I'm not seeing any errors in SMAPI on load.
I have a question, do the blue mystery boxes only produce bombs? I use SVE and some mods, could it be these mods' fault?
I haven't investigated 1.6 much, but it was made clear that a new RNG method was implemented and possibly the boxes use a different hook for progressing their RNG tables such that it triggers when Clint opens them but not when the table is read. If so, that would explain why the boxes will always give the same thing over and over.
The Stardew Predictor has boxes separate with their own table so there is some credence to this theory. Their github might give you some pointers. Other than that, it may be beyond the capability of Content Patcher to fix. Good luck!
"Format": "2.0.0",
"Changes": [
{
"Action": "EditData",
"Target": "Data/Objects",
"Fields": {
"275": {
"ContextTags": null
},
},
"Action": "EditData",
"Target": "Data/Objects",
"Fields": {
"791": {
"ContextTags": ["color_yellow"]
},
},
"Action": "EditData",
"Target": "Data/Objects",
"Fields": {
"MysteryBox": {
"ContextTags": null
},
},
"Action": "EditData",
"Target": "Data/Objects",
"Fields": {
"GoldenMysteryBox": {
"ContextTags": ["color_yellow"]
},
},
},
]
}
Verification is available
-
1
-
2
Jump