Mod idea: blocks for making racing events #6349
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#6349
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?
Could be just a "start" block that will start your timer and "finish" block that will stop the timer and show other people's times.
Can be activated by just punching them, but that will limit the uses.
I wanted to make an event where people have to stay above the floor as long as possible... would be nice if I can fill the bottom of the area with "stop" triggers (all connected to one "finish" block to keep time?)... In this case players should just pass through them to activate them (and land in water).
So, not sure what's the best implementation is...
this sounds like it'd be prone to lag, the same way that pipeworks detecting tubes aren't reliable when there's lag.
Kinda amazing that game engine does not have
moveresult
analog for players...But if entity is attached to a player, could that work as a sensor for nodes? Could work for pressure plates too maybe?
meh, if entity is attached, moveresult does not have collision info...
https://github.com/minetest/minetest/issues/13541 (and a few issues linked therein)
attached objects (players and entities) should assume very little - e.g. their position and drawscale are controlled by their parent, not by anything they can control. those values lie when you're attached, but you can at least query your parent.. but there's also no easy way to figure out your position even if you know your parent.