Jump to content

Rainbow Dash

Members
  • Posts

    58
  • Joined

  • Last visited

Everything posted by Rainbow Dash

  1. Pony-time! (Break)

  2. Bro-tastic! Have fun playing. :3 For future issues, the user Motion Flex mentioned that some guy on the Yogscast forum solved his issues by deleting some folders and stuff. Can read about it here if interested: http://forums.technicpack.net/threads/keep-getting-cant-connect-to-minecraft-net.13523/#post-101349
  3. Thanks! Gonna start suggesting this instead of deleting everything! Thanks for taking the time to post it here. :D
  4. What did you do before you got this error? Is this your first time using the launcher? Are you running this as an administrator on your computer?
  5. I'm not liking those getMirrorUrl in the error.. Anyhow have you tried to just let the logo stay there for a while? I've had to wait up to two minutes for it to start.
  6. So no love for a brony? :c ((Sorry for irrelevant posting... moving right along!)
  7. Great. Sounds a heckofalot like a minecraft.net server issue then.
  8. I've never had an issue with the default memory allocation value. You should be safe... if an issue occurs just make a thread about it - as it will be a different issue. Remember to include the logs! Glad you got it working.
  9. I'm sure it wasn't intentionally done! I'm stunned to see so many new posts about the same issue since I joined and the disabling of AV hasn't solved it so far, unfortunately.. It does look more and more as a minecraft.net server issue.
  10. I don't think the latest launcher supports jre6 anymore. Can someone confirm that? The all-caps thread ''COMMON PROBLEMS AND SOLUTIONS'' suggests you update to the *LATEST* edition of Java 7. Thread is here: http://forums.technicpack.net/threads/common-problems-and-solutions.10851/
  11. Yeah, that's the common issue right now. A lot of reports and comments suggest this is an issue which is caused by the minecraft.net servers being ''wonky''. So a Mojang issue. Other users, myself included, have got it to work after just trying a few times. Really shit situation but, eh.
  12. Yeah @compwiz91, that's exactly what I experienced too. I pointed it out in my bug report (which is now looking more and more obsolete if this is simply caused by minecraft.net servers...) Just trying a few times did work for me in the end. Strangest thing!
  13. Oh joy. Well try your way first!
  14. Hehe, although I wasn't very helpful, you're welcome. Also I thought I should point out that another user in one of those threads managed to get it working after around 5 tries. I'd give it a few more minutes and just give it a new shot later on.
  15. This is a common issue right now and most likely related to minecraft.net - the Mojang servers. Most of the top-threads (based on activity) here ( http://forums.technicpack.net/forums/technic-launcher-bugs-problems.10/ ) are about this issue right now it seems. Give Mojang time to fix their servers and it should be working I hope.
  16. My bad... bin, of course it's bin! Also damn, same issue? The issue you present with the jre7 folder having an entirely different name sounds too familiar to me. I ran into this issue when upgrading a MDM system at work. I'd reinstall Java 7 entirely. May I also suggest installing Update 5 instead? EDIT: I don't want to suggest this, but you could ''consider'' also removing the versions of java which you do not need for this. I don't want to suggest that because of the implications it could have on other software on your system that might require it... It's just a thought though, although it should be unnecessary!
  17. Hey it's what I love doing! I wish I had more helpful things to say..hopefully my stay here on the forums will give me a lot more experience with troubleshooting the launcher and such. ^_^
  18. Well as Torezu pointed out in several other threads there is an issue with connecting to the minecraft.net servers - the Mojang servers. I'm not sure if it's right to blame the launcher for all the issues (even though it conveniently started after I updated) until we can wait out the issue Mojang is having (AGAIN)...
  19. How frustrating. I included it with the OP... Will remember not to edit a bug-report OP in the future. Damn it! I'm running Symantec Endpoint Protection 11.0.6200.754 EDIT: Yes, I have attempted to disable it.
  20. This is the thread The_DarthMoogle is referring to: http://forums.technicpack.net/threads/common-problems-and-solutions.10851/
  21. The amazing Torezu has pointed out that it could also (and *most likely*) be an issue with the minecraft.net servers (again) (surprise... no?) So yeah, not an issue with the launcher. Give it time I suppose.
  22. I'm not sure if there is a solution to it at this moment. Does anyone have a proper solution for this? This specific issue isn't listed in the common issues topic at the moment - as far as I can tell anyway. (It is, but this has been attempted as a fix by many already. Unfortunately unsuccessfully) I would suggest just trying to keep reading those other threads or keep an eye on this: http://forums.technicpack.net/threads/common-problems-and-solutions.10851/ EDIT: Also, you could try running it through the JAR file. Download the latest JAR, right-click it and select "Open". This has worked for a couple already.
  23. Hehe, I understand. No worries! I'd be confused too if I wasn't used to this launcher. What's the problem you're having right now? :3
  24. Perhaps it was the wrong section to post in, but the user was by far an idiot. I'm pretty sure a simple google-search or two would do the trick and give him plenty of information rather than starting a new bug-report thread, but I too dislike the rude approach by some users here. Granted I'm new, it's a bit of a cold attitude to receive from a ''help'' kind of sub-forum. Just my $0.02 on that. Regarding other mods being included, the ones you mentioned have already (as you probably gathered between calming yourself) been excluded for very good reasons: Poor code, general incompatibility and lack of interest (perhaps). Tekkit - as I'm most experienced with - has enough bugs as it is and with the upcoming changes in 1.3 (or/and beyond) it doesn't strike me as the best time to try to mix and match up new mods into the pack. Tiny-editing: I've also heard ''rumors'' that the creators of other mods have simply not wanted their mods in these packs anyway... although that's just something I heard. Nevertheless, read below: Give it time. If there's compatibility and interest new mods will most likely be included (with time).
×
×
  • Create New...