Jump to content

nextcode

Members
  • Posts

    16
  • Joined

  • Last visited

About nextcode

  • Birthday 04/12/1994

Contact Methods

  • Website URL
    http://www.technicpack.net/user/view/269182

nextcode's Achievements

Grass

Grass (2/9)

0

Reputation

  1. I will help you if you can send me the crash-report.
  2. OpenAL in "/usr/lib/java/openal.dylib" is missing or you don't have read-permissions on it.
  3. Nope it does not. I do not distribute the Mojang Server Software. I just wanted to show how to create a Minecraft-Server for a custom modpack. So please delete this useless thread. If it has been already done...
  4. http://www.technicpack.net/modpack/details/technologica.149355 http://feed-the-beast.com/
  5. Hello Technic-Users In this thread I will show you how to create a server for your own custom modpack. Requirements Existing / working custom modpack (you need to run it at least one time on your client without errors) Valid Minecraft license (you need it to download the minecraft server) Preparation Create a new directory for your server Copy all the directory's from your client-directory to your server-directory You will have now the folders 'coremods, config and mods' in your server-directory. Delete all files and folders in the server-directory except this three folders. Check if all your mods are SMP-compatible (usually is written in the mod description). You need to delete all the mod's who are not SMP-compatible (see the mod-description for further information). Build your Server Download the offical Minecraft Server (as jarfile) from Mojang (You need the server based on your Minecraft client-release) Copy the content of your client "modpack.jar" from the /bin folder into the official Minecraft-Server jar. Rename you Minecraft-Server.jar and place the file into the root of the server-directory Now get a script from the internet to start your server (java -Xms512m -Xmx1024m -jar...) Start your server - Your server should now work !
  6. You also have to specify -Xms when you use the Argument -Xmx. Xms set the minimal ammount of RAM java can use for his JVM.
  7. Hello Dorky This seems to be the error to me jinput.jar is a file of minecraft itself. You can try to rename or delete the folder .tekkit in %appdata% and retry to add your modpack into the launcher.
  8. Or better you run without firewall (could be a port or website blocked)
  9. IC2 is the cause of many such problems. On the main page you can just download v1.11 witch is only compatible with MC 1.4.7. To find v. 1.16 (witch is compatible with MC 1.5.2) you need to go to their build (dev) site and download a current snapshot. (You can also take the one I posted on #2 - Its v. 1.16 and compatible with MC 1.5.2) But IC2 is far too unstable for us so we decided to remove it from the modpack. The modders will not continue to build a compatible version to MC 1.6.x.
  10. Hi can you give us the report for this issue? Could also a problem that has been fixed in the newest releases. Did you mind to put the ChickenBones BasicComponents into the Coremods-Folder?
  11. It should be fixed in the newest version of buildcraft. Witch version are you using?
  12. You can also setup Permissions with BukkitForge and Essentials on your server.
  13. It's the modpackers fault. He should reupload it to a webserver witch is available or update the link on the modpack-page.
  14. Could also be a problem of the hoster of the modpack.
  15. Seems like IC2 and GalacticCraft are incompatible in this versions. Witch version of IC2 are you using? You can also try to use the versions of GalacticCraft / IC2 of mecanized (archive version). This is the latest release before we removed IC2 due to stability / performance-issues
×
×
  • Create New...