flux reports: use big ingots (ingots.big = t ... #2281
Labels
No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#2281
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
flux reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
not familiar with that one, could you explain what the difference would be?
reduce the node count for ingot piles from 704 to 88
EDIT: seems like brass doesn't have an ingot pile, so this would be from 640 to 80 (or 88 if we add brass ingots piles)
ah sounds good, ty
I'm an idiot that I hadn't thought of this before.
We could make an LBM that grabs the old block and places a protected chest instead which has nothing as content but the number of ingots this position had before, but meh. That's a stupid solution.
The big ingots even look better than the small ones IMO.
The setting is NOT in the minetest.conf, but in ingots/conf.lua
conf.is_big = true
that's one of my possible solutions, because it'd be easy to do.
the better solution would also be an LBM, which would transform stacks of > 8 ingots into a stack of 8, and store the number of "excess" ingots in metadata. players could remove the excess ingots by right-clicking. infotext (which displays in the HUD when you point at the node) could help users understand that their ingots haven't disappeared.
oh, looks like i added the setting when i updated the mod for blocky:
0a37675992
ah. i apparently forgot that i fixed that for blocky survival and not upstream:
0a37675992 (diff-d5faac49beea75d07295bef975287addbff4be76bcbe2899b94b6c781fd728c7)
@AliasAlreadyTaken if you approve this, i can update the mod and provide an ABM in yl_commons (or yl_integration, if we ever get there) that will convert the old ingot stacks into protected chests.
working on this. thought i'd knock it out in 30 minutes but i keep doofing it up.
implemented
ingots commits:
28c96a9ca5
and24d1c2f654
yl_commons commit:
125614b441
when the ingots mod is updated, and
ingots.big = true
in minetest.conf, then the routine in yl_commons will convert the ingots.this is partially reversible - if
ingots.big
is turned off, ingot stacks of 1-8 ingots will turn back into small ingot piles, but larger stacks, which turn intoyl_tools:protected_chest
s will remain as chests. if you think it's worth the effort, i could mark the chests w/ some node metadata and set up a system to revert those as well.The normally placed protected chests (the red ones) can't be opened by non-area owners.
The generated with the ingots can be opened by everyone. Demonstration on the Haven main square testserver.
interesting, i don't have the yl_tools mod so i couldn't test this. i'll try to figure out what the difference is.
That would be those: https://gitea.your-land.de/osmal/yl_tools
And guess what: There's no license. runs in circles, screaming
current update is
a93e97b9ff
in this update, the big 8-ingot stack has an inventory that can hold up to 56 ingots of the same type. anyone who could modify the ingot stack, can take/put nodes in the inventory. this also allows for full conversion of large ingots back to small ingots.
Maybe its too specific, but wouldn't upstream also benefit from a conversion back and forth?
i thought about that, i can't remember why i decided against it. i'll PR them w/ the code and see what happens.
ah, the reason is that the mod is a mess and i don't want to spend the time to clean it up to integrate the patch properly.
@AliasAlreadyTaken i think the code is live, but you need to set
conf.is_big = true
in minetest.confWill be in upon next restart.
@AliasAlreadyTaken i hope you realized i meant
ingots.big
instead ofconf.is_big
. the latter is something weird my brain seems to have made up O_OOf course! I totally put ingots.big instead of conf.is_big ... hahaha ... who would think conf.is_big is a valid setting?
sneaks off to change conf.is_big to ingots.big
When a player digs a pile of big ingots which has more ingots in its inventory, they only get the 8 big ingots, not the inventory.
Repro:
//load bugtracker2281
on the testserverExpected: The pile should not be diggable due to inventory OR you should have 38 ingots in your inventory
Is Wrong: You have 8 gold ingots in your inventory
w/ the following commit, they are undigable if they have inventory, and they'll drop the items if they are somehow destroyed.
faf5bf7757
this is live