Bla reports: text can be colored in /msg ... #3922
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/petz
3. source/testserver
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/QA main
4. step/QA NOK
4. step/QA OK
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
No Milestone
No project
No Assignees
8 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#3922
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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:
need to correct, mrminer just told me he uses a command block and not /msg
Why do you want to remove this? It doesn't effect anything important, It just lets you color your DMs.
In order to recognize things as what they are, they need to have a color scheme that either the server or the recipient decides, not the sender.
And that you had to use a command block to achieve it because /msg blocks it should be a clear enough sign that it isn´t wanted.
upstream PR https://github.com/minetest-mods/MoreMesecons/pull/28
Fixed upstream
e72790f0eb
staff need colors to see problems and important info quickly, so server chat color control is not nothing. It's important and makes the people helping the server have an easier time of it. That said a color option for command blocks is bad? I usually miss anything they say cuz I'm not looking for chat when I typically run into one. meh.
that said, I can't confirm a command doesn't work if I never confirmed that it did... proving a negative if I never did a positive first or even know it exactly is not really possible but this appears to be fixed.
Read: missing repro. I tried to send myself a coloured DM, but failed.
tried
tell tour (c@#ee82ee)colored (c@#00FF00)text (c@#FFFF00)for (c@#FF7F00)the (c@#990012)test(c@#ffffff)
, found nothing bad. Means: sending colored text is no longer possible.tried
tell @nearest (T@default)Dirt
(invalid translation string) and things got crazy... especially when pointing at the command block you get a flood of errorsQA
per tour, the intial bug (coloured messages) is fixed. However, there are other strings, which we will report upstream.
Can't send colored messages from command blocks anymore, but invalid translation string gives me "Ignoring escape sequence" error. I see no issues about it upstream...
#7202
No issue on upstream bc. it's an engine bug. (Nearly all mods that display text input are affected)
That issue was even linked here...
Thanks tour :)
Closing this one.