gummby8

I would recommend RCD (redstone clock detector) works great even on redpower clocks. I run the test for 1 second, if too many redstone clocks are going faster than that, it is usually a problem. Our server is no joke, but get a dozen or so redpower clocks going at top speed and you will see a difference in the tick rate. http://dev.bukkit.org/server-mods/redstone-clock-detector/ EE also was a major MAJOR cause of low ticks when we were first testing tekkit on our server. Just 4 full energy collector arrays would cut the tick rate in half. Not sure if EE or IC have an option so give more energy but at slower ticks, but I am sure it would help

Title: Cannot run any version of commandbook on tekkit 3.0.4 Version: 3.0.3/3.0.4 OS: Centos 5 / win 7 Java Version: 1.7.0_03 64bit Description of Problem: Cannot run any version of commandbook on tekkit 3.0.4 Error Messages: Error Log: 2012-06-09 16:57:32 [sEVERE] Could not load 'plugins\CommandBook.jar' in folder 'plugins' org.bukkit.plugin.InvalidPluginException: java.lang.NoClassDefFoundError: com/sk89q/minecraft/util/commands/CommandException at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:150) at org.bukkit.plugin.SimplePluginManager.loadPlugin(SimplePluginManager.java:310) at forge.bukkit.ForgePluginManager.loadPlugin(ForgePluginManager.java:55) at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager.java:231) at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:219) at org.bukkit.craftbukkit.CraftServer.<init>(CraftServer.java:195) at net.minecraft.server.ServerConfigurationManager.<init>(ServerConfigurationManager.java:53) at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:160) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:426) at net.minecraft.server.ThreadServerApplication.run(SourceFile:492) Caused by: java.lang.NoClassDefFoundError: com/sk89q/minecraft/util/commands/CommandException at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Unknown Source) at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:139) ... 9 more Caused by: java.lang.ClassNotFoundException: com.sk89q.minecraft.util.commands.CommandException at java.net.URLClassLoader$1.run(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:41) at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:29) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) ... 12 more

I think what he was, and I was trying to say is. We don't expect handholding but, preventative steps could have been made so events and threads such as this one never had to happen. In any case, my server works. So im through bitching, I'll pass my soapbox to the next "crazed idiot" Cheapshot I make an excelent burger made to order. You wana come to AZ we can talk about whatever over one, on the house.

Oh well I tried. Maybe too hard but I believe what I believe and I can't expect anything different from others. This was just one issue I have strong feelings about. Everything else about tekkit is amaizing for sure. <-- lol at the title

I must be, because fixing the aformentioned issues, wouldn't cause "growing pains" they would be harmless. As said before (were you reading?) there would be no server A trying to connect to client B. If there was I would understand why this whole argument is pointless. But that is a moot point. If I implimented the fix on my server, and no one had to update their clients, that is pretty definitive that there are no "growing pains" There would be no massive update of any kind, there would be no support issue because you would be eliminating a problem. Unless stated otherwise, there is no downside to implimenting 2-3 fixes for some major bugs here. At this point it is more of a ," We don't want to fix it, because you said so." There has not been one responce yet with a valid reason why the 2-3 bugs mentioned by myself could not be hotfixed and implimented and save the Tekkit team a ton of headaches. Inertia? Cars have inertia too, but changing my music CD doesnt cause my engine to seize. The fixes that are in question don't overhaul the tekkit engine. No time? You certain have the time to call me a moron half a dozen times I have no idea what I am talking about? I don't have to! The community made the fix for me. I just had to follow the nice instructions. You can too!

