Jump to content

pigsrevenge

Members
  • Posts

    10
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed
  • Personal Text
    I am new!

pigsrevenge's Achievements

Tree Puncher

Tree Puncher (2/8)

0

Reputation

  1. hi hope I haven't missed something but is there no recommended version for 1.7.2 because the dust hasn't settled yet? is it too early and I'm too impatient? thanks ed- and in the meantime we use the latest versions? thanks again
  2. Hi, just wondering what you think of using optifine atm (C7 with forge953) [last post mentioning Optfn was Sep. for mc162]. I recently removed it because of a crash and haven't missed it at all. There used to be a line in the readme that forge ensures the good operation of optifine - is that with mods as well? There are lots of posts in various forums about problems with optifine - so what is your recommendation? is it worth the (potential) trouble? thanks
  3. me too don't let the turkeys get you down guys
  4. Hi-thanks for the replies- I kind of answered my own question by running forge version #916 into my #883 directory without problems, so I in changed the forge version with the same mods and configs and saves without creating a new separate forge #916 directory. I have been making new directories outside dotminecraft (but still in the roaming directory) because I don't get how to isolate saves and mods to different profiles without doing it: if I create a profile within dotminecraft I get all old saves showing up regardless of mc version. I have seen references to mods being classified by mcversion within the dotminecraft\mods folder but can't reproduce it. Are there supposed to be sub-folders like mods\1.6.2 and mods\1.6.4 in the dotminecraft directory created by forge? And if I save a 1.6.2 world (in dotminecraft) why does it show up in a 1.6.4 profile in the dotminecraft directory? I manage ok with what i'm doing and now know how to update forge by applying a new version to my old directory. So thanks again for all your work and this forum.
  5. Hi I make a new folder for each time I update forge and/or minecraft versions. Is there an easy way to update forge e.g. with mc1.6.4 from #883 to #916 and say install over the top of the older version? or something like that? I mean without creating a new version and dragging mods and configs over. (I normally do it piecemeal in case something goes wrong with an id conflict or whatever) I don't know how unlikely a possibility that is but put another way: what is the best way to recreate a modded 164/forge883 with forge916. Is it enough to just copy the mods and config folders to the new version folder? I hope this makes sense; I couldn't find a similar post. Thanks for your time.
  6. hi again I found the thread I couldn't find yesterday (sorry) http://www.minecraftforge.net/forum/index.php/topic,10445.0.html . there has been some discussion on mcforum about this as well - i'm code illiterate so I hope this helps. thanks again.
  7. Hi - as far as I can gather this is probably a Mojang problem - something about the order of events on restart and mod key binds being wiped and reset to default - but I saw on mcforum that ModLoader (the other one) has a patch for this. I was wondering (and hoping) that maybe someone had done something similar for forge? Resetting keys every time the game starts is getting old. I guess you already have enough to do... thanks for your time.
  8. I saw the thread about "do not create coremods folder" but my forge version (auto-install.762 for 161) has a coremods folder and I put the treecapitator coremod in there and it works ok. So to clarify please: should I put treecap. and others in the mods folder now? thanks
  9. thanks for answering, this must be a busy time, I get what you say about the launcher not pointing to the desired place. I guess the launcher will be better in future, I have tried to get answers on the mcforum and googled a lot - but i'd really like to know what is it about the auto forge installer that does restrict saves to the version it creates - could you maybe make an auto installer for 152? I have no idea how much work would be involved for you; or tell me how to adapt the installer to 152? The jar created by the installer looks very different to the one made manually. ed - took out a sentence that was in twice (I was tired ) Anyway, I'm being impatient I guess, Thanks again
  10. Hi forgers, I have been creating versions and directories (in appdata) ok and my saved worlds stay put until I install forge and then the saves revert to the main .minecraft saves whether they were created in 152 or 161. Put another way: all versions created by me in the main .minecraft directory have the same list of saves whatever the mc version is. If I create a new dir. say, <.minecraft forge> I can isolate a saved world there *until* I put forge into its jar, then I get the <.minecraft> saves the version I create with the forge installer doesn't have this problem; the saves stay put. I've tried a heap of different dir.s and versions and orders of doing stuff. so the forge installer does something I haven't been able to reproduce with my clueless shotgun approach. I would appreciate any help. thanks ed- this is for windows7, 3GB ram, java 7 (i'm new here so I hope this is in the right place and all)
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.