ElvenEmpreror reports: An informal survey concluded ( ... #1082
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#1082
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?
ElvenEmpreror reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
...if we wanted to implement that, would that mean we would have to change the stack size of every single item? Or is there something like one master command to change that on a deeper level like changing the default for it?
I suspect that is a thing upstream
there is a setting for this:
1965628705/builtin/settingtypes.txt (L1150)
however, setting the stack max to 100 causes issues for players using small screens (phones) - the stack amounts extend into adjacent inventory cells.
also, there's some advantages to using a multiple of 9, as it makes it easy to evenly convert e.g. a stack of iron ingots into iron blocks, with nothing left over.
The small screen reason is valid, so is the "multpile of nine" one.
Also, I wouldn't be surprised if MT relied on stacks of 99 in one place or another. And if not MT itself, then most likely one of the bazillion mods.
Changing this would require extensive testing for little gain. Unless a very good reason crops up why we should do that, I'd say we won't fix.
MT engine does just fine w/ other stack sizes; the mods are a different story. I think I've fixed issues w/ non-standard stack sizes w/ e.g. unified_inventory_plus.