comp500

Results 280 comments of comp500

Unable to reproduce (missing information)

Fixed in Indigo (https://github.com/FabricMC/fabric/commit/c0ae659db23d759a232f17767d080b0ba3f501fa), needs port to Indium; see https://github.com/PepperCode1/Continuity/issues/120#issuecomment-1280003103

Closing: either I won't be able to fix this, or the other solutions I'm considering to improve fullscreen compat (inc #19) will fix it at the same time :)

Closing: seems to be fixed?

Closing: this isn't really something I want to pursue, as I would like to resolve FPS issues instead of working around them, and such an option if it were even...

Closing: insufficient information to diagnose the issue

Rebased on top of 0.8.5 (https://github.com/SpongePowered/Mixin/commit/155314e6e91465dad727e621a569906a410cd6f4). I was informed that [a mod](https://github.com/Chocohead/Crafty-Crashes/blob/e409aee8e58520667b57d75892606c5257a3e33d/src/com/chocohead/cc/SourcePool.java#L34) uses the current broken behaviour, so I've added methods to expose `IMixinInfo` in more places and provide greater...

Hmm... [the current strategy](https://github.com/packwiz/packwiz-installer/blob/main/src/main/kotlin/link/infra/packwiz/installer/target/ClientHolder.kt) is to retry up to 3 times, with read/connect/write timeouts of 10/20/30 seconds for each retry. I think this will still allow for relatively slow connections,...

I've tweaked the retry strategy to be 15/60, which should allow for pretty slow connections while not taking too much longer to carry out all retries if the server is...

I would love to implement this (particularly round-tripping comments), but it's not really feasible within the current architecture of packwiz and the TOML library it uses. This is one thing...