Add reproduction for inconsistent door-opening actions - #87
Conversation
Co-authored-by: MarcCote <660004+MarcCote@users.noreply.github.com>
|
@copilot check that recent changes in main fixes this issue. |
Checked |
No—this still reproduces on latest |
|
@copilot let's propose a fix for this then. ideally, without introducing breaking changes. |
…r-opening-inconsistency Co-authored-by: MarcCote <660004+MarcCote@users.noreply.github.com>
Co-authored-by: MarcCote <660004+MarcCote@users.noreply.github.com>
Implemented in |
| return this.name + " to " + connectsToContainer.get.name | ||
| } | ||
|
|
||
| return this.name + " from " + connectsFrom.name + " to " + connectsTo.name |
There was a problem hiding this comment.
@copilot when would that be used as a canonical referent? Give concrete example from playing ScienceWorld.
There was a problem hiding this comment.
There is no player-facing example. With easy/teleportAction, the all-universe referent LUT computes this fallback for remote doors (for example, door from bathroom to kitchen while the player is in the hallway), but teleport generation accepts only locations. Open/close/move actions use visible doors and therefore always use door to <destination>.
| return this.name + " to " + connectsToContainer.get.name | ||
| } | ||
|
|
||
| return this.name + " from " + connectsFrom.name + " to " + connectsTo.name |
There was a problem hiding this comment.
@copilot when would that be used as a canonical referent? Give concrete example from playing ScienceWorld.
No. Current
Implemented in |
ScienceWorld generates inconsistent commands for opening doors: the bedroom uses
open bedroom door, while most locations useopen door to <location>.scripts/reproduce_issue_82.py.1-1and print valid door-opening actions.