Jump to content

gummby8

HELEN KELLER
  • Content Count

    52
  • Joined

  • Last visited

About gummby8

  • Rank
    Member
  • Birthday 01/01/1900
  1. 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 mor
  2. 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.l
  3. 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.
  4. 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
  5. 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. Unl
  6. 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
  7. 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&am
  8. 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
  9. 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 p
  10. 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 wo
  11. 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
  12. 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
  13. 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.
  14. 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 plugi
×
×
  • Create New...