-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Occultism recipes not showing for many rituals #90
Comments
I expect that this is because we're not on the latest jei/Occultism versions, because the latest jei is marked as 1.21.1 only. |
Just realized you meant it might be fixed in latest occultism which we can't use because of the available jei versions on 1.21... ignore me lol |
Mea culpa - I will release a version today that accepts older JEI. I missed that JEI restricted its latest versions to 1.21.1 See also klikli-dev/modonomicon#240 |
I am actually not sure, I fixed so many 1.21 bugs that I lost track. If the issue remains after updating to latest occultism (which should now be possible, the last holdback was modonomicon requiring a JEI alpha version, which I just fixed in v1.100 of modonomicon), please ping me and I will look into it again. I expect it should be fixed though as I recently tested something in ATM 10 which ditched JEI and is on latest occultism and there I did see the recipes in the book |
Hmm I will have to try with E10, in my local install I see the recipes " EDIT: I need to debug further but I get a lot of [21Aug2024 11:26:16.112] [Render thread/WARN] [Modonomicon/]: Recipe occultism:ritual/possess_warden (of type occultism:ritual) not found. in the E10 instance, that would explain why nothing shows here, but not sure why the recipe is not found |
@NielsPilgaard it looks like the recipes are not loaded (neither modonomicon nor jei find them). Is it possible that e.g. your kubejs script has an issue causing recipes not to be re-added after modification? |
@MuteTiefling please see above, what do you think? |
Certainly possible. I don't have easy access to a pc for testing, however. |
Alright, I'll give it a go if I can find time for it 👍 |
If not, I'll be able to in a couple days |
Testing with everything updated to 1.21.1. With our kubejs scripts as they exist in release, the issue persists. |
More specifically, I need to remove all recipe scripts for the issue to go away. The non recipe scripts are having no impact. |
@MuteTiefling is OccultismKubeJS present? |
@klikli-dev We do have occultism kubejs, yes We're also updated to 1.21.1 now and I'm still seeing the issue. |
What gets me is the seemingly random nature of affected recipes. It's very specific ones that don't show, but I don't see any correlation. Most of them are possession recipes. But then the silverfish horde and endermite recipes are fine. |
Although, those two do have an |
@MuteTiefling can you point me to where / how you modify the recipes? |
@klikli-dev our occultism specific recipes are here https://github.com/EnigmaticaModpacks/Enigmatica10/tree/master/kubejs/server_scripts/recipes/occultism But, removing them does not resolve the issue. I have to remove every single recipe altering script for your recipes to re-appear. Even if those scripts are unrelated to Occultism.
|
ok it reproduces if I put just your recipe script into my kubejs addon workspace. Maybe I can find out more! EDIT: No logs or similar. The only thing I found so far is that the recipes get "lost" pretty early in kubejs processing, because kube never even attempts to transform the json into a recipe object. |
I posted about the issue in the kubejs discord and asked them to give me directions on how to further diagnose this! |
I tested in a clean instance (Kubejs and Occulstim only) and this worked for me. ServerEvents.recipes((event) => {
event.forEachRecipe({ type: 'occultism:ritual' }, (r) => {
let recipe = r.json.asMap();
let recipe_id = r.getId();
if (recipe.spirit_max_age) {
if (recipe_id.includes('_trader')) {
// Remove decay from Traders
delete recipe.spirit_max_age;
} else {
// Reduce delay for all other spirits (weather/daytime rituals)
recipe.spirit_max_age = 10;
}
}
// Override default craft time for all recipes
recipe.duration = 20;
});
}); |
Found the common trace here: Tried re-adding the recipe myself as an interim solution and it doesn't like
|
And if I remove that value, the recipe loads without issue. |
That is a great find, although I am not sure why it happens, as the KubeJS people helped me set up that part. I will investigate, maybe it is outdated or we overlooked something |
I am not 100% sure but I think it might be fixed: I will push my changes for you to test @MuteTiefling Basically what I did was write a custom wrapper for the entity to sacrifice (THANK YOU for tracking that down as the common issue!). Weirdly someone in the Kube discord initially told me to remove my custom wrapper and use their component builder, but apparently it is somehow not compatible (any more?). But that is fine, if it works we keep it ! EDIT: release/v1.21.1-1.3.0 is building, once it is out it should maybe hopefully possibly fix it |
the component builder seems not to work the way we want This may fix EnigmaticaModpacks/Enigmatica10#90 Closes #5 because the server run now has an example for the entity to sacrifice
Awesome! I'll pop it in my test instance as soon as I can, thanks for your efforts! |
Woot! Working great! Thanks for the fix @klikli-dev, you're the best :D |
Thanks a lot for your help in this, this would sooner or later trip up a lot of mod pack devs and you did the legwork in tracing it down. |
Modpack Version
1.9
Describe your issue.
Many of the rituals in occultism are not showing in the occultism book or EMI.

Crash Report
No response
Latest Log
No response
Have you modified the modpack?
No
User Modifications
No response
Did the issue happen in singleplayer or on a server?
Singleplayer
Discord Username
calog3no
The text was updated successfully, but these errors were encountered: