is 161 stable now

[hydroflame]

Hey guys, title says it all

 

to those who used 1.6.1, would you say its stable now? are most method deofbfuscated yet ?

[maxpowa]

Honestly, nobody should be deeming it "stable" until it becomes a recommended on files.minecraftforge.net . Until then, it's too unstable for public use.

[Mazetar]

Hey guys, title says it all

 

to those who used 1.6.1, would you say its stable now? are most method deofbfuscated yet ?

 

Forge is not yet at it's recommended build, maybe it will be at the beginning of next week according to what's been said.

Forge builds do not change the deofbfuscated names, that is MCP and their mappings. So there we just have to wait some.

Luckly names are easy to fix and change so no worries.

 

So 1.6.X is NOT stable yet and wont be for a least a few days.

Which you could see since there's no recommended build and the release thread for forge for 1.6.X clearly states this

[hydroflame]

yeah i know theres no "recommended" build, but i wanted to ask people opinion on its stability overall as i don't want to upgrade to something ill spend more time debugging then actually coding my features

 

about the obfuscation mapping being mcp: yeah, sorry i forgot they're 2 different things

 

i can read the release thread y'know