Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

EbeneezerSquid

Members
  • Posts

    5
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed
  • Personal Text
    I am new!

EbeneezerSquid's Achievements

Tree Puncher

Tree Puncher (2/8)

1

Reputation

  1. Disregard. it IS an Optifine bug. sorry to waste your time and board space.
  2. My Apologies, minecraftforge-universal-4.0.0.200 OptiFine_1.3.2_HD_U_B2 [1.3.2]ReiMinimap_v3.2_05 UniversalElectricity_v0.5.1 And forgotten in the post above, but should not be involved: BWG3_FORGE_109 (And I discovered that Crafting Table III, while it "installed" without crashing, doesn't work either, as it did not get updated, but got mislabeled somewhere making me think it had. Manually removing all mod files had no effect on the bug.) Should I cross-post into UE and Optifine forum threads? Not sure what is to blame for this. Will probably create a dozen copies of my gameworld to test every version of minecraft jar as I mod up later tonight.
  3. I'm running into an odd graphical bug, that I'm hoping someone has seen before. I'm not sure if Forge, FML, Optifine, UE, or rays from Saturn are responsible, or a combination. All of the Ores added by UE show up, when placed as blocks, as textures from terrain.png. Tin is a sapling (oak, i think), while copper is a portal (complete with animation). As soon as the block is broken, the "Item" version of the ore shows correctly. This occurs both with and without texture packs - I even created and added my own copper and tin textures and figured out where to put them in my custom texture pack thinking it could be a x16 - x64 texture issue, but no dice. I had something similar occur with Foliage where the new flowers used the old chest textures from terrain.png, and I reloaded my entire minecraft from scratch, and am getting this issue now. (I hadn't gotten down to the ores with Foliage so I cannot verify if the ores were changed then too.) While it is quite playable in this condition, it is rather immersion-breaking and ugly. Any ideas or suggestions? Edit: While normally played with multiple mods, running with only Forge, Optifine, UE, Crafting table III, and Rei's minimap results in the same error.
  4. the first test release should be out soon-ish, it depends on how much time lexmanos has available to finish porting to the new system & mc 1.3 Excuse me that i'm annoying,but what is the limit-day when Forge 1.3.1 is out?(approximately) I believe the more it is asked, the longer forge is gonna take. Stop asking already!
  5. On the Official Minecraft Forums, there is a user who is claiming Forge was updated to support 1.3.1 on Monday. I'm not seeing it here, is he off his rocker, or using a development build? I haven't seen any development builds in the forums, Github, or Jenkins, but I'm unfamiliar with either of the latter two. If he is completely off his rocker, someone may want to post a correction in the thread, as he is probably sending quite a few people on a scavenger hunt for the new Forge. http://www.minecraftforum.net/topic/227822-125-spmp-millenaire-npc-village-300r3-more-mp-bug-fixes/page__st__34460#entry17095518 Cheers! and thanks for all the hard work.
×
×
  • Create New...

Important Information

By using this site, you agree to our Privacy Policy.