chylex
chylex
I reimplemented the tailing logic in my project to see how far I can get, and found that besides `Modify(Metadata(Any))` you mentioned, watching the parent folder also fired a `Remove(File)`...
I found https://www.youtube.com/watch?v=R-BPNomdkBE which configured Commit Status Publisher with the GitHub integration but using the Gitea API endpoint, so I guess GitHub and Gitea have the same/similar APIs? Haven't tried...
Any update on this?
I manually do the instruction printing from coremods when the transformation fails, how would it work in the modlauncher?
Can't get it to work, I set the system property but it's not getting through the `MarkerManager.exists("CLASSDUMP")` condition. The main point of this is so users who run into conflicting...
I'm probably doing something wrong... I tried using the system property both in the forge profile in the launcher, and in dev environment. Stepping through the latter returns false on...
Dumping is good for devs, but as I said, I use this as a tool to diagnose errors/conflicts on the user's side - if a transformer fails, I dump instructions...
Oh, I heard of shading but never thought to dig deeper into it, that resource could be quite useful, thanks. So yes, shading is definitely needed there. Calling the checker...
Okay, I did find a potential problem because the coremod returns class name as string, so the shading doesn't update them properly. It also then ignores the actual mod... I'll...
I thought about it and with the background line colors I made the call to not add customization, primarily because every single thing that's in this plugin becomes my responsibility...