Well I found that I can get this mod to work if I set this to be a new item in the server config (running MCPC 172 r0.3 forge 1025-b38 on the server and client has forge 1025.). So with this change in the config for both client and server, I can make the compas and it will switch modes, however there are no needles that show up. If I do not change the config to make the finder compass a new item, I am not able to change modes at all. I just have the default compass with the default needle utilizing the same server. There are no errors, it just doesn't work.
I haven't seen this mentioned in my brief search, so I thought it might help some others out there who find themselves in my position. After adding FC to my mod folder, I entered a saved game where FC gave the messages for each Saved Setting, but no arrows appeared when near appropriate ore blocks. After a bit of investigating, I realized that the updated FC had not overwritten my existing config file, and the config file's inner syntax had changed. Once I edited my config to the proper syntax, everything worked beautifully. So, if you have an existing config file, replace or update it. One further hint: If you are testing to see if FC is detecting diamond ore properly, don't just drop a few diamond ore blocks in creative mode and look for a response. Odds are you would drop them at or above sea level, and FC will only find diamond ore within its naturally occurring range. Hope this helps out.
Hi um, maybe I'm just being a total idiot but...how do I change the needle setting thing? Is it supposed to be with a right click? Cuz that's not doing anything for me. I went underground and had like three needles (I assume this was the miner setting with iron, coal, and gold), but when I right clicked with it nothing changed. Honestly I just want to use it to find a stronghold, but I have no idea what I'm doing >.<; any help would be appreciated thanks.
The compass works great with the 3 pre-configured settings. I I'm using the M-Ore mod and was hoping FC could find two of the ultra-rare ores from that mod. While my setting addition's name shows up, none of the needles ever show up (just on my addition, they work fine on your settings). I copied the settings for the chest for the two ultra-rare ores, and added two of the more common ores as a test. None of the arrows show up at all. I'm using the correct block ID names but do I have to do anything special since those ores are from a mod?
That is 1.6.4 version? Are you SURE those blocknames are correct?
Sorry, I forgot that detail, it's for 1.7.2 with the current version of forge. I've triple checked the ore names, even copy/pasted them on the last attempt to be sure I didn't mess up capitalization. I also double checked the .class names against the texture names just in case there was some difference (there wasn't). This is the mod in question: http://www.minecraftforum.net/topic/1573550-172updatedm-ore-mod/
I'm sure my own stupidity is at fault, I just can't seem to see past it atm.
So I'm sitting at work, trying to get some custom needles to work. Some work, others don't. I'm not using any additional client side mods other than yours, and minimum requirements.
Setting:Iron Only - v3
NoEnderEyeNeedle
iron_ore:255:255:255:15:1:1:1:0 <-- Here's my problem. Was scanning only 1 block.
iron_block:255:255:255:15:1:1:100:0
15:255:255:255:15:1:1:100:0
Looking at your post above mine, does that mean I have to use minecraft: or something else? The 15 I added later thinking maybe iron_ore was broke for whatever reason. I'm not sure
I'm checking through the log file, and I don't see anything that stands out as an error.
The following entries do work: Setting:Sand Only
NoEnderEyeNeedle
sand:255:128:64:100:5:1:100:0
Setting:Diamond Only
NoEnderEyeNeedle
diamond_ore:0:128:255:15:1:1:100:0
Yes. Only the server side knows where the stronghold is. Ender Eyes get their navigational data from the server too.
EDIT: Singleplayer? Uhm in adventurer mode it should show up
Ah, I see. All three settings it came with, adventure mode included, have the no ender eye thing, so I guess I'll just delete that part for that one. Thank you ^.^
so messing with the config file for a good hour there seems to be some problems with 1.7 + new id system and finder compass... heres some things i tried.
but first of all i am using forge 1.7.2-10.12.0.1047
finder compass 1.7.2b ( from the changelog in the zip file)
various other mod
this line works: (just fill in the remaining things with reasonable numbers)
ALL MODS HAS OR NEED A PREFIX BUT this prefix is in the form of modname:MaybeSomeExtraStuff.blockname note the coloni got this info from using nei block id dump
IC2:blockCrop
IC2:blockBarrel
appliedenergistics2:tile.BlockCableBus
appliedenergistics2:tile.OreQuartz
appliedenergistics2:tile.OreQuartzCharged
appliedenergistics2:tile.BlockMatrixFrame
appliedenergistics2:tile.BlockQuartz
appliedenergistics2:tile.BlockFluix
are these correct? or what i am suppose to be using?idk but they work in game with /give myname ModName:FunnyClassName.BlockName
im guessing that the extra colon is messing up how the mod look for the item considering it is using the colon to break where ever there is a new paramater, although don't count on this being correct since i dont know how it was coded. if this is so, easy fix would be requiring all syntax to have the extra colon even vanilla items or replacing the syntax colon with something other character.
1.7.2c
fixed Config Parser being unable to deal with prefixes
fixed Config Parser running too early, being unable to find mod Blocks
added block ID dump to console/log if you have 'failed' block IDs in your config
improved behaviour when dealing with missing/partially broken config files
fixed Compass Tick not being executed in remote multiplayer mode
Here is the code I added (copy/pasted really):
Setting:M-Ore
//
NoEnderEyeNeedle
//
// Granite
BlockGranite:51:255:204:60:60:1:100:1
//
// - Silver Ore
SilverOre:184:138:0:60:60:1:100:1
//
// - Platinum Ore
PlatinumOre:255:125:155:25:2:1:100:0
//
// - Sapphire Ore
SapphireOre:26:255:26:25:2:1:100:0
Sorry, I forgot that detail, it's for 1.7.2 with the current version of forge. I've triple checked the ore names, even copy/pasted them on the last attempt to be sure I didn't mess up capitalization. I also double checked the .class names against the texture names just in case there was some difference (there wasn't). This is the mod in question: http://www.minecraftforum.net/topic/1573550-172updatedm-ore-mod/
I'm sure my own stupidity is at fault, I just can't seem to see past it atm.
**DISREGARD** - I found my problem.
So I'm sitting at work, trying to get some custom needles to work. Some work, others don't. I'm not using any additional client side mods other than yours, and minimum requirements.
Setting:Iron Only - v3
NoEnderEyeNeedle
iron_ore:255:255:255:15:1:1:1:0 <-- Here's my problem. Was scanning only 1 block.
iron_block:255:255:255:15:1:1:100:0
15:255:255:255:15:1:1:100:0
Looking at your post above mine, does that mean I have to use minecraft: or something else? The 15 I added later thinking maybe iron_ore was broke for whatever reason. I'm not sure
I'm checking through the log file, and I don't see anything that stands out as an error.
The following entries do work:
Setting:Sand Only
NoEnderEyeNeedle
sand:255:128:64:100:5:1:100:0
Setting:Diamond Only
NoEnderEyeNeedle
diamond_ore:0:128:255:15:1:1:100:0
EDIT: Singleplayer? Uhm in adventurer mode it should show up
Ah, I see. All three settings it came with, adventure mode included, have the no ender eye thing, so I guess I'll just delete that part for that one. Thank you ^.^
Is there any way at all it could point me toward my LAST DEATH SPOT? I'm dead (lol) serious.
but first of all i am using forge 1.7.2-10.12.0.1047
finder compass 1.7.2b ( from the changelog in the zip file)
various other mod
this line works: (just fill in the remaining things with reasonable numbers)
are these correct? or what i am suppose to be using?idk but they work in game with /give myname ModName:FunnyClassName.BlockName
im guessing that the extra colon is messing up how the mod look for the item considering it is using the colon to break where ever there is a new paramater, although don't count on this being correct since i dont know how it was coded. if this is so, easy fix would be requiring all syntax to have the extra colon even vanilla items or replacing the syntax colon with something other character.
fixed Config Parser being unable to deal with prefixes
fixed Config Parser running too early, being unable to find mod Blocks
added block ID dump to console/log if you have 'failed' block IDs in your config
improved behaviour when dealing with missing/partially broken config files