Jump to content

Ragnar Homsar

Retired Staff
  • Posts

    530
  • Joined

  • Last visited

Everything posted by Ragnar Homsar

  1. Here's an idea: don't be an ass and act like you know better than your parents. If they don't want you playing FPS games, then don't argue. Not much you can do.
  2. Get rid of McAfee. Get MSE.
  3. I can't access edit history, much less delete parts of it. I get the feeling Tapatalk is at fault.
  4. For the record, yes, I edited the OP. I think it's much better this way.
  5. I managed to get Magecraft 0.1.0 to compile, after fixing quite a few things in the code. http://rhematic.net/mc/magecraft.zip None of the items actually do anything but it's a start, there's no errors in the code. Here's the source I used to build this version: http://rhematic.net/mc/magecraft_src.zip
  6. Tell me how this works? If you don't explicitly sign away your rights to graphics you've created for a mod, then the mod author doesn't have any rights to it and you can, if you really felt like it, charge them with using your graphics without permission.
  7. Sounds are more often than not ripped from some source with its own specific copyright statement, and most textures/images are derivatives of the original graphics in Minecraft (UIs, Industrialcraft blocks using the old iron texture as a base for machine blocks, etc.)
  8. If you didn't get the hint I was telling you to shut up too, that's why I pink name'd you too.
  9. This guy has the right idea, and for the record I WILL be perma-kellering for people being idiots about copyright.
  10. If you scroll down on the Index page a bit, you'll see the mod discussion forum. Please take some time to look at the forums some more before asking where anything is.
  11. Also note that pretty much all of the "latest versions" you cited are for 1.3+. I also don't see any dupe bugs fixed between the 1.3 update and the last 1.2.5 update.
  12. are you going on about?
  13. In accordance with the rule I set up over on the Launcher bug board, if you post a bug that is not modpack-related, you'll get a 3 day ban. Repeat offenses will result in a week long ban, and then a permaban. How do you tell if a bug is modpack-related? Torezu explained it nicely: If you get past the Launcher and end up at either the Mojang screen or "Minecraft has crashed!", it's a modpack bug.
  14. Seriously, you people just can't stop doing it. From now on, if I catch you posting a modpack bug in this section, it's a 3 day ban. No questions. Doing the same thing after you get banned will get you banned again for a week. After that, you're perma-banned. Wanna know what constitutes a modpack bug? Torezu explained it concisely in the last warning topic I made:
  15. Give us a log first.
  16. This isn't even a Launcher bug, the Launcher finished what it was supposed to do.
  17. Server Op Swap Shop is not for you to pimp your server and ask for mods.
  18. Your Anti-Virus program looks suspiciously like a rogue.
  19. Uninstall AVG and get Microsoft Security Essentials or Avast!.
  20. Your post will be deleted otherwise!
  21. Regdates are what you have dick-waving contests about when post counts don't work. :v:
  22. Get rid of AVG anyway, it's a huge piece of shit.
×
×
  • Create New...