You should make the fusion furnace compatible with buildcraft, so you can pump items in and out of it.
You should also create steel. you should have a firing furnace, which would bake coal into coal coke and planks into ash. The ash would be combined with iron to create steel. the coal coke could be crushed in a crushing machine. the catalyst could be crushed charcoal, crushed coal or crushed coal coke.
Not sure if this is the right place to ask this, but is there a way to makeyou ores spawn in another mods dimension? And if so what steps would I have to take to make that happen?
I'm new to minecraft modding in genral but I do have experience with basic programming languages and have work with modding for various other games.
Also slightly related, but is there a way to make an ore from your mod, compatable with an ore from another? For example, your mod and another I use both add onyx and I would like to diable one form spawning, but stil able to use the other to make various htings with.
Any help, or pointing in the right direction would be greatly appreciated. (Also these will be for personal use and not distributed by any means apart from a personal freind or two)
Not sure if this is the right place to ask this, but is there a way to makeyou ores spawn in another mods dimension? And if so what steps would I have to take to make that happen?
The modding I intended this past weekend (and shopping and everything else) was largely crushed by a bout of insomnia, but I was actually planning something like this.
We may be moved to the plugin development thread, so I started the conversation there:
Suggestion: Make it so the Simpleores overworld ores spawn in custom dimensions?(Like the Twilight Forest or Mystcraft Ages?)
Sorry if its somthing already added in the 1.6 versions. :S
I should have some time on Thursday, and I will try to make some time this weekend. (Though, I've been told that I have plans. ) I've discussed trying to make a plug-in mod that replicates the ore generation, along with a separate config. I was thinking of having four lines in the case statement, initiating generation if the world ID equals one of four user-defined variables which will default to 9991, 9992, 9993, and 9994. The first three will be for the regular ore generation, the fourth will be for Onyx generation, in case there is a new Nether plane.
There will be a config file, and the values for ore generation will default to the same, but be configurable. This allows you to have Simple Ores rare or more common in higher dimensions, but the new config file would affect all higher dimensions the same.
Unless someone else can get this done faster, I will try to get this done this weekend. Once it works, I will do the same for zot201's Only Silver.
Edit: Oh, and your name just clicked. How's Narshe this time of year?
I should have some time on Thursday, and I will try to make some time this weekend. (Though, I've been told that I have plans. ) I've discussed trying to make a plug-in mod that replicates the ore generation, along with a separate config. I was thinking of having four lines in the case statement, initiating generation if the world ID equals one of four user-defined variables which will default to 9991, 9992, 9993, and 9994. The first three will be for the regular ore generation, the fourth will be for Onyx generation, in case there is a new Nether plane.
There will be a config file, and the values for ore generation will default to the same, but be configurable. This allows you to have Simple Ores rare or more common in higher dimensions, but the new config file would affect all higher dimensions the same.
Unless someone else can get this done faster, I will try to get this done this weekend. Once it works, I will do the same for zot201's Only Silver.
Edit: Oh, and your name just clicked. How's Narshe this time of year?
Why make the config affect all higher dimensions the same when they could have their own rates?
Why make the config affect all higher dimensions the same when they could have their own rates?
I was balancing "How many dimensions do I want to add?" vs. "How many dimensions do I want config files for?"
I don't know if the dimension ID number has an upper limit, but I know a co-workers FTB server has quite a few Myst Craft worlds. If it is an integer, and there is no cap like there is on ID values, then the potential number of dimensions is 2,147,483,647, minus 3 for the vanilla worlds, resulting in 2,147,483,644 possible worlds.
Each with a config file.
I think the correct answer is, "AleXndr, can you change the Mod to...".
If I stick with three or four, then yes, I supposed I could give the values extra designations. I am, of course, making the assumption that I can set the default values to a very high "place-holder space", so the user would have to set them to actually used world ID's.
The place holder for a second Onyx spawn will be 666. (Or 614.) That's probably what would be used anyway.
I was balancing "How many dimensions do I want to add?" vs. "How many dimensions do I want config files for?"
I don't know if the dimension ID number has an upper limit, but I know a co-workers FTB server has quite a few Myst Craft worlds. If it is an integer, and there is no cap like there is on ID values, then the potential number of dimensions is 2,147,483,647, minus 3 for the vanilla worlds, resulting in 2,147,483,644 possible worlds.
Each with a config file.
I think the correct answer is, "AleXndr, can you change the Mod to...".
If I stick with three or four, then yes, I supposed I could give the values extra designations. I am, of course, making the assumption that I can set the default values to a very high "place-holder space", so the user would have to set them to actually used world ID's.
The place holder for a second Onyx spawn will be 666. (Or 614.) That's probably what would be used anyway.
What you could do is have a config list of all ID's that you want the surface ores to spawn in, and all ID's you want the nether ores to spawn in. Then, all the user does is adds the dimension ID to the list (either for surface or nether), and then the generate function is run for all the ID's in that list. Probably eliminates being able to configure the rates, but would allow as many dimension IDs as the user has without you having to create new constructors for every single dimension.
What you could do is have a config list of all ID's that you want the surface ores to spawn in, and all ID's you want the nether ores to spawn in. Then, all the user does is adds the dimension ID to the list (either for surface or nether), and then the generate function is run for all the ID's in that list. Probably eliminates being able to configure the rates, but would allow as many dimension IDs as the user has without you having to create new constructors for every single dimension.
That is something I was wondering. The Forge tutorials show how to use the config files to set an integer. So, I figure I could so something like create world spawn integers wsAlpha, wsBeta, wsDelta, wsGamma, and nsAlpha (Nether Spawn). So, these five variables default to 99990 through 99995.
Now, is there a way to set an integer to something like ( 3 | 4 | 7), so each of the five variables could each be set to multiple dimensions? Five variables could be set to four config files: resource sparse; infrequent ores, large veins; frequent ores, small veins; resource rich; Nethers. Actually, make that six config files, and put "default" in the middle. Unless you wanted all five surface-world configurations *and* a world full of Creepers and Adamantium, those six config files could cover all your bases.
That is something I was wondering. The Forge tutorials show how to use the config files to set an integer. So, I figure I could so something like create world spawn integers wsAlpha, wsBeta, wsDelta, wsGamma, and nsAlpha (Nether Spawn). So, these five variables default to 99990 through 99995.
Now, is there a way to set an integer to something like ( 3 | 4 | 7), so each of the five variables could each be set to multiple dimensions? Five variables could be set to four config files: resource sparse; infrequent ores, large veins; frequent ores, small veins; resource rich; Nethers. Actually, make that six config files, and put "default" in the middle. Unless you wanted all five surface-world configurations *and* a world full of Creepers and Adamantium, those six config files could cover all your bases.
Any ideas on how the code would be handled?
That would require an array, rather than an int. I'm not sure how the Forge config handles arrays, if at all. You would be better off generating/including your own file that loads an array from a list of numbers ie. {10, 37, 4}. Those numbers would align to spawn rate, spawn height and vein size, etc.
That would require an array, rather than an int. I'm not sure how the Forge config handles arrays, if at all. You would be better off generating/including your own file that loads an array from a list of numbers ie. {10, 37, 4}. Those numbers would align to spawn rate, spawn height and vein size, etc.
I think I might have been unclear. The list of numbers would have been the dimensions that use a given file. What I was thinking was to create five config files (ignoring Nether for a moment), making the spawn rate and vein size: low / low, low / high, "vanilla", high / low, high / high. (Of course, these would all be adjustable in the config files. You could turn them into whatever you want.)
Then, if you have something like Myst Craft and create yourself a vast array of worlds, you just list the world ID values into the integers wsAlpha, wsBeta, wsVanilla, wsGamma, and wsDelta. If you create thirty worlds, you can list five of them under wsBeta so they have infrequent but high-yield veins, put two in wsDelta for high-yield worlds, etc., and the rest in wsVanilla.
Something like the case command would work here. If case of worldID equals a value of wsAlpha (and wsAlpha is one or five or fifteen different ID's registered in the config file), the world uses the wsAlpha resource-poor worldgen.
Also, wsVanilla would be the standard Simple Ores generation. Any worldID's not listed would use Minecraft's default (coal/iron/diamond) generation.
AleXndr, akkamaddi, just want to say thank you for all the great stuff you guys do with this mod. Love Simple Ores 2 & love all the plug-ins.
Rollback Post to RevisionRollBack
[Scott]: Things I have managed to get in the last five minutes, in order of ascending importance: cobblestone, planks, lapis lazuli, redstone, gold, coal, diamond. VERY LOST.
I have even more goodies in store for you all with the next version, including:
An integrated localisation! Yay! This means the SimpleOres names will change when you change your Minecraft language (provided that there is a language file for your language). There is a new toggle in the Settings file to enable the old localisation, so that you can easily set the names to silly things I haven't fully tested the toggle yet, but I'll get there.
An update to the Fusion Furnace so that it properly supports metadata, yay!
Somehow allow the Fusion Furnace to use OreDictionary recipes. There has got to be a way, but hopefully this doesn't turn out so difficult that it has to be pushed back.
Hopefully, an NEI plugin for the Fusion Furnace recipes.
I'm still looking into chests and anvils. While they probably won't be in this version, work on them has begun (in the form of a plugin).
I also looked into adding Horse Armor, but at the moment it doesn't look like there are any Forge hooks for it, so it won't be possible without base class edits, which I won't do.
I have even more goodies in store for you all with the next version, including:
An integrated localisation! Yay! This means the SimpleOres names will change when you change your Minecraft language (provided that there is a language file for your language). There is a new toggle in the Settings file to enable the old localisation, so that you can easily set the names to silly things I haven't fully tested the toggle yet, but I'll get there.
An update to the Fusion Furnace so that it properly supports metadata, yay!
Somehow allow the Fusion Furnace to use OreDictionary recipes. There has got to be a way, but hopefully this doesn't turn out so difficult that it has to be pushed back.
Hopefully, an NEI plugin for the Fusion Furnace recipes.
I'm still looking into chests and anvils. While they probably won't be in this version, work on them has begun (in the form of a plugin).
I also looked into adding Horse Armor, but at the moment it doesn't look like there are any Forge hooks for it, so it won't be possible without base class edits, which I won't do.
If you have any ideas, let me know
A way to get the ores in other Dimensions besides standard ones, like Mystcraft ages and the Twilight Forest. Oh and a +1 Rep cause I like the ideas.
[Scott]: Things I have managed to get in the last five minutes, in order of ascending importance: cobblestone, planks, lapis lazuli, redstone, gold, coal, diamond. VERY LOST.
You should also create steel. you should have a firing furnace, which would bake coal into coal coke and planks into ash. The ash would be combined with iron to create steel. the coal coke could be crushed in a crushing machine. the catalyst could be crushed charcoal, crushed coal or crushed coal coke.
I'm new to minecraft modding in genral but I do have experience with basic programming languages and have work with modding for various other games.
Also slightly related, but is there a way to make an ore from your mod, compatable with an ore from another? For example, your mod and another I use both add onyx and I would like to diable one form spawning, but stil able to use the other to make various htings with.
Any help, or pointing in the right direction would be greatly appreciated. (Also these will be for personal use and not distributed by any means apart from a personal freind or two)
The modding I intended this past weekend (and shopping and everything else) was largely crushed by a bout of insomnia, but I was actually planning something like this.
We may be moved to the plugin development thread, so I started the conversation there:
http://www.minecraftforum.net/topic/1937532-simpleores-2-plugin-development-thread/#entry24288543
Same speeds, much higher durability, I forget the specific numbers though.
Sorry if its somthing already added in the 1.6 versions. :S
Think I will be on here often? Haha no.
I should have some time on Thursday, and I will try to make some time this weekend. (Though, I've been told that I have plans. ) I've discussed trying to make a plug-in mod that replicates the ore generation, along with a separate config. I was thinking of having four lines in the case statement, initiating generation if the world ID equals one of four user-defined variables which will default to 9991, 9992, 9993, and 9994. The first three will be for the regular ore generation, the fourth will be for Onyx generation, in case there is a new Nether plane.
There will be a config file, and the values for ore generation will default to the same, but be configurable. This allows you to have Simple Ores rare or more common in higher dimensions, but the new config file would affect all higher dimensions the same.
Unless someone else can get this done faster, I will try to get this done this weekend. Once it works, I will do the same for zot201's Only Silver.
Edit: Oh, and your name just clicked. How's Narshe this time of year?
Why make the config affect all higher dimensions the same when they could have their own rates?
I was balancing "How many dimensions do I want to add?" vs. "How many dimensions do I want config files for?"
I don't know if the dimension ID number has an upper limit, but I know a co-workers FTB server has quite a few Myst Craft worlds. If it is an integer, and there is no cap like there is on ID values, then the potential number of dimensions is 2,147,483,647, minus 3 for the vanilla worlds, resulting in 2,147,483,644 possible worlds.
Each with a config file.
I think the correct answer is, "AleXndr, can you change the Mod to...".
If I stick with three or four, then yes, I supposed I could give the values extra designations. I am, of course, making the assumption that I can set the default values to a very high "place-holder space", so the user would have to set them to actually used world ID's.
The place holder for a second Onyx spawn will be 666. (Or 614.) That's probably what would be used anyway.
What you could do is have a config list of all ID's that you want the surface ores to spawn in, and all ID's you want the nether ores to spawn in. Then, all the user does is adds the dimension ID to the list (either for surface or nether), and then the generate function is run for all the ID's in that list. Probably eliminates being able to configure the rates, but would allow as many dimension IDs as the user has without you having to create new constructors for every single dimension.
That is something I was wondering. The Forge tutorials show how to use the config files to set an integer. So, I figure I could so something like create world spawn integers wsAlpha, wsBeta, wsDelta, wsGamma, and nsAlpha (Nether Spawn). So, these five variables default to 99990 through 99995.
Now, is there a way to set an integer to something like ( 3 | 4 | 7), so each of the five variables could each be set to multiple dimensions? Five variables could be set to four config files: resource sparse; infrequent ores, large veins; frequent ores, small veins; resource rich; Nethers. Actually, make that six config files, and put "default" in the middle. Unless you wanted all five surface-world configurations *and* a world full of Creepers and Adamantium, those six config files could cover all your bases.
Any ideas on how the code would be handled?
That would require an array, rather than an int. I'm not sure how the Forge config handles arrays, if at all. You would be better off generating/including your own file that loads an array from a list of numbers ie. {10, 37, 4}. Those numbers would align to spawn rate, spawn height and vein size, etc.
I think I might have been unclear. The list of numbers would have been the dimensions that use a given file. What I was thinking was to create five config files (ignoring Nether for a moment), making the spawn rate and vein size: low / low, low / high, "vanilla", high / low, high / high. (Of course, these would all be adjustable in the config files. You could turn them into whatever you want.)
Then, if you have something like Myst Craft and create yourself a vast array of worlds, you just list the world ID values into the integers wsAlpha, wsBeta, wsVanilla, wsGamma, and wsDelta. If you create thirty worlds, you can list five of them under wsBeta so they have infrequent but high-yield veins, put two in wsDelta for high-yield worlds, etc., and the rest in wsVanilla.
Something like the case command would work here. If case of worldID equals a value of wsAlpha (and wsAlpha is one or five or fifteen different ID's registered in the config file), the world uses the wsAlpha resource-poor worldgen.
Also, wsVanilla would be the standard Simple Ores generation. Any worldID's not listed would use Minecraft's default (coal/iron/diamond) generation.
AleXndr did the work, and provided some really useful advice.
I, on the other hand...
So direct your thanks to him.
A way to get the ores in other Dimensions besides standard ones, like Mystcraft ages and the Twilight Forest. Oh and a +1 Rep cause I like the ideas.
Mythril and Onyx versions of the Fusion Furnace?
Ooh, those would be pretty. Maybe a bronze one, too? The brick doesn't blend in with the rest of my forge equipment.
I'd like to put in a vote for sinisite bars or maybe a door. It's a pretty metal, and I'd like to decorate my Nether fortress with it.
I have been searching for a while, and haven't found any.