Property visibility levels
Registered by
Erik Ogenvik
Currently all properties are visible for everyone. There's some preparation in place through the "visibility" element in the ruleset, but that's currently ignored.
We need to implement a system of visibility levels. There should be three levels:
"public": these properties are visible to all minds
"protected": these properties are only visible to the mind of the entity (things like "hunger")
"private": these properties are only visible to admin clients
The simulation should always have access to all properties though.
Blueprint information
- Status:
- Started
- Approver:
- Erik Ogenvik
- Priority:
- Medium
- Drafter:
- Erik Ogenvik
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Deployment
- Milestone target:
- None
- Started by
- Erik Ogenvik
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
The proposed solution is to use the naming of the property as key. A prefix of" _" means "protected", "__" means "private". All else is "public".
(?)
Work Items
Dependency tree
* Blueprints in grey have been implemented.
