Err, how about NO? I'm not wasting time on this. Sorry. It's a long weekend and I have a real life to attend to. I'm only interested in the discussion so I can make FML 1.3 look vaguely similar to the long term to try and smooth the transition over time. I can find that data out after the fact. There's plenty of opinion and most of it is not going to be germane to the real problems Mojang faces. See: the rest of this thread and the epic trolling on #minecraftdev ever since the announcement.
- cpw
- Curse Premium
-
Member for 13 years, 3 months, and 16 days
Last active Fri, Dec, 1 2017 15:36:58
- 14 Followers
- 207 Total Posts
- 317 Thanks
-
Jun 27, 2012cpw posted a message on Minecraft API Discussion - Sat, 20:00 CEST, #minecraftdev on EsperPosted in: News
Err, how about NO? I'm not wasting time on this. Sorry. It's a long weekend and I have a real life to attend to. I'm only interested in the discussion so I can make FML 1.3 look vaguely similar to the long term to try and smooth the transition over time. I can find that data out after the fact. There's plenty of opinion and most of it is not going to be germane to the real problems Mojang faces. See: the rest of this thread and the epic trolling on #minecraftdev ever since the announcement. - To post a comment, please login.
0
Easy then: set the chunks per ticket number to zero. Then every chunk loading ticket can load as many tickets as it wants. Good luck! Oh, and if you don't like it, I suppose I can remove the entire feature. Then chunkloading is gone again... Hmmmm. STFU.
0
OK. I'll bite quickly. Because I don't want a stupid mod to destroy the game for every other mod. Chunkloading has massive sideways impacts and can't be allowed to be laissez-faire. It's why Lex removed all chunkloading capability in Forge 4.0. I added it back, because it *needs* to exist in some form, but I put in place a mechanism which allows for end-user (and especially administrator) control and sets sane limits for normal play.
I have recently, at the request of chickenbones (by the way, why the f**k didn't you just *ask*?), added in a few extra features so chunkloading config remains centralized in a single config file for *all* chunkloading, and allows, by default, mods to override their default chunkloading configuration. Also, player tickets now exist...
Now, get that crap out of there...
0
How would an administrator deal with it if the administrative tools I put in place for dealing with it got subverted by immibis? ChickenBones has agreed to respect the configuration. Immibis will be *made* to respect it. I can block the mod from doing what it's doing. I would rather not though. Except every server administrator in existence? Yeah. no. Not buying it. Immibis now has a way to request a non-default configuration, I suggest he uses it or finds his mod having a very hard time working at all...
0
0
0
Don't put IronChest in the minecraft.jar. Don't put simple ores in the minecraft.jar.
0
FML and forge are rarely more than a day or so out of sync...
0
r17 works perfectly with recent forge/FML builds.
0
Fixed in latest FML. Will be pushed to forge shortly. Wacky way to do it: using custom chat messages!
2
Fixed in latest FML. Will be fixed in forge next build...
0
Nevermind. It's working. Forgemodloader support is fixed.
0
Yeah, you clearly know exactly what you're talking about.
http://www.minecraftforge.net/forum/index.php/topic,1200.0.html
The latest recommended build is 204, built about 5 hours ago. It works very well. To clarify something that is confusing you: ModLoader hasn't been a Forge requirement for about 3 months now. Forge runs ModLoader mods just fine without it (as well as Forge mods, obviously).
0
It is working. Get latest forge and download the version on the thread RIGHT now.
1
0
To all - the modloader compatibility in this mod is broken at present. If you recompile the "mod_ReiMinimap" class file you will get a working mod. Not sure what he built it against, but it's not the published modloader or FML/forge.