Arabella reports: a bug or a minor 'inconvenienc ... #826
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#826
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?
Arabella reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
I believe this issue can be closed as it looks like this feature has been added upstream as documented here and appears fixed on ingame on YL.
not fixed - has to be commas or spaces, not both:
Ok, I misunderstood the desired behavior. I can see how this is annoying.
Looking at the original code, the easiest fix I see is to handle the desired format using gsub to replace ', ' with ',' to convert the input to an acceptable format for pattern matching. Something like this:
local found, _, x, y, z = param:gsub(", ", ","):find("^(-?%d+)[, ](-?%d+)[, ](-?%d+)$")
This should handle using commas and/or spaces plus typos/combinations of both.
Are you looking to just override these chatcommands locally or need a PR for upstream or a fork of areas? I can pursue either if desired.
If it's not something yl-specific, then updating upstream is more desirable - it benefits not only us, and we have to resolve less conflicts when pulling upstream updates.
Upstream PR
I'll follow up if/when it is merged.
i feel like there's a better solution that allows for a comma, any space character (
%s
), or a single comma with any number of space characters before or after it.I would do it like this:
Allows any amount of spaces between anything.
Does not allow mixing commas and spaces (sanity check)