FeatureCreep and Omnilook conflicts

[SuntannedDuck2]

Tested using 0.19.3 Loader of Legacy Fabric and Ornithe Gen 1 (it's what the installer generated using 0.15.0 Ornithe installer), using 1.13.2.

Mod Remapping API 1.27.3 or 1.29.0 (Legacy Fabric/Ornithe) and Fabricated Rift 1.3.0 (Legacy Fabric) and 1.3.1 (Ornithe 1.13.2) with OSL 0.16.3 and 0.18.0 (Gen 2 so not related in testing)

Tested using featurecreep-4.0AM18-1.13.2Rift.el9fc4.noarch.fpm.jar (latest build of FeatureCreep).

Crash report states Fabricated Rift errors with prelaunch errors, invocationtargetexception and other class errors, notfoundexception, illegalstateexception.

Source: https://www.curseforge.com/minecraft/mc-mods/featurecreep/files/all?page=1&pageSize=20&version=1.13.2&gameVersionTypeId=7500&showAlphaFiles=hide

Tested using omnilook-0.2.1.jar, states requires version 1.0.0-beta.7.3, any version between 1.3.0 (inclusive) and 1.12.2. (inclusive) or version 1.14 or later of Minecraft but only the wrong version is present 1.13.2

Source: https://modrinth.com/mod/omnilook/versions

Hadn't done testing with OptiFine, Modern Mixins and Tritium but they work now.

FeatureCreep is the newest 1.13.2 mod came across during testing.

I don't have hope in my testing and may have messed up builds disabled or active jar files in testing, so I'd say do as much thorough testing as can with what is available.

[thecatcore]

FeatureCreep relies on LaunchWrapper which we don't use, so a work around will have to be found.

Omnilook seems to have Fabric support for b1.7.3, 1.3-1.12 and 1.14+. As such it is recognized as a Fabric mod instead of a Rift one which is the main reason for the crash.

[SuntannedDuck2]

FeatureCreep relies on LaunchWrapper which we don't use, so a work around will have to be found.

Omnilook seems to have Fabric support for b1.7.3, 1.3-1.12 and 1.14+. As such it is recognized as a Fabric mod instead of a Rift one which is the main reason for the crash.

Makes sense. I think FeatureCreep only targets Forge 1.13.2 otherwise. But Launch Wrapper makes sense there.

Ah so Omnilook has Forge 1.13.2 instead but yeah no Legacy Fabric or Rift 1.13.2 makes sense, bit confusing to tell though (which at that point not really much point focusing on Rift 1.13.2 and a compatibility through Fabricated Rift either? it's too niche a use case and not really worth the effort) fair enough.

Do you have a working Rift 1.13 or 1.13.2 I struggle to get it running in the MultiMC/PolyMC/PrismMC launchers? Even my old modpacks 'that did work' don't as I think it wants to call the Rift GitHub source (also on my prior device as my hard drive crashes not sure even after that of the files were there when packaging the modpacks and as on a new device and trasnferring files is a pain with my old ones). But depends what's available in the Rift GitHub sources still, clearly people still make the odd Rift ports so things are available.

But it can't due to it's current status (when it shouldn't need to). Mojang launcher maybe I can with the ASM files I backed up and placing them in my launcher setup but otherwise the other launchers (even with at least I thought in the past the necessary files) still tries to seek out the source.

I have a Rift 1.13 + Datapacks let's play finished (not 1.13.2 yet as didn't see much point with those mods as much as the ones with more content to them at least with the focus at the time years ago I recorded and only in the last 1 to 2 years editing them) so I don't need to like record anything of them. But just so I can know Rift works at all outside of me testing the mods inside Fabricated Rift Legacy Fabric/Ornithe all the time (even if yes 1.13.2 currently).

Just when a mod is tagged for so many things, always just get curious what is actually supported (especially when they tag a lot of modloaders and working out which versions they actually support and don't mention in the changelog, and as a player your like uh what does it support really).

Thanks