Jump to content

Serpardum

Members
  • Posts

    5
  • Joined

  • Last visited

About Serpardum

  • Birthday 01/20/1964

Profile Information

  • Gender
    Male
  • Location
    California
  • Interests
    Just about everything
  • Minecraft In-Game Name
    Serpardum

Serpardum's Achievements

Dirt

Dirt (1/9)

0

Reputation

  1. He is saying delete (or change the .zip extension to something else) the file: %appdata%Roaming.TechnicModPacksBigDigModsDimensionalDoors-1.5.2R1.3.6RC1-73.zip If it was me and I had this problem I'd probably rename it to .xxx, run the game, quit and name it back to .zip Removing it should get rid of the offending pocket dimension. I haven't tried since I haven't gotten this problem, but just saying.
  2. I am playing Big Dig on single player and I hosed my character file. I gave myself an item with bad meta data. Since Nether Ferrous Ore is worthless, I was going to get rid of it and give myself twice as much Ferrous Ore as a work around. Instead of giving myself 18 1051:4 I gave myself 4 1051:18. It wound up crashing the server. I loaded NBTExplorer, went into my serpardum.dat file and deleted the item. Loaded BigDig and crashed. Went into my character file and it was back. Tried a few times with same thing. Completely deleted serpardum.dat, ran bigdig and crashed. Serpardum.dat was there (as it should be when it doesn't find it) but it was the character with the bad id and metadata. Searched for serpardum.dat and it was the only one. Deleted serpardum.dat in the BigDig!saves folder. Where is Big Dig necroraising this information from? The file is deleted. It should be the only place it exists. Please help!
  3. I'm having an issue where most of the time I load technic and I can't launch any of my packs. I have the console up and when I click on a pack I onloy get a few lines of info. It says "loading" under the packs but never does. I've found that if I close technic, relaunch it, click ont eh pack on the left and see if I get the additional info. I have to redo this until eventually it loads the info. Last time it took me around 20 tries before I got the additional info and was able to launch my client.
  4. Okay, apparently the good people at Technic have taken care of this magic themselves. To test I simply renamed the forge universal jar to modpack.jar, put it in a bin folder, zipped it up, put it on the interweb, made a new modpack, pointed it at this, ran technic, installed my modpack and ran it and... forge was setup. Thanks Technic!
  5. I've run into an issue with updating my modpack from 1.5.2 to 1.6.4. I am using forge and am trying to install the forge 1.6.4 universal into my .minecraft. It turns out that I need to manually download two files from mojang bcprov-jdk15on-148.jar.stash and scala-library.jar.stash and copy them into the .minecraft/lib file removing the .stash extentions. However, this gives me a few problems. My pack would only include things in the packs directory, not the /lib directory and secondly, I"m not legally able to redistribute anything from Mojang. What can/is be done about this? Is there a workaround?
×
×
  • Create New...