How to - edit core classes for debugging?

[TheGreyGhost]

hi all

 

The new gradle setup for Forge has put the Forge and Minecraft sources into a library.  Previously I used to edit the vanilla classes to add diagnostics etc when I was trying to figure out how the vanilla worked (or more often - why my own code didn't work).

 

I'm hoping that I can still do this just by removing the forge jar from the library, extracting all the files into a test workspace, tweaking the build config (should be fun! have no idea about gradle), and editing them directly as in ye happy days of olde. 

 

Thoughts from people who know more about gradle and IDEA than me?

 

-TGG

 

 

[shadowmage4513]

Sorry, I don't have an answer,

 

I was just writing to add that I, too, am curious as to how this can be done.  I have needed this ability at various points to track down strange issues or to more-closely examine how the base MC source works.

 

It would be a shame to have to set up an entire Forge/FML dev environment just to add some temporary debug output to a base-class.

[GotoLink]

You can still put breakpoints and run client/server debug.

[TheGreyGhost]

You can still put breakpoints and run client/server debug.

yeah that's true, and in 3/4 of the cases that works fine for what I need.  I'm thinking of those cases where it's more effective to modify the code to log or to see what happens if I comment out part of the code.  Especially for rendering, or for code that gets executed many times and I need to break if a particular condition becomes true.

 

I'll give the extraction idea a crack, can't be that hard surely :-)

 

[LexManos]

Officially, the answer is that you can't We are trying to drive home the point that modders SHOULD NOT be editing base classes.

However, if you're smart enough to setup project dependancies, and know how to keep your code seperate from the minecraft code then there is nothing stopping you from doing it.

Go forth and figure it out!