Jump to content

EvilOwl

Ascended
  • Posts

    1462
  • Joined

  • Last visited

  • Days Won

    36

Everything posted by EvilOwl

  1. Is %appdata%/.technic/logs really empty? If it is there were some reports where the launcher just had to download an update and you need to give it some time. leave it for 10 minutes and check then. If the system is holding it down you can try to run it as administrator and watch the taskbar for any popping questions about running it.
  2. How about you post the modpack api link? The one you use in the launcher and put those logs on paste.ubuntu.com
  3. Post solder configs, change any logins/passwords to ****** Post the webserver configs, again change any personal data to **** You set the root directory wrong on that page, solder.minewood-mc.co.uk should point straight to var/www/.../TechnicSolder/public. This way you expose the TechnicSolder directory to the whole world. Only the public directory should be public. Edit: use pastebin-like sites for configs, not all will work, some of them block php
  4. If you do you'll be running a custom modpack so don't post any crashes to the Bug Reports section, post them to Platform Pagoda instead.
  5. Read some topics in here and make your own thread about it, include links to logs and the modpack api link (the one you enter in the launcher)
  6. If you searched for hours you should know from other topics here how to upload logs to paste.ubuntu.com, post the link after that
  7. Copy the contents of the latest launcher log from .technic/logs and paste it to http://paste.ubuntu.com then post the link here.
  8. Open the launcher and paste the api link in the search box: http://api.technicpack.net/modpack/gigawatz 48 hours of free tech support included, after that time I'm going to transfer the modpack ownership to Gigawatz
  9. Uploading it right now, I added some dependencies you missed (CoFHCore, Mantle) and Waila.
  10. iChun released Blocksteps and Bee Barker for minecraft 1.8
  11. Be sure to have all needed drivers (you were missing the graphic ones earlier) like those for your motherboard/chipset. Edit: ...and find a smaller modpack obviously.
  12. How about you find a link to this submitted log in your browser's history and post it here?
  13. ...and bump the version on the platform so the launcher can be also notified
  14. He's giving you bad credentials. Where can he login with that? To the vanilla launcher? To his own technic launcher? Does he have his credentials saved there? Maybe he doesn't remeber his own passwords, tell him to log out of his launcher and log in again to check who's wrong. You cannot be both logged in with the same credentials at the same time.
  15. I actually did all that steps above I mentioned and the modpack started fine so hold onto that upload you did and just do the stuff i listed. Check if that would work.
  16. That log looks like: 1. You didn't paste the whole log. Check your log's end part with that one you uploaded. Is it really the entire log? 2. The game is running fine but you don't see it or you're not patient enough and you're forcing it to close. Pick one of those two options. I'm not entirely sure but there was also a mention somewhere on the mods related sites about old/legacy graphic cards not working properly with minecraftforge and/or cofhcore (which are both in blightfall). Don't quote me on that last one.
  17. You probably have the right Forge version locally and the wrong one uploaded to dropbox. If you're using some kind of barebones/simplyforge pack for local testing you need to check the bin directory there, open the modpack.jar file with winrar/winzip/other tool, there's a changelog file inside named like forge-version.mc-version.txt. This is the best way to check what forge version is hidden inside a modpack.jar file just to be sure.
  18. Hmmm you updated your mods and settings to 1.7.10, did you update Forge to 1.7.10? Link for the lazy you don't need legacyjavafixer with Forge above version 1217, remove it remove that mekanism directory from mods remove that 1.7.2 directory from mods, that wrong Forge version made it and downloaded a file there, remove it also Test all that and come back with a report.
  19. Upload the latest launcher log from .technic/logs to http://paste.ubuntu.com
  20. Still no problem there. I need .technic/modpacks/blightfall/logs/fml-client-lates.log It's a bit big but try to upload it on paste.ubuntu.com because that launcher log doesn't show anything wrong.
  21. Did you throw all the stuff to dropbox? I'll take a look but not now. Remind me in 5 hours or bug me on technic IRC channel with typing my nick around that time.
  22. Sure. Go here http://technicpack.net/news and read, read all the things. If Hexxit will be updated/released this will be the first place to have that information.
  23. Can I have a new, fresh log? Lets try one more time.
  24. That should be fixed in 1.0.7
  25. Quote from a friend: logs can be found when clicking the launcher options button on the top right corner on the launcher window. If you can't open the launcher the logs can also be found inside %appdata% -> Roaming -> .technic -> logs Paste the content on pastebin.com or paste.ubuntu.com and give the link.
×
×
  • Create New...