It seems I was happy too fast ;x Indeed, installer detect my version now, it even says "instalation successfully", but in controls I can't find it, and it have no response when I'm using any of xray keys
I'm very sorry for taking your time ;s
I've figured out the problem... The developers of Huzuni have obfuscated their code, and in doing so, restructured all of the Minecraft code. Unfortunately there's not much I can do to make it work.
Rollback Post to RevisionRollBack
Check out my XRay mod!
Forge compatible, configurable, and easily installable.
Click here for more information.
I'm putting out one more 'pre-release' before I put out an official release.
This way I get a chance to catch any bugs early. Downloads: 1.7.21.8
Here's the changelog for this version:
v2.14.0
- Made fullbright stay on if you toggle xray while fullbright is already on
- Made cave mode not automatically turn fullbright on
- Cave mode now shows lava and torches
- Restructured and cleaned up a lot of internal code
- Added XRay 'profiles'
- Added ability to exclude blocks in XRay config files
- Added ability to use a wildcard in XRay config files
- Added {X2}, {Y2}, and {Z2} options for `Coords.txt`
- Fixed two small performance bugs
- Added support for 1.8.1
Rollback Post to RevisionRollBack
Check out my XRay mod!
Forge compatible, configurable, and easily installable.
Click here for more information.
For some reason, Minecraft crashes after I logged in after I installed the your latest pre-release along with Optifine :/ Not sure if it's because I did something wrong though :x
For some reason, Minecraft crashes after I logged in after I installed the your latest pre-release along with Optifine :/ Not sure if it's because I did something wrong though :x
EDIT: It crashes even with just XRay installed
Are you using the 1.8 version or the 1.7.2? Can you post the crash log?
Rollback Post to RevisionRollBack
Check out my XRay mod!
Forge compatible, configurable, and easily installable.
Click here for more information.
at bsu.aj(SourceFile:447)
at bsu.a(SourceFile:299)
at net.minecraft.client.main.Main.main(SourceFile:120)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Stacktrace:
at bsu.aj(SourceFile:447)
-- Initialization --
Details:
Stacktrace:
at bsu.a(SourceFile:299)
at net.minecraft.client.main.Main.main(SourceFile:120)
-- System Details --
Details:
Minecraft Version: 1.8
Operating System: Windows 8.1 (x86) version 6.3
Java Version: 1.8.0_25, Oracle Corporation
Java VM Version: Java HotSpot(TM) Client VM (mixed mode), Oracle Corporation
Memory: 94861776 bytes (90 MB) / 168955904 bytes (161 MB) up to 523501568 bytes (499 MB)
JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx512M -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
Launched Version: 1.8-XRay
LWJGL: 2.9.1
OpenGL: GeForce GT 620/PCIe/SSE2 GL version 4.4.0 NVIDIA 344.11, NVIDIA Corporation
GL Caps: Using GL 1.3 multitexturing.
Using GL 1.3 texture combiners.
Using framebuffer objects because OpenGL 3.0 is supported and separate blending is supported.
Shaders are available because OpenGL 2.1 is supported.
VBOs are available because OpenGL 1.5 is supported.
Using VBOs: No
Is Modded: Very likely; Jar signature invalidated
Type: Client (map_client.txt)
Resource Packs: []
Current Language: English (UK)
Profiler Position: N/A (disabled)
at bsu.aj(SourceFile:447)
at bsu.a(SourceFile:299)
at net.minecraft.client.main.Main.main(SourceFile:120)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Stacktrace:
at bsu.aj(SourceFile:447)
-- Initialization --
Details:
Stacktrace:
at bsu.a(SourceFile:299)
at net.minecraft.client.main.Main.main(SourceFile:120)
-- System Details --
Details:
Minecraft Version: 1.8
Operating System: Windows 8.1 (x86) version 6.3
Java Version: 1.8.0_25, Oracle Corporation
Java VM Version: Java HotSpot(TM) Client VM (mixed mode), Oracle Corporation
Memory: 94861776 bytes (90 MB) / 168955904 bytes (161 MB) up to 523501568 bytes (499 MB)
JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx512M -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
Launched Version: 1.8-XRay
LWJGL: 2.9.1
OpenGL: GeForce GT 620/PCIe/SSE2 GL version 4.4.0 NVIDIA 344.11, NVIDIA Corporation
GL Caps: Using GL 1.3 multitexturing.
Using GL 1.3 texture combiners.
Using framebuffer objects because OpenGL 3.0 is supported and separate blending is supported.
Shaders are available because OpenGL 2.1 is supported.
VBOs are available because OpenGL 1.5 is supported.
Using VBOs: No
Is Modded: Very likely; Jar signature invalidated
Type: Client (map_client.txt)
Resource Packs: []
Current Language: English (UK)
Profiler Position: N/A (disabled)
Looks like that was a dumb mistake on my part, I've fixed it and reuploaded them. Could you try redownloading? Same link.
Rollback Post to RevisionRollBack
Check out my XRay mod!
Forge compatible, configurable, and easily installable.
Click here for more information.
Feedback: As far as FML, your current updated beta is looking good at initial glance, although I didn't go through all of the features.
For 1.8 I have Forge Mod Loader (FML) 8.0.9.1016 installed, which loaded everything in my mods\1.8 folder including OptiFine_1.8.0_HD_U_B2, your xray beta, liteloader and several liteloader mods like the minimap mod_voxelMap_1.3.0_for_1.8. Now, if your mod could just make espresso! (...speaking of which, I plan on buying you a "cup of coffee" soon).
Thanks for everything, looking forward to your release.
One very minor thing to note, so I thought I'd mention it:
The new {X2}, {Y2}, {Z2} tags truncate to one decimal place when the second place value is a zero. For example, it will show 12.3 instead of 12.30, which causes any subsequent text on the line to move over by a space, which is mildly annoying when you have more than one coordinate displayed on the same line.
Interestingly, on the whole number values, it will show at least the first zero (it displays 63.0, instead of just 63), though it should ideally display 63.00.
If that's turns out to be too much of a pain to fix, then just truncating all values to one decimal place is fine. Two decimal places is probably excessive anyway. If anyone needs more than that, there's always the F3 screen.
One very minor thing to note, so I thought I'd mention it:
The new {X2}, {Y2}, {Z2} tags truncate to one decimal place when the second place value is a zero. For example, it will show 12.3 instead of 12.30, which causes any subsequent text on the line to move over by a space, which is mildly annoying when you have more than one coordinate displayed on the same line.
Interestingly, on the whole number values, it will show at least the first zero (it displays 63.0, instead of just 63), though it should ideally display 63.00.
If that's turns out to be too much of a pain to fix, then just truncating all values to one decimal place is fine. Two decimal places is probably excessive anyway. If anyone needs more than that, there's always the F3 screen.
That's an easy fix
Rollback Post to RevisionRollBack
Check out my XRay mod!
Forge compatible, configurable, and easily installable.
Click here for more information.
Color codes in the "Coords.txt" file still work fine for me.
Speaking of the coordinate file, is there a {Biome} tag or something to show the current biome? I tried it and it didn't work, so I'm guessing that doesn't exist. No big deal, just curious.
Hopefully soon. What I've released so far are pre-releases so people can test them out and report back any problems.
Forge compatible, configurable, and easily installable.
Click here for more information.
1.8.1 is out now as well. So many versions...
I didn't even release 1.8.1 was out
Guess i'll have to work on an update for that as well.
Forge compatible, configurable, and easily installable.
Click here for more information.
I've never heard of huzani before... could you PM me a download link? I'll see what I can do.
Forge compatible, configurable, and easily installable.
Click here for more information.
I've fixed the problem. The installer will now successfully detect Huzani. Download link here: 1.7.10
This is the pre-release of the latest version, so it has all the new features. I recommend updating it when I put out an
official release.
Note: I didn't test using XRay in Huzani. I just made it recognize it.
Let me know if you have any further issues.
Forge compatible, configurable, and easily installable.
Click here for more information.
I've figured out the problem... The developers of Huzuni have obfuscated their code, and in doing so, restructured all of the Minecraft code. Unfortunately there's not much I can do to make it work.
Forge compatible, configurable, and easily installable.
Click here for more information.
This way I get a chance to catch any bugs early. Downloads: 1.7.2 1.8
Here's the changelog for this version:
- Made fullbright stay on if you toggle xray while fullbright is already on
- Made cave mode not automatically turn fullbright on
- Cave mode now shows lava and torches
- Restructured and cleaned up a lot of internal code
- Added XRay 'profiles'
- Added ability to exclude blocks in XRay config files
- Added ability to use a wildcard in XRay config files
- Added {X2}, {Y2}, and {Z2} options for `Coords.txt`
- Fixed two small performance bugs
- Added support for 1.8.1
Forge compatible, configurable, and easily installable.
Click here for more information.
EDIT: It crashes even with just XRay installed
Are you using the 1.8 version or the 1.7.2? Can you post the crash log?
Forge compatible, configurable, and easily installable.
Click here for more information.
// Hi. I'm Minecraft, and I'm a crashaholic.
Time: 11/26/14 11:41 AM
Description: Initializing game
java.lang.VerifyError: Expecting a stackmap frame at branch target 15
Exception Details:
Location:
cll.a(Lbec;Ldt;Lard;Lciv;)Z @3: ifeq
Reason:
Expected stackmap frame at this location.
Bytecode:
0x0000000: b200 ad99 000c 2bb8 00b1 9a00 0503 ac2b
0x0000010: b900 3d01 00b6 0024 3605 1505 02a0 0005
0x0000020: 03ac 1505 aa00 0000 0000 0043 0000 0001
0x0000030: 0000 0003 0000 0036 0000 0034 0000 001c
0x0000040: 2a2b 2d2c b600 2d3a 062a b400 202d 1906
0x0000050: 2b2c 1904 b600 33ac 03ac 2ab4 0022 2d2b
0x0000060: 2c19 04b6 0031 aca7 0037 3a05 1905 1202
0x0000070: b800 273a 0619 0612 01b6 0026 3a07 1907
0x0000080: 2c2b b900 3d01 002b b900 3d01 002b b600
0x0000090: 25b8 0038 bb00 1a59 1906 b700 3abf 03ac
0x00000a0:
Exception Handler Table:
bci [15, 33] => handler: 106
bci [34, 87] => handler: 106
bci [88, 89] => handler: 106
bci [90, 102] => handler: 106
Stackmap Table:
append_frame(@34,Integer)
chop_frame(@64,1)
full_frame(@88,{Top,Object[#7],Object[#21]},{})
full_frame(@90,{Object[#13],Object[#7],Object[#21],Object[#3],Object[#9]},{})
full_frame(@103,{},{})
full_frame(@106,{Top,Object[#7],Object[#21]},{Object[#25]})
chop_frame(@158,3)
at bsu.aj(SourceFile:447)
at bsu.a(SourceFile:299)
at net.minecraft.client.main.Main.main(SourceFile:120)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Stacktrace:
at bsu.aj(SourceFile:447)
-- Initialization --
Details:
Stacktrace:
at bsu.a(SourceFile:299)
at net.minecraft.client.main.Main.main(SourceFile:120)
-- System Details --
Details:
Minecraft Version: 1.8
Operating System: Windows 8.1 (x86) version 6.3
Java Version: 1.8.0_25, Oracle Corporation
Java VM Version: Java HotSpot(TM) Client VM (mixed mode), Oracle Corporation
Memory: 94861776 bytes (90 MB) / 168955904 bytes (161 MB) up to 523501568 bytes (499 MB)
JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx512M -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
Launched Version: 1.8-XRay
LWJGL: 2.9.1
OpenGL: GeForce GT 620/PCIe/SSE2 GL version 4.4.0 NVIDIA 344.11, NVIDIA Corporation
GL Caps: Using GL 1.3 multitexturing.
Using GL 1.3 texture combiners.
Using framebuffer objects because OpenGL 3.0 is supported and separate blending is supported.
Shaders are available because OpenGL 2.1 is supported.
VBOs are available because OpenGL 1.5 is supported.
Using VBOs: No
Is Modded: Very likely; Jar signature invalidated
Type: Client (map_client.txt)
Resource Packs: []
Current Language: English (UK)
Profiler Position: N/A (disabled)
Looks like that was a dumb mistake on my part, I've fixed it and reuploaded them. Could you try redownloading? Same link.
Forge compatible, configurable, and easily installable.
Click here for more information.
It works now. Thanks a lot man! I love using your mod so much
For 1.8 I have Forge Mod Loader (FML) 8.0.9.1016 installed, which loaded everything in my mods\1.8 folder including OptiFine_1.8.0_HD_U_B2, your xray beta, liteloader and several liteloader mods like the minimap mod_voxelMap_1.3.0_for_1.8. Now, if your mod could just make espresso! (...speaking of which, I plan on buying you a "cup of coffee" soon).
Thanks for everything, looking forward to your release.
One very minor thing to note, so I thought I'd mention it:
The new {X2}, {Y2}, {Z2} tags truncate to one decimal place when the second place value is a zero. For example, it will show 12.3 instead of 12.30, which causes any subsequent text on the line to move over by a space, which is mildly annoying when you have more than one coordinate displayed on the same line.
Interestingly, on the whole number values, it will show at least the first zero (it displays 63.0, instead of just 63), though it should ideally display 63.00.
If that's turns out to be too much of a pain to fix, then just truncating all values to one decimal place is fine. Two decimal places is probably excessive anyway. If anyone needs more than that, there's always the F3 screen.
That's an easy fix
Forge compatible, configurable, and easily installable.
Click here for more information.
Forge compatible, configurable, and easily installable.
Click here for more information.
?
It definitely did not get dropped, so it must be a bug.
Out of curiosity, are you using the "§" character, or "$"? You need to use "$" to avoid encoding issues (plus it's easier).
Forge compatible, configurable, and easily installable.
Click here for more information.
Speaking of the coordinate file, is there a {Biome} tag or something to show the current biome? I tried it and it didn't work, so I'm guessing that doesn't exist. No big deal, just curious.