Define multiplayer learning rules
This commit is contained in:
@@ -573,3 +573,58 @@ Save/load rules:
|
||||
Persistence rule: learning state should make a returning character feel
|
||||
continuous while giving designers enough history to tune teaching, feedback, and
|
||||
anti-exploit behavior.
|
||||
|
||||
## Multiplayer Learning Rules
|
||||
|
||||
Learning in multiplayer should make cooperation valuable without turning nearby
|
||||
players into passive experience sources.
|
||||
|
||||
Teaching:
|
||||
|
||||
- The server validates teaching credit.
|
||||
- The teacher must know the concept, have enough practical experience, or
|
||||
demonstrate the action in the current context.
|
||||
- The learner must be nearby, attentive, and eligible for the concept.
|
||||
- Teaching grants bounded awareness or practice credit, not instant mastery.
|
||||
- Dangerous concepts require supervised practice before full confidence is
|
||||
awarded.
|
||||
|
||||
Observation:
|
||||
|
||||
- Nearby observation can unlock awareness of a concept when the action is
|
||||
visible and relevant.
|
||||
- Passive observation grants less credit than direct practice.
|
||||
- Repeated passive observation has diminishing returns.
|
||||
- Observation does not grant credit while idle, disconnected, hidden from the
|
||||
action, or outside the relevant range.
|
||||
|
||||
Shared work:
|
||||
|
||||
- Group tasks can grant role-specific experience to active contributors.
|
||||
- Roles should be explicit enough to audit later: gatherer, builder, fire
|
||||
watcher, first aid helper, scout, teacher, cook, hauler, or defender.
|
||||
- Failed group work can teach useful feedback when a player helps diagnose or
|
||||
correct the problem.
|
||||
- Idle proximity, item handoff spam, and repeated low-risk loops should not
|
||||
grant shared-work credit.
|
||||
|
||||
Group skill benefits:
|
||||
|
||||
- Skilled contributors can reduce risk, improve quality, increase speed, or
|
||||
make warnings more visible for the group task.
|
||||
- Benefits should be capped so one expert does not remove all challenge.
|
||||
- Benefits apply only while the contributor is present, equipped, and actively
|
||||
helping.
|
||||
- No global aura: skill benefits do not apply across the map or while logged
|
||||
off unless a future offline-simulation rule explicitly grants protection.
|
||||
|
||||
Network rules:
|
||||
|
||||
- Client learning requests are hints only.
|
||||
- Server authority validates distance, visibility, participation, role,
|
||||
cooldown, tools, environmental context, and outcome before granting credit.
|
||||
- Teaching, observation, and shared-work events must be persisted for tuning and
|
||||
anti-exploit review.
|
||||
|
||||
Multiplayer rule: cooperation should transfer awareness, improve group outcomes,
|
||||
and reward active contribution without bypassing practice, risk, or context.
|
||||
|
||||
Reference in New Issue
Block a user