Jump to content

Recommended Posts

Posted

Foreword: I am not asking how to develop mods with mixins.

The problem:

I have been building a large modpack (approaching 400 mods and I haven't finished yet) for a past couple of weeks and (just as expected) I have finally run into some performance issues.

I am aware of the existence of spark and Observable, which are excellent tools, but these won't help here. I suspect one of the mods did something silly to one of the Entity (sub)classes and I intend to track it down. Binary chop is not a feasible option here. A single reproduction cycle can take a couple of hours - combine that with the tangled mess of dependencies between the mods and you get the perfect recipe for a huge headache.

What I am looking for is a command/tool capable of logging [modid]<->[modified class] pairs. Or at the very least print all involved modid's for a given classname.

I am fairly certain this information is already somewhere inside the running instance, I just don't know how to get it out. Can someone point me in the right direction? 馃槄

Posted

Welp, turns out what I was looking for was already there inside debug log 馃槅

The logs starting with [mixin/]: Mixing contain what I was looking for.

Not exactly the easiest way to grab the data I need, but nothing a bit of greping cannot fix

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

  Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

  Your link has been automatically embedded.   Display as a link instead

  Your previous content has been restored.   Clear editor

  You cannot paste images directly. Upload or insert images from URL.

Announcements



  • Create New...

Important Information

By using this site, you agree to our Terms of Use.