shanish reports: Right click a worn tool to rep ... #1757
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#1757
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?
shanish reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
I've had this exact same idea myself before, it wouldn't be hard to implement.
It only adds functionality and I can't see any drawbacks.
@AliasAlreadyTaken given that they haven't accepted by last PR for #1456, how do you want me to proceed? Is the server just pointed at https://github.com/fluxionary/minetest-anvil/tree/fix_hud_bug still?
As far as I can see the anvil points to the master branch of https://github.com/minetest-mods/anvil
I will mirror that repo, fork the mirror to the your-land org, then add a yl_stable branch and we can add the fix there. Then we're kinda independent of upstream. Should they ever get around to pull your fix, we can remove it from yl_stable.
Here's our fork: https://gitea.your-land.de/your-land/anvil.git
Please push your fix to yl_stable.
Why did we not do it this way from the very start? Because I was under the false impression that pulling those mods in from their original location would save us time. This proved wrong in all cases where such a mod needed a quick bugfix and where a githost of such a mod suddenly ceased working.
Here we're using our own version of the anvil:
e42038ded5
Pushed an update to yl_stable:
cdc3391253
This commit also fixes a number of other bugs and lays the groundwork for extending anvils as discussed in e.g. #1575, your-land/administration#44, your-land/administration#111
This is live