I'm sorry, but I do not understand this. Could you explain? Do you mean a block with multiple names registered in the language registry?
No, it is nothing about the language registry.
Since I have backported the ore generation to MC 1.6.4, I have used the string format <mod id>:<unlocalized name> as a replacement of the string id in MC 1.7.2. While some mods may re-use block instances from other mods or even vanilla Minecraft, sometimes they will re-register the block instances with their mod id automatically assigned (to a different integer id, I guess). This phenomenon causes an error in the name vs block one-to-one mapping and crash the game in the construction of my ore generator class.
OnlySilver-1.6.6-1.7.2 & OnlySilver-1.6.6-1.6.4 are released!
- Fixed silver bow does not consume arrows.
- Updated textures for silver ore and silver ingot.
- Added the tool enum and armor enum to the API. (1.6.6-1.7.2)
Well, yet, but Diamond is a vanilla material, so I think it is fair to use that.
D
R
D
Diamond / Silver Rod / Diamond in the crafting grid, and then the new item "Diamond Capped Silver Rod". Perhaps put a lump of redstone or glowstone in the middle of the bow recipe "for power". It would all be Silver and vanilla materials.
And, by the time you get seven diamonds (the first three will go to your pickaxe, obviously, then four for the bow), a chest full of arrows is not an unreasonable expectation. It would not be overpowered. If the bow requires glowstone, then that means the player has either mined in the Nether, or beat a witch.
I have a little time to work in Eclipse this evening. I'm migrating Recycle Your Silver and Sterling & Black to the new API file (in "zot\onlysilver\api"). I always recommend "use the latest version", but what is the minimum version of Only Silver which has this file in the code?
I have a little time to work in Eclipse this evening. I'm migrating Recycle Your Silver and Sterling & Black to the new API file (in "zot\onlysilver\api"). I always recommend "use the latest version", but what is the minimum version of Only Silver which has this file in the code?
OnlySilver-1.6.8-1.7.2 & OnlySilver-1.6.8-1.6.4 are now online!
- Fixed FOV retraction on bow use.
- Tweaked mob equip spawning.
- Added optional Akkamaddi Style mob equip spawning.
- Items and blocks would now automatically search a blank id to assign to. (1.6.8-1.6.4)
OnlySilver-1.6.8-1.7.2 & OnlySilver-1.6.8-1.6.4 are now online!
- Items and blocks would now automatically search a blank id to assign to. (1.6.8-1.6.4)
If you have an existing config file, will Only Silver continue to use the ID's you have assigned?
OK, so... we should back up our config file, and re-assign the ID's? (I just do not want my stash of silver to disappear.)
The id is changing only when there is an id collision involving OnlySilver, i.e. no need to care if you do not change your settings or combination of mods, but backing up your config is always a good idea.
EDIT:
Maybe I should better revert this feature to reduce accidents. How do you think about it?
EDIT:
Maybe I should better revert this feature to reduce accidents. How do you think about it?
Do you mean "turn it off" to reduce accidents?
Can you use a Boolean value to turn it on?
My concern is that when Only Silver updates any class file, or the proxy file moves, Minecraft will show an "item mismatch". Only Silver decides to change the ID's of silver things, then someone could suddenly have the silver items purged from their game. (These are among the many reasons to regularly back up your game save folder, and the config files.)
However, if someone is adding Only Silver, then your system to carefully assign ID's would be wonderful.
I'm not sure an easy way to do this (especially across multiple computer operating systems), but it would be good if "If OnlySilver.cfg exists, do nothing | if OnlySilver.cfg does not exist, run ID assignment." Otherwise, you could make it a Boolean, and say in the description:
If you are adding Only Silver, and get an ID conflict, go to the config file and set "Use ID Sorter=false" to true. Only Silver will try to assign the items and blocks to unused ID's. This can change any or all existing item and block ID's, so be very careful using this if Only Silver has been in use already.
Also.... this should all go away for 1.7.
(Please forgive my excessive use of smiley faces.)
Also, you may find this interesting:
I was trying to be useful in another thread. Someone got an "out of bounds" error from ore generation.
Someone else said that they used IDFixer and IDFixer Light, and found it far more trouble than it is worth. Apparently, these ID fixing mods identify "ID numbers" as number over a certain size. Someone said that the problem he had was it set the spawn height of some ores to 4096.
The latest version of Only Silver will break my "Sterling & Black" 1.3.0a. TheOldOne (thank you) found a stray import to the Only Silver's old API file in the main class file. (The recipe class file had already been converted.) I have re-packaged Sterling & Black, and tested it with my live game, along with Only Silver 1.6.8.
The current Recycle Your Silver is already converted.
I have put that the newest Only Silver may change IDs in an old config, but finally I recognized that I have remembered it wrong. Actually an attempt to use a free ID would only occur when a config entry does not exist, which would be the case that you do not have a config in your folder, or you have an old config with some parts deleted(*). In short, this new feature affects only initial IDs, old users would have almost nothing to take care about it.
* A technique to reset the config partially, remaining only those parts you want to keep.
- Fixed a crash occurs whenever a block with multiple names being loaded.
- Added the tool enum and armor enum to the API.
Only Silver: OnlySilver-1.6.5-1.6.4
"Only Developer's Silver": OnlySilver-src-1.6.5-1.6.4
I'm sorry, but I do not understand this. Could you explain? Do you mean a block with multiple names registered in the language registry?
No, it is nothing about the language registry.
Since I have backported the ore generation to MC 1.6.4, I have used the string format <mod id>:<unlocalized name> as a replacement of the string id in MC 1.7.2. While some mods may re-use block instances from other mods or even vanilla Minecraft, sometimes they will re-register the block instances with their mod id automatically assigned (to a different integer id, I guess). This phenomenon causes an error in the name vs block one-to-one mapping and crash the game in the construction of my ore generator class.
- Fixed silver bow does not consume arrows.
- Updated textures for silver ore and silver ingot.
- Added the tool enum and armor enum to the API. (1.6.6-1.7.2)
Only Silver:
OnlySilver-1.6.6-1.7.2
OnlySilver-1.6.6-1.6.4
"Only Developer's Silver":
OnlySilver-src-1.6.6-1.7.2
OnlySilver-src-1.6.6-1.6.4
Actually, you could make an "advanced silver bow" (perhaps silver rods capped with diamonds), where that is a feature.
Diamond Capped Silver Bow
+Infinity
Much more than only silver, lol.
Well, yet, but Diamond is a vanilla material, so I think it is fair to use that.
D
R
D
Diamond / Silver Rod / Diamond in the crafting grid, and then the new item "Diamond Capped Silver Rod". Perhaps put a lump of redstone or glowstone in the middle of the bow recipe "for power". It would all be Silver and vanilla materials.
And, by the time you get seven diamonds (the first three will go to your pickaxe, obviously, then four for the bow), a chest full of arrows is not an unreasonable expectation. It would not be overpowered. If the bow requires glowstone, then that means the player has either mined in the Nether, or beat a witch.
It's just an idea.
I have a little time to work in Eclipse this evening. I'm migrating Recycle Your Silver and Sterling & Black to the new API file (in "zot\onlysilver\api"). I always recommend "use the latest version", but what is the minimum version of Only Silver which has this file in the code?
Thank you.
- Fixed FOV retraction on bow use.
- Tweaked mob equip spawning.
- Added optional Akkamaddi Style mob equip spawning.
- Items and blocks would now automatically search a blank id to assign to. (1.6.8-1.6.4)
Only Silver:
OnlySilver-1.6.8-1.7.2
OnlySilver-1.6.8-1.6.4
"Only Developer's Silver":
OnlySilver-src-1.6.8-1.7.2
OnlySilver-src-1.6.8-1.6.4
If you have an existing config file, will Only Silver continue to use the ID's you have assigned?
P.S.
In addition, the new id generated will replace the old *ahem* one in the config.
The id is changing only when there is an id collision involving OnlySilver, i.e. no need to care if you do not change your settings or combination of mods, but backing up your config is always a good idea.
EDIT:
Maybe I should better revert this feature to reduce accidents. How do you think about it?
Do you mean "turn it off" to reduce accidents?
Can you use a Boolean value to turn it on?
My concern is that when Only Silver updates any class file, or the proxy file moves, Minecraft will show an "item mismatch". Only Silver decides to change the ID's of silver things, then someone could suddenly have the silver items purged from their game. (These are among the many reasons to regularly back up your game save folder, and the config files.)
However, if someone is adding Only Silver, then your system to carefully assign ID's would be wonderful.
I'm not sure an easy way to do this (especially across multiple computer operating systems), but it would be good if "If OnlySilver.cfg exists, do nothing | if OnlySilver.cfg does not exist, run ID assignment." Otherwise, you could make it a Boolean, and say in the description:
Also.... this should all go away for 1.7.
(Please forgive my excessive use of smiley faces.)
Also, you may find this interesting:
I was trying to be useful in another thread. Someone got an "out of bounds" error from ore generation.
Someone else said that they used IDFixer and IDFixer Light, and found it far more trouble than it is worth. Apparently, these ID fixing mods identify "ID numbers" as number over a certain size. Someone said that the problem he had was it set the spawn height of some ores to 4096.
Apparently, ID sorting does not always work well.
The current Recycle Your Silver is already converted.
I apologize for the inconvenience.
* A technique to reset the config partially, remaining only those parts you want to keep.