Assuming you are trying to make the TC broadsword compatible with the ZSS skills and are adding the entry to the ZSS Weapon Registry config, you need to use the TC Broadsword's registry name.
Registry names should always be completely lowercase and in the format 'mod_id:item_name', e.g.: `tconstruct:broadsword`.
You can test it out without restarting constantly by using the ZSS Weapon Registry command. See the manual for an explanation.
Trying to mess around with adding the tinker swords and can't get it to work here either...thinking it's cause the item itself is named after what it's made out of? Either that or I'm misspelling something and just can't figure it out.
So `zssweaponregistry allow sword tconstruct:broadsword` is not working? How are you testing it? As far as I can tell from the TC source code on GitHub, that should be the correct name to use...
Does that happen to you often? I can't say I've ever experienced that myself, but it doesn't sound found. Have you tried modifying the spawn rate?
Usually in the Nether. It's not so common that I need to modify the spawn rate. In the Overworld, I usually get to become better acquainted with Thunder Keese.
The Meaning of Life, the Universe, and Everything.
Join Date:
10/5/2016
Posts:
48
Member Details
The game crashed whilst unexpected error
Error: java.lang.IllegalArgumentException: Cannot get property PropertyInteger{name=power, clazz=class java.lang.Integer, values=[0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15]} as it does not exist in BlockState{block=minecraft:lit_redstone_ore, properties=[]}
I'm using the 1.8 version because a lot of mods I have don't have a 1.8.9 version. But, whenever I interact with redstone, it breaks the game. Can you update the 1.8 version to have what the 1.8.9 version has and fix this bug? I love this mod but, this is a pain.
That was all it gave me. Where can I find more info on the crash?
When it crashes, there should be a whole ton of output in the launcher console. If the console isn't open, edit your profile to keep it open when you launch Minecraft.
Copy the entire contents of that console once you get the game to crash and put it in a spoiler or on pastebin and put the link here.
The Meaning of Life, the Universe, and Everything.
Join Date:
10/5/2016
Posts:
48
Member Details
Ok, I did a bit of testing. The problem was not your mod. It was actually NEI which surprised me. I apologize for blaming your mod. Quick tip for anyone reading this: if you want to use NEI for 1.8, download the latest version, not the recommended. Also, I still would love it if you were to continue updating the 1.8 version of this mod. Such an amazing mod. And even better now that I realize it wasn't your mod. Again, sorry about that.
So `zssweaponregistry allow sword tconstruct:broadsword` is not working? How are you testing it? As far as I can tell from the TC source code on GitHub, that should be the correct name to use...
It says 'Could not find item broadsword for mod tconstruct'
This is from 1.7.10 if that helps, not sure if Tinkers Construct changed their item naming system for the newer versions or something weird.
It says 'Could not find item broadsword for mod tconstruct'
This is from 1.7.10 if that helps, not sure if Tinkers Construct changed their item naming system for the newer versions or something weird.
Try enabling the advanced tooltips in Minecraft and see if that shows you the item's registered name (I don't recall off the top of my head).
If it doesn't, you can either scour through the 1.7.10 branch of TC's GitHub page, or try installing a mod that does show you the item registry names. Another option might be to look at TC's language file and try whatever you find there for the broadsword.
@VirusMonnoroth - Glad you got it sorted. No, I won't be updating the 1.8.0 version of the mod any further. 1.8.0 has died, just as 1.7.2 did, and mods that don't update past that will get left behind. That's just the way of Minecraft. :\
@VirusMonnoroth - Glad you got it sorted. No, I won't be updating the 1.8.0 version of the mod any further. 1.8.0 has died, just as 1.7.2 did, and mods that don't update past that will get left behind. That's just the way of Minecraft. :\
Aww. Ok. What is the next version you have planned? Also, Can you at least fix the funky shields when in BG2?
Aww. Ok. What is the next version you have planned? Also, Can you at least fix the funky shields when in BG2?
I will only be doing major Minecraft versions from here on out, so 1.8.9, 1.9.4, 1.10.2, etc. Right now I am still working out some issues in 1.8.9 as well as adding some final features for the currently supported versions.
In the case of shields, that was a problem introduced by the work-in-progress rendering systems of 1.8.0 and the earlier Forge versions; I was able to fix it in 1.8.9 because the rendering system has finally been sorted out. In other words, it may not even be fixable in 1.8.0.
Besides that, since I have very limited time to work on mods, it would be prudent to only devote time to supporting the Minecraft versions that are commonly played. As such, I will continue to support 1.7.10 as well as 1.8.9 for the time being, but after this next set of new features I will not be back-porting any additional new features that may be introduced in 1.9.4 or up - it is simply too time-consuming to keep supporting multiple versions.
I will only be doing major Minecraft versions from here on out, so 1.8.9, 1.9.4, 1.10.2, etc. Right now I am still working out some issues in 1.8.9 as well as adding some final features for the currently supported versions.
In the case of shields, that was a problem introduced by the work-in-progress rendering systems of 1.8.0 and the earlier Forge versions; I was able to fix it in 1.8.9 because the rendering system has finally been sorted out. In other words, it may not even be fixable in 1.8.0.
Besides that, since I have very limited time to work on mods, it would be prudent to only devote time to supporting the Minecraft versions that are commonly played. As such, I will continue to support 1.7.10 as well as 1.8.9 for the time being, but after this next set of new features I will not be back-porting any additional new features that may be introduced in 1.9.4 or up - it is simply too time-consuming to keep supporting multiple versions.
I will only be doing major Minecraft versions from here on out, so 1.8.9, 1.9.4, 1.10.2, etc. Right now I am still working out some issues in 1.8.9 as well as adding some final features for the currently supported versions.
In the case of shields, that was a problem introduced by the work-in-progress rendering systems of 1.8.0 and the earlier Forge versions; I was able to fix it in 1.8.9 because the rendering system has finally been sorted out. In other words, it may not even be fixable in 1.8.0.
Besides that, since I have very limited time to work on mods, it would be prudent to only devote time to supporting the Minecraft versions that are commonly played. As such, I will continue to support 1.7.10 as well as 1.8.9 for the time being, but after this next set of new features I will not be back-porting any additional new features that may be introduced in 1.9.4 or up - it is simply too time-consuming to keep supporting multiple versions.
so long as you get the rupees and the wallets in 1.7.10, i'll be happy. I have a few mods that don't seem to be updating past 1.7.10....and at least one dead mod...sigh.
so long as you get the rupees and the wallets in 1.7.10, i'll be happy. I have a few mods that don't seem to be updating past 1.7.10....and at least one dead mod...sigh.
That's the version I'm coding them for initially (easier to update usually than back-port), so yes
Trying to mess around with adding the tinker swords and can't get it to work here either...thinking it's cause the item itself is named after what it's made out of? Either that or I'm misspelling something and just can't figure it out.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumSo `zssweaponregistry allow sword tconstruct:broadsword` is not working? How are you testing it? As far as I can tell from the TC source code on GitHub, that should be the correct name to use...
Usually in the Nether. It's not so common that I need to modify the spawn rate. In the Overworld, I usually get to become better acquainted with Thunder Keese.
Reminiscent of what, Minish Cap? I really like how those rupees look, so I adapted them into different colors, silver was a pain in the butt though.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI recommend Custom Chest Loot. Just change the "pot" file or whatever in the config.
Are you planning to update this mod to 1.10.2? Since it is becoming the new "stable" version. Sorry, if you said it somewhere and I miss it
You can change the loot dropping from jars and grass in the .cfg file.
im pretty sure you can toggle what drops from grass, not sure with jars doe.
The game crashed whilst unexpected error
Error: java.lang.IllegalArgumentException: Cannot get property PropertyInteger{name=power, clazz=class java.lang.Integer, values=[0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15]} as it does not exist in BlockState{block=minecraft:lit_redstone_ore, properties=[]}
I'm using the 1.8 version because a lot of mods I have don't have a 1.8.9 version. But, whenever I interact with redstone, it breaks the game. Can you update the 1.8 version to have what the 1.8.9 version has and fix this bug? I love this mod but, this is a pain.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumYou're going to have to post the whole crash report, preferably in spoilers or on pastebin.
That was all it gave me. Where can I find more info on the crash?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumWhen it crashes, there should be a whole ton of output in the launcher console. If the console isn't open, edit your profile to keep it open when you launch Minecraft.
Copy the entire contents of that console once you get the game to crash and put it in a spoiler or on pastebin and put the link here.
Ok, I did a bit of testing. The problem was not your mod. It was actually NEI which surprised me. I apologize for blaming your mod. Quick tip for anyone reading this: if you want to use NEI for 1.8, download the latest version, not the recommended. Also, I still would love it if you were to continue updating the 1.8 version of this mod. Such an amazing mod. And even better now that I realize it wasn't your mod. Again, sorry about that.
It says 'Could not find item broadsword for mod tconstruct'
This is from 1.7.10 if that helps, not sure if Tinkers Construct changed their item naming system for the newer versions or something weird.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumTry enabling the advanced tooltips in Minecraft and see if that shows you the item's registered name (I don't recall off the top of my head).
If it doesn't, you can either scour through the 1.7.10 branch of TC's GitHub page, or try installing a mod that does show you the item registry names. Another option might be to look at TC's language file and try whatever you find there for the broadsword.
@VirusMonnoroth - Glad you got it sorted. No, I won't be updating the 1.8.0 version of the mod any further. 1.8.0 has died, just as 1.7.2 did, and mods that don't update past that will get left behind. That's just the way of Minecraft. :\
Aww. Ok. What is the next version you have planned? Also, Can you at least fix the funky shields when in BG2?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI will only be doing major Minecraft versions from here on out, so 1.8.9, 1.9.4, 1.10.2, etc. Right now I am still working out some issues in 1.8.9 as well as adding some final features for the currently supported versions.
In the case of shields, that was a problem introduced by the work-in-progress rendering systems of 1.8.0 and the earlier Forge versions; I was able to fix it in 1.8.9 because the rendering system has finally been sorted out. In other words, it may not even be fixable in 1.8.0.
Besides that, since I have very limited time to work on mods, it would be prudent to only devote time to supporting the Minecraft versions that are commonly played. As such, I will continue to support 1.7.10 as well as 1.8.9 for the time being, but after this next set of new features I will not be back-porting any additional new features that may be introduced in 1.9.4 or up - it is simply too time-consuming to keep supporting multiple versions.
Ok. Thank you. Either way, I still love this mod.
so long as you get the rupees and the wallets in 1.7.10, i'll be happy. I have a few mods that don't seem to be updating past 1.7.10....and at least one dead mod...sigh.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThat's the version I'm coding them for initially (easier to update usually than back-port), so yes