Cubyz
Cubyz copied to clipboard
PixelGuys
[Ore] Resin
This is a proposal to add resin ore to the game.
In game properties:
- naturally spawns as an ore on coniferous tree logs.
Modifiers
sticky- When you mine a block with a tool that has sticky modifier it does not drop item, instead item is placed directly into your inventory. #172
Spawn rules
0 < Z < 4000
Related to: #1269
I still think tree tappers are something to consider so that resin is something you have to work towards, instead of just finding on a tree. Then we could expand it to other trees, like harvesting sap or syrup from deciduous trees.
I agree with Carrie. Plus there's the idea of truffles, where you have to go digging around trees to find them.
Truffles and tapping are fundamentally different mechanics, first one is still basically searching for ores with strange spawn style, while the other is basically farming, you place a tap and you wait. I don't say it is bad, Its just something that is not yet present anywhere in Cubyz, so we are opening new domain - farming - and we don't have tools in engine for that yet.
Actually, there might be a clever way to get this done and handle dropping items when inventory is full using #1251 BlockDropLocation set to player position instead of broken block. We need to check tho if we need to remove velocity in such case so drops don't escape instead of getting picked up.
However what happens if another player stands in the same location?
We can no longer place resin ore on logs, so we need a different solution.
We could also do a carpet rotation, but it's directly on top of the block instead of being 1 pixel away from it. (don't worry I can fix the z-fighting)
Or we could also give rotation modes more bits and some control over the model.
Logs were supposed to also support stair rotation, we would need a lot of bits
And the last option would be to remap the old log variant back to rotation data 0.
Logs were supposed to also support stair rotation, we would need a lot of bits
We could afford an extra 32 I think.
But where do we store all the 4294967296 possible combinations of the data?
At this point we'd have to make model loading more dynamic, instead of as static as it is right now.
We could also do a carpet rotation, but it's directly on top of the block instead of being 1 pixel away from it. (don't worry I can fix the z-fighting)
This would be good enough i think
Updated my tree tapping issue #1384 with what I was suggesting on saturday (a seperate sappy log block)
