Closed ghost closed 2 years ago
Interesting, oki!
This is because I found that the sponge development team, in order to reduce the probability of crashing in the event of a Mixin conflict, had an optional test for the success of Mixin. I was just able to take advantage of this and go about fixing bugs in other Mods in a concurrent environment in a non-forced dependency way, regardless of whether they were installed or not.
No problems with memoryleakfix - a problem with Fastload: https://github.com/BumbleSoftware/Fastload I try other mods:)
FastLoad and quite a few Mod conflicts actually (
I don't really want to do compatibility with other optimised mods, it's difficult and most of the time pointless(((
Mixin has one disadvantage, Mixin cannot Mixin Mixin code. This is the biggest headache of all((((((
A official conflict list would be helpful - if you could add that to the description 👍 I would really love to use this mod, the question is at the end from what I benefit more 🤔 I can skip Fastload, but not sure about other mods.
The principle of FastLoad is to make a memory cache, but it is still questionable whether the thing supports concurrency.
I've actually been busy working on a new gun mod lately, so finding problems may be quick, but fixing bugs will be slower(((((((
I was testing it now with every mod (almost, just Chunky, DimThread (bug), Dynmap, Sneaky Tree Growing (bug), squaremap, website mod disabled). You made it working - as far as I can say 🥳
Only Fastload was buggy, everything else should work!
But I get a massive log spam - you may want to look into that: latest.log
Actually, error printing is an option (
The "C3H6N6O6" config file is empty. Is this normal?
This is normal, an empty file means that all options are default. This is the full configuration file:
# is a comment, the right side is the default value, generated with an empty file, that is, all default values are used.
# Parallelise entity enabled (false is enabled)
EntityDisabled = false
# Parallelise the block entity disable (false is enabled)
BlockEntityDisabled = false
#Whether to print entity reporting errors (true to print)
logEntityException = true
#Whether to print the block entity error (true to print)
logBlockEntityException = true
It's very different from other mods, and that's because I'm using the same library I used for my Java work. I've only actually got into Fabric Mod development in the last two years, but I've been working with Java for 8 years (
Looks much better now - I would say the mod is now usable on 1.19 😆 But I will wait a bit longer, until the log spam is fixed - oh, I was disconnecting right now from my server - after that the server was shutting down. Oki, still some work to do. Thanks for your awesome work 👍
By the way, next time you have a problem, please open a new Issue. a very long Issue is not very convenient((((
It was a good way to communicate - but it got wayyy too long, yes 😁
As far as I know, I am the only one who has used this method to enhance inter-mod compatibility.