I think you contradict yourself on the top two lines there I never have to unzip bukkit pluggins because, they work out of the box. Configure, sure. Fix no. When I edit a config file that is configuring. When I unzip a compiled jar and replace broken class files, that is fixing. The difference? Bad design, unwilling devs, incapable devs? IDK. Again I don't buy the "too busy" excuse. Everyone here is in agreement that the fixes take but 5 min to impliment and for some reason call me lazy when I am wondering why the devs are the ones not willing to spend 5 min to put in the fix. I spent my 5 min implimenting the fix, so I wouldn't call myself lazy, I did the work. I know it takes 5 min, and thats all, and it works. Why can't the Tekkit devs take the same 5 min and prevent the other dozens of tekkit server admins from having to do the same? 100 server admins installing a 5 min fix with the added posts and threads say "OMG IT NO WURK" OR, take 5 min, add the corrected class file and re-upload it. I must be really special for the Tekkit devs to take time out of their "Busy lives" to come here to the forums and waste time calling me an idiot. I almost feel honored, like meeting a celebrity. Or maybe they are not as busy as they say. The team continues saying, " Oh you have no idea" then enlighten me. What sort of pilgramage would one have to go through besides a 5 min class file swap to impliment the fixes for say, Block place events or the monster tile spawner.

Lol given their current responses, your sarcasm is closer to truth. Anyway, no point in arguing anymore "mostly a bunch of asshat prima donnas" I suppose the statement is true once you second guess anything the Tekkit team does. They get defensive and make you look like the badguy instead of owning their mistake and simply saying "Yup we messed up, glad the community found it and fixed it. We'll get that fix in when we can" No it's nothing but, "You have no idea" "You're a moron" "You are not us" IDK maybe they are just too young to understand the concept of "owning your mistakes".

I know damn well I am not entitled to anything. I am wishing for the Tekkit team to own up to their mistakes instead of making me look like the badguy when they are the ones responsible for the mistake. I didn't ask when Tekkit 3 was comming out, I asked if the bugs would be fixed when it does, since the solutions have already been discovered. It would be quite silly if those bugs were still present in the next update. I also hope the community continues to find and fix bugs. That is what the communitys known for, and it is wonderfull. But I would like to see the Tekkit team actualy impliment those fixes. Especaly when they don't interfeer with Server A connecting to client B, when they don't take hours of testing. EDIT: Just thought of somehting that made me lol, "Tekkit.jar, some assembly required"

Re: Next Go-Around, please configure the pack better for balance and gameplay Sorry I don't belive the Tekkit team is such a victim of such a high workload that would cause them to dissregard such flaws in their own builds. So, if you are so busy that you can't spend the time to put in simple updates and fixes , and because I am such a whiny bitch asking for instant gratification all the time, I clearly must ask the following question. Will the aformentioned bugs be fixed in Tekkit 1.2? Or were you too busy for them in the last several months to spare your precious time to copy paste a fix into the next update? I'm just wondering if I'll have to be the one fixing the mistakes the Tekkit team refuses to take ownership for.

