Jump to content

po5

Members
  • Posts

    71
  • Joined

  • Last visited

About po5

  • Birthday 12/02/1985

po5's Achievements

Grass

Grass (2/9)

0

Reputation

  1. If this is multiplayer you should not allow a blackhole band because using it with an alchemy bag can get some serious duping going
  2. Seems to be working fine with 3.1.2
  3. po5

    [3.1.1] Pipe Error?

    Does anyone have any idea what caused it?
  4. Title: [3.1.1] Pipe Error? Version: 3.1.1 OS: Ubuntu 12.04 LTS 64 Bit Java Version: Java HotSpot 64-Bit Server VM (build 23.1-b03, mixed mode) Description of Problem: The server threw the following error in console, i am not sure what excactly caused it. After the error the server froze, everyone lost connection and no-one could connect until it was restarted. Error Messages: java.lang.NullPointerException Error Log: http://paste.ubuntu.com/1116499/
  5. The forcefields are really awesome.
  6. I tried this on a 3.1.1 server and it does not work
  7. Title: [3.1.1] Nether ore wont macerate Version: 3.1.1 OS: Ubuntu Java Version: 7 Description of Problem: Putting iron or gold nether ores in rotary macerator will not yield anything Error Messages: Error Log:
  8. Im pretty sure this is fixed in 3.1.1
  9. Hey. I really love EE, but i believe the condenser is imbalanced. The fact you can put pipes into it, and generate thousands of emc in minutes, from cobblestone generators or something similar is too imbalanced. It causes a huge supply of resources that is way above the demand, even by EE standards, which tends to require a fair amount of diamonds etc. itself. So do you think we could remove the ability to put pipes into alchemical chests and condensers to avoid these infinite resource machines, they really kill the later stages of the game, especially in multiplayer.
  10. This is kind of off topic. But most plugins will error alot if you use forcefields on your server, 3.1.1
  11. Why are you going to bring stupidty into this? Its very arrogant of you. Whoever decided to release 3.1.1 for servers, but hold the update on the clients have created this problem
  12. Thats no You are trying to manage the community but you only end up creating more problems. First of all, the servers who do update loose players because some people cant connect, 2nd of all, when people switch to the dev builds, there will be a point where you push a new dev build, and these people will update without knowing any better. Then they cant connect. And whats the reason for this? You dont want to "Break every single server". Well that will not be the case since client updates are optional.
  13. That is pretty far out. Take a look at the front page, only links to 3.1 but why should server owners use it? Clients are not 3.1 yet. Its got nothing to do with server owners failing to pay attention, its something wrong with the release cycle from the tekkit team
  14. We dont need the devs to manage the community, or more specifically server owners. When a release is ready, release it. And if help is needed to test it, say it. The way it is now they recommend server owners to run 3.1.1 but clients to run 3.0.4 which makes no sense
  15. Keep in mind the version on the front page is not what you want to get. Its only a dev build and not recommended
×
×
  • Create New...