How exactly is that relevant to what I said? I was saying that in response to adding things to the entity ID list as you add blocks on, but the blocks would be getting their IDs from the entity list, thus not being able to get the ID in the first place. I know what they are silly. :P
That would technically be easy to solve. Assuming we have a Map<LocalID,GlobalID> map [translates local IDs into the global ID] and a Map<GlobalID,LocalID> reverse [does the reverse of the previous Map, has no entry for GlobalIDs not present locally]
we still have over 1000, iirc we haven't got more than 600 yet, but remember this isn't just blocks, this is things like scrap that can't be placed.
Interesting... I believe on the wiki there are around 650 block IDs accounted for, not counting some of the new blocks in the last few updates that haven't been catalogued. I just didn't know how many we had left.
Just one problem with that. 11+8=19 the smallest power of two greater than 19 is 32, and 32-19=13. 13 entire bits remain unused internally when calculating, unlike the 5 unused bits right now. You didn't even double the amount of bits for the id, but more than doubled the junk-overhead. I personally would just put 5 of the 8 bits of the additional byte into the id. the others would go into orientation and the logic-bit, so they don't have to be mingled with to fit corners and other fully-rotateable blocks. Any leftover bits could maybe be turned into meta-flags.
Simple: all metaitems[regardless of type] share 1 single id. Only the meta structure stored outside of the item itself holds the types. Or do you want to stack a logbook with your helmet and a gun? :P
Can't metaitem stacks be "special" inventory entries, though? Like the multistacks, sort of, ish. The game could specially check metaitems when you try to stack them and if the types don't match the stack operation will cancel.
Not only types have to match, each metaitem also contains their own stats[in regards to handheld weapons]. Also, have fun stacking 2 logbooks with different text-content onto each other, erasing one of them :P
How exactly does the stacking system work? If I were to do stacking, I would simply have an array/list created whenever stacking happens. It wouldn't alter the metadata at all, just show them with a pretty number. :p
How exactly does the stacking system work? If I were to do stacking, I would simply have an array/list created whenever stacking happens. It wouldn't alter the metadata at all, just show them with a pretty number. :p
That is not how it works, because if you were to split the stack, how to determine which items end up in which stack?
Get count of array/list, use that divided by two rounded to an int to get the max number to take away. Go through each thingy in stack, and if the max to take hasn't been reached, then add that to the new stack. Once that's done, take away the number of items from the original stack. Simple. :p
The result of that can be fairly random, as the contents of the array might be unsorted. And if only 1 element is not the same as the others, and the player wants that specific element, in a stack of say, 500 items. Good luck searching.
Oh right, forgot, they're meta items which have more data. Oops :p
Since handheld weapons each store their own stats[the OPgun is just a rocketlauncher with a modified damage per shot tag AFAIK], pretty much all data of all the tags has to be displayed in the dropdown. Those can be many, but the number of items in the stack will be even greater[again, 500 items stack e.g.] Have fun searching for the 1 item you wish for in a stack of 499 other random items.
