Please send your log, otherwise we can't know what the issue is. Also that is too much ram to have allocated.

What are you referring to by "addons" then? Mods that you downloaded separately and added to the EMC-F-v2 folder yourself?

You can remove the conflicting mods for Aristois to work, otherwise you cannot use Aristois with this modpack

Not currently with the client

Nuker automatically disables when you re-join. You can enable/disable mods from the main menu by pressing right-shift

Delete libraries/net and try again

Yes

Not sure what happened yesterday but now it's working fine. There were no issues

9f3ada3a-e71d-40cf-bda3-406e08611c51-image.png

0b05fbb4-589e-4496-94bd-5a6eada742ef-image.png

Thanks for the log, it has been forwarded to the developer

If they are all mods, you can just use .setbind and press the same key for all of them.

With macros you use &&. Example: .t BunnyJump && .t AirJump && .t NoFall

@dyiing SOCKS5

It says the issue

OptiFabric error: OptiFabric could not find the Optifine jar in the mods folder:

You have OptiFabric but not OptiFine. You need to add OptiFine to /mods/ or remove OptiFabric from libraries/me/deftware/EMC-F-v2/

That's why then.

Send your log file after the game loads to the main menu. You can also try this: https://discuss.aristois.net/topic/27/aristois-isn-t-loading-only-emc

No, Aristois is not a miner. Since it is loading more stuff than the vanilla game, you can expect usage to be slightly higher.

On my machine (i7-8700k), vanilla sits around 2.6%, Fabric at 2.8% and Aristois around 3%. The only time I see spikes is loading new stuff (which of course happens on Vanilla and Fabric too).

353463b3-44dd-4ce9-931b-5eb1302a3df2-image.png

It's also important to note that the usage will be higher while resources are still loading. My main menu sits at around 80% usage until everything is done loading.

Have you compared the results with vanilla and Fabric? In a server? You might want to try allocating more RAM if it's running on the higher end.

This was a bug which is now resolved