Texture definitions fixed, now all from 16 to 256 are supported under the correct name
Added Dungeon Finding Needle. Unlike the Diamond Scan, this will only run after you moved a distance from your last scan location (if your minecraft seems to stop for a second this might be it scanning). Also different: It checks a lot more space below and above you. The green Needle will then point you toward the coordinates of the Mob Spawner inside the dungeon. Once you are at the coordinates (but wrong height), the needle will point up or down, indicating whether the dungeon is above or below you.
Just run around. Depending on which scanrange you installed, you need to travel an absolute(!) distance of 60 or 24 before the compass automatically scans 60 or 24 blocks in all directions for Mob Spawners.
Absolute means you cannot run in circles. You must leave one area to scan the next.
Note they are so rare you just might not be in range of one.
Also note, for performance reasons, there will be no scanning if you are above 60 Blocks (generally "surface level").
I wonder if i could make this dramatically more efficient, by hooking the 'entry' of a Block into the world instead of painstakingly looping all Blocks to find one of a kind.
Problem is Blocks get loaded as byte array ... which i have no idea how to use.
I got an error report and I change between files and everything but still getting an error.
java.lang.ArrayIndexOutOfBoundsException: 1024
at ai.a(TextureCompassFX.java:50)
at hf.a(SourceFile:230)
at net.minecraft.client.Minecraft.a(SourceFile:317)
at k.a(k.java:28)
at net.minecraft.client.Minecraft.run(SourceFile:632)
at java.lang.Thread.run(Thread.java:636)
I don't have a texture pack and the only mod I have installed is more ores.
I have tried to use the 16x16 and 32x32. I am including the other .class file too.
I wonder if i could make this dramatically more efficient, by hooking the 'entry' of a Block into the world instead of painstakingly looping all Blocks to find one of a kind.
Problem is Blocks get loaded as byte array ... which i have no idea how to use.
Coal finder
Iron finder
A button for reset
My suggestions :>
PS: I can have the SAME compass :> ? Because my compass don't show up or down... :\ I need that please I have a 32x texture pack
I got an error when I tried to play when I installed it. I used the 16 and 32 textures in the 7 scan folder.
java.lang.ArrayIndexOutOfBoundsException: Coordinate out of bounds!
at sun.awt.image.ByteInterleavedRaster.getDataElements(Unknown Source)
at java.awt.image.BufferedImage.getRGB(Unknown Source)
at ai.<init>(TextureCompassFX.java:25)
at net.minecraft.client.Minecraft.a(SourceFile:317)
at net.minecraft.client.Minecraft.run(SourceFile:632)
at java.lang.Thread.run(Unknown Source)
--- END ERROR REPORT 9bcc5803 ---------
I second the error reports from Stxyzth and ReicK, and further offer this information:
I use default textures, which i'm reasonably sure are 16x. I tried on a clean jar, just to be sure. I deleted META-INF. I did copy BlockCoord.class, as instructed.
I used scanrange_7/16_default_textures/ai.class and scanrange_15/16_default_textures/ai.class and got:
java.lang.ArrayIndexOutOfBoundsException: Coordinate out of bounds!
at sun.awt.image.ByteInterleavedRaster.getDataElements(Unknown Source)
at java.awt.image.BufferedImage.getRGB(Unknown Source)
at ai.<init>(TextureCompassFX.java:25)
at net.minecraft.client.Minecraft.a(SourceFile:317)
at net.minecraft.client.Minecraft.run(SourceFile:632)
at java.lang.Thread.run(Unknown Source)
...for both of them. Same message. Which was disouraging. The readme (you, YES YOU! READ ME NOW.txt) said (rather nonsensically) to use the 32_textures/ai.class if I didn't know what a texture was. I do know what a texture is, and actually understand how to change their size, but regardless, I tried 32_textures/ai.class just in case:
java.lang.ArrayIndexOutOfBoundsException: 1024
at ai.a(TextureCompassFX.java:50)
at hf.a(SourceFile:230)
at net.minecraft.client.Minecraft.a(SourceFile:317)
at net.minecraft.client.Minecraft.run(SourceFile:632)
at java.lang.Thread.run(Unknown Source)
A different error. Same for both again, though. Makes sense, really, considering I was using what I believe to be the wrong one. Odd that it says 1024, though, rather than what I would have expected, that being 16 (because 0 to 16 is 17 indexes -- one too many)
Not being a total noob, I decided to rip the thing apart. The code inside minecraft is rather abysmal as it's shipped (obfuscated), but I smashed around a little and found this odd variable declaration:
final int field_22004_texturesetting = 256;
...not that it appears to be actually used anywhere, I would have expected it to be 16 (for the 16_default_texture/ai.class, at least) regardless.
I have no idea what you did to your code, but it's quite clear to me that you broke it somewhere along the line. I hope you can figure it out, though, because I don't honestly have the time to get familiar enough with the minecraft codebase to work out a proper fix.
Wait, so this worked for me when using the default textures, but now that I have Misa's 64X64 realistic, I dont seem to have the blue line. I did use the .class from the 64 X 64 folder, so dont say I didnt do that. My minecraft works fine, I just dont seem to be getting any blue lines. There just might not be any nearby diamonds, but thats doubtable. Does the texture pack have to be made compatable for this mod?
Edit: Ive never been so unhappy to find diamonds in my life, but I found diamonds, and there was never any blue line... :sad.gif: So this basically conforms that the texture pack needs compatibility, unless im doing something wrong? Maybe I need to use the 7? Help me out here.
Edit: I found diamonds again, still no blue line. This is a rather ridiculous amount of diamonds to be getting WITHOUT the aid of the blue line . 11 in 20 seconds? hell yes.
The compass on this mod >_>
I have played Minecraft since July... last year I am pretty capable of crafting a compass....
it is the standard compass. your just not anywhere near a diamond.
And this is a WIN mod!
now $$$ < My $$$
[tnt] [tnt] [tnt]
[tnt] [DORE] [tnt]
[tnt] [tnt] [tnt]
Just do it...
LOL, that would be awesome.
Texture definitions fixed, now all from 16 to 256 are supported under the correct name
Added Dungeon Finding Needle. Unlike the Diamond Scan, this will only run after you moved a distance from your last scan location (if your minecraft seems to stop for a second this might be it scanning). Also different: It checks a lot more space below and above you. The green Needle will then point you toward the coordinates of the Mob Spawner inside the dungeon. Once you are at the coordinates (but wrong height), the needle will point up or down, indicating whether the dungeon is above or below you.
Added youtube video for the Dungeon Finder ^^
Absolute means you cannot run in circles. You must leave one area to scan the next.
Note they are so rare you just might not be in range of one.
Also note, for performance reasons, there will be no scanning if you are above 60 Blocks (generally "surface level").
Problem is Blocks get loaded as byte array ... which i have no idea how to use.
I don't have a texture pack and the only mod I have installed is more ores.
I have tried to use the 16x16 and 32x32. I am including the other .class file too.
EnviousHost MINECRAFT SERVERS - CHEAP - [FREE MUMBLE] [FREE WEBHOSTING] [ONE CLICK PLUGINS]
Why the he'll would you need a coal finder?
Someone had to say it.
Anyway, awesome mod!
I see. I was interested in the mod, just had not downloaded it.
I use default textures, which i'm reasonably sure are 16x. I tried on a clean jar, just to be sure. I deleted META-INF. I did copy BlockCoord.class, as instructed.
I used scanrange_7/16_default_textures/ai.class and scanrange_15/16_default_textures/ai.class and got:
...for both of them. Same message. Which was disouraging. The readme (you, YES YOU! READ ME NOW.txt) said (rather nonsensically) to use the 32_textures/ai.class if I didn't know what a texture was. I do know what a texture is, and actually understand how to change their size, but regardless, I tried 32_textures/ai.class just in case:
A different error. Same for both again, though. Makes sense, really, considering I was using what I believe to be the wrong one. Odd that it says 1024, though, rather than what I would have expected, that being 16 (because 0 to 16 is 17 indexes -- one too many)
Not being a total noob, I decided to rip the thing apart. The code inside minecraft is rather abysmal as it's shipped (obfuscated), but I smashed around a little and found this odd variable declaration:
...not that it appears to be actually used anywhere, I would have expected it to be 16 (for the 16_default_texture/ai.class, at least) regardless.
I have no idea what you did to your code, but it's quite clear to me that you broke it somewhere along the line. I hope you can figure it out, though, because I don't honestly have the time to get familiar enough with the minecraft codebase to work out a proper fix.
Good luck, man.
I kept checking the source for errors ... it didnt occur to me to check the files i distribute.
Now how in earth did that one get there ... in both folders too ... o_O i did fresh compiles for all files ... don't know.
I apologize for any inconvenience caused ._.
The file (and readme) are now fixed, i checked all files again to be certain.
As for SMP ... *checks* ... it will not work on online servers that mod the block IDs. I'll have a look how that works
Edit: Ive never been so unhappy to find diamonds in my life, but I found diamonds, and there was never any blue line... :sad.gif: So this basically conforms that the texture pack needs compatibility, unless im doing something wrong? Maybe I need to use the 7? Help me out here.
Edit: I found diamonds again, still no blue line. This is a rather ridiculous amount of diamonds to be getting WITHOUT the aid of the blue line . 11 in 20 seconds? hell yes.
Yes, of course. I'll try it again too.
...And to no avail. What else could be the problem?