paradise-lost Sunday 10 October 2021

39 messages5 people

Isshaq02:30
When do you guys think the update is roughly coming? I’m planning on starting an aether survival world but if the update is coming soon I’d rather wait
Jack PapelTeam02:31
It's currently projected for November
Isshaq02:31
Cool
If I create a world with the aether reborn mod and then update it with the mod’s update will animals and dungeons be added to my world or would it likely cause corruption?(edited)
Jack PapelTeam02:34
We're planning to not cause any corruption
sunsette02:35
you should planning to cause bofa
Isshaq02:35
Sounds good, it’s also awesome to hear you guys are still at work on this thing I think it’s a great mod for anyone wanting to experience the aether and not use backports for 1.12.2
Jack PapelTeam02:36
Thanks :)
ColdFlame5318:03
Unfortunately i had to remove this mod until update because of the modded fuels issue :/ haha glad its getting fixed possibly in November though ☺️
sunsette18:45
Fuels?
AzzyypaarasTeam18:46
Replying tosunsetteFuels?
something something we did hackery to add more furnace fuels when there was a registry
May or may not be CDA's fault
sunsette18:46
wait why’s that an issue
is there not a registry anymore ?
AzzyypaarasTeam18:46
I am going to preemptively assume it is 😎
Ok so basically, furnace fuels are hardcoded
Fabric added a workaround for that through a registry
We either did not know there was a registry, or cda moved us out of using it when he went on his "NO MORE FABRIC API :spunchbob:" spree, so we added fuels via mixin
This breaks the registry, so any mod that adds fuels through it fails to do so when AR is installed
sunsette18:48
no more fabric api vine boom
AzzyypaarasTeam18:48
Replying tosunsetteno more fabric api vine boom
buwoop sound effect #1
sunsette18:49
why is it that fabric api no more
AzzyypaarasTeam18:49
Oh no, fabric api is v ery more
But there was a period where that was not the case
sunsette18:49
Very more let’s go
A
AzzyypaarasTeam18:49
See, CDA was at one point fixated on getting this ported to forge so it could run on both modloaders
18:50
I should have shut that idea down the moment I noticed him going for it, but I did not
- 👀1
Resulting in the refactor wars of 1997
I ended up digging into him with like, three paragraph of why doing that was a bad idea, and that was the end of that
sunsette18:53
yeah uh isn’t that like an absurd amount of work to maintain
AzzyypaarasTeam18:54
Replying tosunsetteyeah uh isn’t that like an absurd amount of work to maintain
Yes and no
If you do it properly and plan for it from teh beginning, there are ways to set things up so that one codebase can be compiled for both modloaders
However, there is one big issue with this
Even if you can run on both modloaders, your libraries almost certainly cannot, thus you would need to do everything in house
And I don't mean libraries as in "oh we have one that helps with rendering" no no, I mean you can't even use the fabric/forge api
Now I am not sure if you have ever looked, but AR currently uses like, nine different libraries not including FAPI
sunsette18:55
lol
AzzyypaarasTeam18:56
And that number is likely to go up, it is much more common for libraries to be added than removed
Only case where the second thing really happens is if a library is irreparably breaks or if its functions get merged into FAPI itself, both very rare things.