Jump to content

plowmanplow

Discord Moderator
  • Posts

    4594
  • Joined

  • Last visited

  • Days Won

    74

Everything posted by plowmanplow

  1. Creating a server from an existing modpack:
  2. Updated all the 1.6.4 versions, and the 1.7.2 version to include Lexmanos' Java 8 hotfix.
  3. You might see a few things in your web server error logs, but most things are caught by the API and only displayed in-line.
  4. I mean from the console during installation if any errors pop up. The API tries to output some fairly comprehensive detail if a critical error is caught as well.
  5. The Dashboard and the mod list are supposedly going live along with a number of other fixes (like the pack limit issue when using Solder) as soon as SCT gets to it. They have been stated (in IRC) to be fixed, just not pushed out yet.
  6. Looks like you didn't complete the installation process properly. Make sure you are following the directions in the Wiki.
  7. Solder 0.7-DEV is what you should be seeing. Without more detailed console output and more information about which versions of everything you are running, it would be difficult to guess what the problem might be.
  8. That error is telling you that the mods on your server (the specific ones listed) do not match the versions in your client pack.
  9. It has been stated by one of the devs/admins in the Technic IRC channel that they intend to implement a method for starting the launcher directly to the modpacks tab.
  10. You haven't provided enough information for us to assist you. What modpack are you working with? (provide API/Platform URL) The logs are truncated. You should be posting full logs in a pastebin service. Do you have a crash report? Post at in a pastebin as well.
  11. Don't paste partial (or full) logs or crash reports here. Use a pastebin service.
  12. Since the pack archive referenced in your pack settings hasn't changed, and the pack version number hasn't been incremented, I cannot guess as to what might be going on. You'll need to update things before I can diagnose the current configuration.
  13. You have two files named "CodeChickenLib-1.7.10-1.1.1.99-universal.jar" and "CodeChickenLib-1.7.10-1.1.1.99-universal (1).jar" in your /mods/1.7.10/ folder. When CodeChickenCore initializes it will check to make sure that the CodeChickenLib (CCL) mod is up to date. However, it will only check the "correct" version of the name (the name the author assigns to the file). Since you have a file with (1) in the name the correctly named file will get removed and updated, but the (1) version will be left. When the pack starts you now have two different, conflicting versions of the same mod and the pack will fail. Either remove both CCL mods from your /mods/1.7.10/ folder and just let CodeChickenCore download the latest version, or remove them both and get the latest (#110 I believe) version and put that in the /mods/1.7.10/ folder.
  14. I just ran through a new install of Solder on Windows 7 (should be the same for any other 64bit Windows). I used: Apache 2.4.10 x64 from ApacheLounge PHP 5.6.4 x64 from php.net MySQL Everything worked as expected following the installation procedure on the wiki. I was able to make a pack, make a build, add a mod, etc. I was not able to add a mod version, but that may be something local or some other wonkyness with Solder on Windows. I haven't gotten a response about that yet in IRC and I can't seem to get it to output any detailed error information while trying to get the MD5 hash.
  15. Always post full logs and/or crash-reports using a pastebin service (such as pastebin.com). You have not included enough information to diagnose the issue.
  16. You will want a minimap mod in your pack. There are a few available, but my recommendation would be to use Litemod along with voxelmap_litemod.
  17. It's fairly straight forward. Just drop the JAR into the /mods/ folder. If the pack doesn't start then you'll just have to remove OptiFine. OptiFine is widely known to be incompatible with a ton of mods and generally difficult to work with if it doesn't just work "right out of the box".
  18. I'm not really sure what you are asking for. The whole purpose of the ore dictionary is to make blocks/items from different mods, which are registered with the same "type" (such as oreCopper or ingotTin), work interchangeably with each other. Do you have recipes that won't take a specific kind of tin or copper?
  19. It is relatively straight forward to ensure that most filesystem calls in PHP are platform agnostic. However, I've not gone through the code to see if they are relying on features common to *nix. Your best bet is to just try going through the installation process and see where it gets you. I would highly recommend sticking with Apache/Mysql/PHP even on windows.
  20. Try going directly to http://your.ip.addr/index.php/ I can't go do just the base URL on mine, it doesn't detect the application correctly.
  21. You'll need to provide more details in order to diagnose the issue. The easiest way to do that is for you to provide the API URL for your modpack so it can be tested locally.
  22. There is a version of Worldedit for Forge/MC 1.7.10: http://minecraft.curseforge.com/mc-mods/225608-worldedit
  23. TiCTooltips is a client only mod. Try removing that. The error here: Caused by: java.lang.NoClassDefFoundError: net/minecraft/world/World indicates that you have a client only mod in your server mods folder.
  24. The key set in your app.php config file needs to be 32 characters long, like this: 'key' => 'fhdj4837xhak4#&dhDGWO35%1bxkao^2',
  25. This is a known issue at the moment. Check the issue tracker on Github for a temporary workaround.
×
×
  • Create New...