Throw a disc golf disc #11
Labels
No labels
animation
audio
blocked
bug report
controversial
documentation
easy
feature request
hard
medium
multiplayer
physics
ui
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Depends on
#10 Bake Rydskogens disc golf course
elsie/liuverse
Reference
elsie/liuverse#11
Loading…
Reference in a new issue
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?
Once the Rydskogens course is baked, the obvious thing is to let you play it.
A disc is a projectile with a lift-and-fade arc, released from a tee, and it
either reaches a basket or does not. There are 18 real holes with names.
Where it fits the existing architecture:
tick -- this is the one place where cheating would actually matter, because a
score is a score.
ClientMsgappends (per theClientMsg/ServerMsgrule: append, never reorder).
SceneSpecobject slot like a scooter, not baked geometry.liuverse-worldwith the rest of the engine-free simulation and is testablewithout a GPU.
Par per hole comes from the golf tags on the course relation if that gets baked;
the disc golf hole ways carry names but no par.
Requires #10 first.
Related
A physics engine changes one line of this: the disc stops being arithmetic and
becomes a body.
#112 collects the thrown-body work — a mass, a restitution and a friction,
paired with the material under it. Rydskogen is gravel and forest floor, so
the disc that lands in the trees and the disc that lands on the fairway are
the same throw onto two different friction coefficients.
What does not change is the scoring rule. "Reached the basket" is still a
comparison against the basket's position, and it is still owned by this issue.
What changes is that the disc can now miss for reasons that have nothing
to do with arithmetic: it hits a tree, it lands in the rough and stops short,
and it is thrown too flat to fade up at all. A disc golf hole that you can
throw badly is a hole; a hole that is one arithmetic test is a checkbox.
The wire side matches the other server-authoritative mechanics: the disc is a
body on the server, its state travels in a new
ServerMsgvariant appendedto the end, and the throw itself is a new
ClientMsgvariant. The discitself is a
SceneSpecobject slot, not baked geometry, exactly as thisissue already says.
Related: #110 the physics engine, #112 the shared thrown body.
Don't really care