I am wondering where you are going with this. As every bug >>I<< have listed is 100% server side and does not require a client update at all. block place bug, monster spawner tile, even a new one I noticed today, EE DM and RM tools dont send block break events. All of these bugs have been fixed by the community and require 0 client updates. It still boggles my mind that the Tekkit team has not implimented a fix for the block place event yet. Do none of the Tekkit team members play on a server with any form of grief protection? Towny, worldguard ect.. You would know right away that your Tekkit jar has a giant security hole in it with flashing neon signs saying "COME GRIEF THIS !!" I can go to any tekkit server that does not have the community fix in place and dump lava wherever I want, I can place any block I please wherever I want, and this still is not fixed in the Tekkit.jar. Would any Tekkit team member advertise Tekkit as the easiest thing to grief? Because that's what it is currently. Infact you can't stop people from griefing unless you modify the Tekkit.jar yourself. I know you don't "market" Tekkit to people who have no clue how to run a server, but the very product you are giving people is defective in a big way. I don't buy the "We have lives" excuse either, because I doub't the tekkit team is so busy that not one person could take the 10 min to fix a snipit of code, or at the very least, drop a class file into the jar and re-upload it. I don't belive the Tekkit team want to be assholes but the lack of an official solution to some of these very gamebreaking bugs (that don't require client updates) says to me, "We don't give a rip if your server and your content is safe or not" I doubt that is the message the Tekkit team wishes to convey, but that is what it is currently.

Your right I removed em

Re: Next Go-Around, please configure the pack better for balance and gameplay Cheap Shot, I understand you and the Tekkit team put a lot of thankless effort into Tekkit, and first let me be one to say, thank you. It is a wonderfull mod/pluggin/api that you and the team have made. You are correct. I don't do what you do. I won't pretend to know how java works. I am a network architect by trade, not a java dev. But when you say that there was extensive testing done, and some of the bugs that we have seen show up, I can not help but question that statement. Case in point, the monster spawner tile bug. It took me 5 seconds to select a 100x100 area with world edit and use //cut and //paste to find that bug. This is such a highly used process it is suprissing that no Tekkit member found it. Anyone should hit a monster spawner withing a 100x100 area, and I would have thought that would cover just about any BC or IC2 or EE natural block as well. Going forward the error generated in console referes to the monster spawner tile. Again I don't know java but simply downloading Bukkit 1.4 and replacing Tekkit's class file with Bukkit's class file, appears to solve the issue. This wasnt an issue with a mod, this was an issue with Tekkit. Again simple things like, "omg my keys overlap" suck it up and remap your keys, but again I shouldn't be replacing class files in the tekkit.jar for something that took 5 seconds to find and 5 min to fix. Even if the Tekkit team didn't find the solution, a simple "Thanks for solving that bug, it will be fixed in the next update. And then.....actualy update! Why hasn't the monster spawner tile bug or the world guard protections fixes been implimented yet? They are really bad and highly game breaking bugs. A community member found the solution, confirmed by the community to work, and Tekkit hasn't updated or hotfixed or whatever yet. Its been months. Im not asking for 1.2, I am asking for a bug fix release! You even have a common problems and fixes thread! What is it good for if you don't even update it with "Common problems and fixes"!? I understand some things do go unoticed, or forgotten, or fall through the cracks. But to come back and say "you honestly have no idea what you're talking about, and base most of that on nothing" seems harsh, and unfair to your community. We do test, we do find bugs, we do find fixes, and when they are that simple, anyone would question the Tekkit team's effectivness. I compare the above mentioned bug to ordering a burger without pickles, and recieving a burger with pickles, and then the burger guy gets pissed at me for confronting him about making my burger wrong. It's like "Really? Come on man." A simple mistake like that is understandable, you don't need to insult the intelegence of your community with things like "You have no idea" or "You are not us"

Re: Next Go-Around, please configure the pack better for balance and gameplay Yes I agree that there is some configuring needed for a server to function. But I should never have to unpack a jar and replace class files because the monster spawn tile is borked. Or do the same because the block place event isn't working. THOSE sort of bugs should get fixed within a day or confirming that the bug exists

if you have world edit installed id recomend using //remove items 10000 if your players have bad pipes it can cause a huge issue with spitting items onto the ground. I also recommend clearing all living entities from your world I use super mob removal because /butcher doesnt clear animals and people with crazy huge farms will cause a problem too.

Re: Next Go-Around, please configure the pack better for balance and gameplay It's called a pull request. Someone fixes a bug you are too busy to deal with. All you have to do is test teh validity of the fix, and impliment it. Pretty much every dev on bukkit does it. Thats the beauty of a community. The tekkit devs could impliment the fixes and spend a day testing their validity. And then release a patched client bug free! Or someone here could write a walkthrough of every bug and the 4 hours of patching and config writing that is needed simply to get Tekkit to work with basic plugins, like towny or worldguard. I find it absolutly rediculous that the block place bug is still present months after release, that literaly makes protection plugins such as towny or worldguard useless. If bukkit had such a problem they would have it patched within a few hours of the bug being confirmed. Tekkit? "Oh build perm plugins are broken? Meh fix it yourself. We just put the mods in this cool looking package for you."