mcrfpy.Entity repr lies #217

New issue

Closed

opened 2026-01-15 03:28:37 +00:00 by john · 0 comments

john commented

2026-01-15 03:28:37 +00:00

Owner

>>> e2
<Entity (grid_x=0, grid_y=0, sprite_index=0)>
>>> e2.pos
<Vector (5, 5)>

More associated weirdness. Why does an entity have to be associated with a grid to have its position assigned?

.pos is not accessible when not on a grid - can't be read or written. But the same position is applied when the entity is added to another grid, or back to the same. Position is a property on the entity... ...yet it's only accessible if the entity is on a grid.

Nominally, a position would be a property of the relationship between Entity and Grid. When removed from a grid, they'd truly be positionless. To be added to a grid, EntityCollection would also require a position value. But that's enormously complicated. Is this "can't access your own position element" really a good fit?

``` >>> e2 <Entity (grid_x=0, grid_y=0, sprite_index=0)> >>> e2.pos <Vector (5, 5)> ``` More associated weirdness. Why does an entity have to be associated with a grid to have its position assigned? `.pos` is not accessible when not on a grid - can't be read or written. But the same position is applied when the entity is added to another grid, or back to the same. Position is a property on the entity... ...yet it's only accessible if the entity is on a grid. Nominally, a position would be a property of the relationship between Entity and Grid. When removed from a grid, they'd truly be positionless. To be added to a grid, EntityCollection would also require a position value. But that's enormously complicated. Is this "can't access your own position element" really a good fit?