GrnEyedDvl

I didn't say anything about the IC2 bug, in fact I specifically mentioned that it was part of a custom mod pack but that this post was about something else. The only thing I said about custom modpacks is that they broke them last time around because the launcher wouldn't save them, and that they moved the save file paths around.

I really like how nobody actually read this and then goes off about my ranting. This was not a rant, and there were suggestions in my "rant" that were completely ignored. I know how it is developed, and have been involved in numerous such projects myself. In fact I happen to own a site that is about 10-20 times bigger than this one, and when we screw up (which does happen, especially recently with some upgrades) we don't respond to people this way. We also make damn sure we announce something BEFORE we launch it just so people know there may be some issues. And that site happens to host thousands of mods for a particular game platform, its not like I am not familiar with modding or coding or the issues that come with it. If anyone doubts me on that, then I will post a link to the site in question and prove it. I use the same name there as here and its well known who owns it. You are one that didn't actually read the post. Resetting a pack isn't going to do any good at all on a brand new install, or an updated pack. For instance, I have never once played the Hexxit mod. There is nothing to reset, its never been installed. I ran that modpack for the first time 2 minutes ago, and got this. Just how is resetting my pack going to fix that? I suppose I could manually go through the pack and fix all the problems, but that kind of defeats the purpose of an installer doesn't it? "CodeChickenCore doesn't support v 1.5.2" isn't specific enough? This is a mod installed by default by the Tekkit modpack that is incompatible with other parts of the pack. How much more information do you need? Putting a different version in the pack fixed it, but that was just one example. I posted another on 20 lines above. The shit that was too long to read included the explanation of the code behind it. You are too lazy to actually read a post and then complain about ranting?? That is the very definition of ranting. Accusing someone of ranting when you haven't even bothered to read the post is a bit hypocritical don't you think? See above. I really like how nobody responded to the BETA testing comments. Its really not that hard to create a subforum and let people willing to use the beta platforms comment on them before they are released. Instead we went from launcher version 322 yesterday to 325 today (which is fine) and it still has problems (which is not). I am assuming that the reason for 3 version updates in a 24 hour period is because you found problems, and I am glad you got them fixed. All I am saying is that you could have found those problems in the beta test process, if you had a structure in place to let people who actually use the beta launchers report them.

Its the entire platform, not a single modpack. You keep pushing things out as "stable" when they are nowhere close to it. You never give server admins any warning and it causes havoc for anyone running a custom mod pack. Not to mention that the built in modpacks are broken as well. For example this shot. In the background you can see crash files from a custom mod pack that's broken, but this is about the Tekkit modpack that is part of the platform. When you launch it, it asks you if you want to update. I clicked yes, it downloads the files and when its loading you get this. Obviously this wasn't tested at all if there are incompatible versions built in. On the custom mod pack side, every time you guys change something the custom mod packs are broken. Last time around the launcher wouldn't even pick up the custom mod packs, wouldn't save settings like RAM allocation, and you moved the location of saved games without notifying anybody. After everyone got their saved game locations moved, you updated the launcher and fixed the mod pack loading and settings were being saved, but you moved the saved games back to their original location and caused another round of breakage. Again without any notification. Nothing in the change logs. You have a setting in the launcher for using beta builds. Why don't you actually use that to its full potential? Setup a forum for beta testers to report problems, and a separate forum for server admins to report problems that arise in custom mod packs due to launcher changes. If you had the infrastructure in place on the forums, I have no doubt that lots of people would give you input BEFORE you mark something as stable and push it and cause all kinds of problems. I know I would. I would have no problems at all adding a test world to my current server configurations and having 10-20 people run through it so problems could found before they became mainstream. As things are now, I am tired of getting screamed at once a month because of problems caused by the platform when I had no idea changes were coming. I understand that you cannot possibly test every single custom mod pack in the world, and I would not expect you to even if it was possible. But what I do want is for my server and my single player games to run as smoothly as possible, and that simply is not the case the last few months. And the issue of incompatible on a default install is just sloppy. Its a pretty glaring oversight that's pretty easy to catch and even easier to fix, and it should have been. If you don't want to take suggestions and make procedural changes I guess that is your choice. I suppose you could even ban me, which again would be your choice, and I am all for having the freedom to make choices. But understand that stuff like this forces choices upon people, such as getting pressured to remove the Technic platform altogether and going with something else. Especially when this thing breaks in the middle of a scheduled competition. That's not a choice I want to make, but I also don't want 500 pissed off users.

I have to second this, and it causes huge problems for server admins. Also, since everything has been repathed all of your custom control settings and video settings and everything else are gone as well. The original path for modpacks was .technic/modpackname Now it is: /technic/modpacks/modpackname So all of your saved single player games need to be moved, along with all kinds of other stuff like REI minimap waypoint files. I cant believe you guys made a major change like this without notifying people, just pushed it out there and caused all kinds of problems.

Yeah they hosed this up pretty bad. The announcement is in the News section of the front page, but this is FAR from the only problem with the new launcher. Settings no longer save correctly either, such as RAM use even adding packs to the list of available packs. Both of those settings have to be redone every time you launch it.

The item is not colored until after it passes through a retriever, he is talking about what happens before it gets there. If two retrievers are requesting the same item, the closest one gets it and the furthest one does not. This sort of makes it impossible to setup a simple system with a presorted supply chain. Instead you have to resort to a complicated setup of retrievulators (that are buggy as hell) or lots of filters and sorting machines.

Worldguard has a remove drops command as well.

Do not take your users word for it, test it yourself. Use permissionsex, enable modifyworld, and blacklist the items for whatever user group you want. Here is the entry that prevents users from holding a nuke. They can still craft it, but as soon as they pick it up they lose it, and the materials used to make it.