AspireMint reports: [XP] Idea: similar to /coords ... #4158
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#4158
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?
AspireMint reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
I know we are not XP/level focused and don't want to obsess about it, but it would still be fun to look up if one wanted to know.
With yl_settings, the /info command will have a lot more information about a player. We need yl_settings so that each player can decide what they want to reveal about themselves.
...until the player uses the /bug command and ends up revealing all player-relevant data (apart from private messages and mails) here in the bugtracker for everyone to see?
notably, once yl_settings is around, player metadata won't contain a lot of the values it currently does.
Even with yl_settings there will still be player meta. Values players can alter themselves or need to be changed when a player is not logged in will go to yl_settings. More technical stuff a mod or mechanic needs to store on a player while online could still go to player meta, but yes, we'll most likely need to move some values to yl_settings