Entity knowledge contents: make map data available directly through GridPointState #16
Labels
No Label
Alpha Release Requirement
Bugfix
Demo Target
Documentation
Major Feature
Minor Feature
priority:tier1-active
priority:tier2-foundation
priority:tier3-future
Refactoring & Cleanup
system:animation
system:documentation
system:grid
system:input
system:performance
system:python-binding
system:rendering
system:ui-hierarchy
Tiny Feature
workflow:blocked
workflow:needs-benchmark
workflow:needs-documentation
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: john/McRogueFace#16
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?
Notes say:
21 feat: Grid strict mode: Entity's GridPointState (discovered, visible) should include a point member: None if not discovered, a unmodified version of the GridPoint object if discovered but not visible, and a up-to-date GridPoint with
.entitiessub-member (entities at that visible GridPoint)atmethod returns a GridPointState ("gps") instance with these values:gps.discovered == False->gps.point == NoneNo knowledgegps.discovered == True && gps.visible == False->gps.pointis a GridPoint instance, but that instance has no.entitiescollection. It's also a copy of the GridPoint when it was last seen, not as it currently is.gps.visible == True->gps.pointis a GridPoint pointing at the Grid's vector, and includes a.entitiescollection of the Entities presently at that position (list of items, etc)this is being deferred as the capability can already be provided in Python: a subclass of Entity could store its own map data based on last visible state. I'm interested in providing the functionality natively, but it's going to be a while
john referenced this issue2025-11-26 10:23:53 +00:00