Bla reports: staff command to tag a player ... #4214
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#4214
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?
Bla reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
Yes, would be very useful to mark some non-planters or some non-english-talkers.
for this you would have to know which language the people speak, how is that supposed to be implemented??
First of all the client info contains the selected language so its possible.
But thats not even necessary Boot just provided some use cases to my suggestion so the language info in that case would come from staff itself without any code needed.
ok so this becomes unnecessary for a programmer and this is a case for AliasAlredyTaken?
the client doesn't send the user's locale to the server; translation is done by giving the client all the translation files and sending a specially designed message that instructs the client on how to build a translation.
The question of the language will be solved elsewhere, this type of tagging is informational only and there are not automatisms involved.
A solution to this issue:
on_joinplayer
.minetest.get_player_information
lang_code = "fr", -- Language code used for translation
@flux Because this isn´t the first time.
I got no problem with being corrected but it would be nice if you would atleast check first.
In most clients, this lang_code isn't set. If it is, it does give indication at best, we cannot hardcore rely on it as it's a user set value. But since there's not much reason to not tell the truth about the language, we can at least guess that direction.
There is a Point 4 in #3323 (comment) to guess a client language. If need be, we should open another issue to discuss language guessing and leave this issue to the initial tag request.
I actually meant that in the sense that if communication as a bailiff (or staff) is difficult, then it is sometimes due to age (you can do little), but sometimes also due to the player's lack of English skills. This is exactly where a reference to the language would be useful. Otherwise, the origin can remain anonymous.
apologies, i did check first, i just searched for "locale" and not "lang_code". also, the translation stuff does happen client side and not server side, though this would allow it to happen server side as well. seems the only place this is used in the server's codebase is when filtering (searching) items in unified inventory.
/tag playerName farm (non-replanter)
/tag playerName language (watch for rude language)
/tag playerName watch (possible disrupter, cheater, etc. general watch them)
I know I brought this up like 7 months ago... but it wasn't a good idea. Fresh starts are a trademark of YL and I like it that way. If someone can't get themselves banned outright, then we don't need to treat them like some sorta criminal?
This along with my /ignore idea are not my finest moments.
I like the ignore command, if it needs adjustment, we should discuss that in a separate issue.
I also like the tag command, it doesn't mean we'll use it for negative stuff entirely. To the contrary, all staff actions are meant to protect the herd, help the person and so on.
I didnt suggest /tag just for negative stuff, that depends on what you use it for.
Base idea behind it was to give staff a simple helpful shared reminder/info tool.
i'd like to propose that certain commands automatically add a tag, e.g. granting/revoking privileges, jailing, kicking, and banning.
The basic premise works, staff and bailiff can add, list and remove tags. Using
yl_tags.add_player_tag(name, tag_message)
we could tap into yl_tags and add stuff automatically.this is live