This mod look amazingly beautiful. I wish he would re-continue i, plus that other guy he linked the mod to is not nearly as good looking (As in the mod).
Nooo please don't go!
I Love this mod, because I love dual wielding! I love all the work you put into this great mod! Please, do not let it's awesomeness get degraded into a shield mod I have no interest in ever using unless it eventually gets dual wielding too! PLEASE!I really want him to re-continue this, I really do! If there was a poll, I would click the hell out of the "re-continue" option.... Oh well...
Are you going to update the mod to newer minecraft versions (1.4.2 or 1.3.2)?
Did you read the title?
Rollback Post to RevisionRollBack
Let’s play good guys against bad guys… Yes. Let’s play that. Are you ready? You’re the bad guy. And when you’re bad, you just run. That’s fine right? Well… Shall we play?
i've got an experimental bit of content i was going to try out: if it works; could solve the slot problem
a "strapped vest": an item that is equipped in the body slot that includes it's own slots. armour, sheathe, quiver etc: and their remembered on the itemStack NBT
(it would just be a matter of sending a large packet) i've done something similar sending a packet containing individual chars in a string and it seemed to work(being a large number of integers)
It would actually be more values then that because of enchantments.
Lets work it out shall we.
Remember that in the Forge packet handling it is all stored in bytes (1 int = 4 bytes, 1 short = 2 bytes)
Per Item
1 value for itemID, max is ~4000 so can use a short (2 bytes)
1 value for damage, not sure what that max is so probably should use int (4 bytes)
Per Enchantments
1 value for enchantment id, max value is 255 so really need to use a short (2 bytes) *
1 value for level, only really need a byte (1 byte)
Now I am fairly sure that there is a maximum of 4 enchantments on default items (3*4=12 bytes)
This would mean that the total packet size for a slot would be 18 bytes.
If you had 4 slots + entity Id (int) that would make the packet size 58 bytes + the header (2 + 2 * channel length). Looking at the code, the maximum packet size is actually 32,767 (32 * (2^10 - 1)) so yeah you are well under and actually not that big.
This is also assuming that all the items need to support enchantments.
*You might be able to get away with using an unsigned byte (i.e. add 128 to the value). This would give you room for 254 enchantments plus 1 value for "no enchantment" This would make each slot 2*4 = 8 and the total packet size of 46 + header.
If you are confused about read/writing ints & shorts to/from byte[] just use a ByteBuffer. I can show you code if you need it.
i've noticed there's a "Packet104WindowItems"; this packet sends an itemstack array between containers: with some changes. a similar system could be used to share the slots:
aside from that. a container interface should be able to sync the data anyway. (as this packet is used when containers are used)
I'm just a wanderer.....
I'm prolbly bored and tired when I post so plz excuse me if I am bieng entirely stooped ty
I Love this mod, because I love dual wielding! I love all the work you put into this great mod! Please, do not let it's awesomeness get degraded into a shield mod I have no interest in ever using unless it eventually gets dual wielding too! PLEASE!I really want him to re-continue this, I really do! If there was a poll, I would click the hell out of the "re-continue" option.... Oh well...
CustomNpcs
The bug said it was fixed, but sadly I still have the issue: The custom inventory interface with the Aether mod is not right. Does anyone have a fix?
Probably the best Minecraft Mod ever made
We won't forget you...
Did you read the title?
a "strapped vest": an item that is equipped in the body slot that includes it's own slots. armour, sheathe, quiver etc: and their remembered on the itemStack NBT
(it would just be a matter of sending a large packet) i've done something similar sending a packet containing individual chars in a string and it seemed to work(being a large number of integers)
Lets work it out shall we.
Remember that in the Forge packet handling it is all stored in bytes (1 int = 4 bytes, 1 short = 2 bytes)
Per Item
If you had 4 slots + entity Id (int) that would make the packet size 58 bytes + the header (2 + 2 * channel length). Looking at the code, the maximum packet size is actually 32,767 (32 * (2^10 - 1)) so yeah you are well under and actually not that big.
This is also assuming that all the items need to support enchantments.
*You might be able to get away with using an unsigned byte (i.e. add 128 to the value). This would give you room for 254 enchantments plus 1 value for "no enchantment" This would make each slot 2*4 = 8 and the total packet size of 46 + header.
If you are confused about read/writing ints & shorts to/from byte[] just use a ByteBuffer. I can show you code if you need it.
aside from that. a container interface should be able to sync the data anyway. (as this packet is used when containers are used)
Such a shame, cause I was gonna Download the mod when 1.4 came out. 'sigh' oh well.
PS: Even if you don't update, please don't take down the 1.2.5 version, for the people willing to downgrade.