As most of the interactables are being implemented in #68 for #66, the only thing remaining in this issue is interacting with cameras and admin.
I spoke to vedal about the idea of letting neuro interact with these two and we agreed that given the neural network we have and the way we are recording the data, there's no real way to get and parse data from admin, so it would be a waste of time to try to implement it.
However, as for cams, we can actually record player data for players visible on cams, and even spot murders/vents and report them to the language model.
Now we need to figure out how we're gonna implement this, what will dictate when cams are opened, scrolled, etc?
Currently the agent seems to like going to cams on polus, so opening cams whenever in range might not be a good solution. I also don't really like the idea of using random range. The same problem occurs for the meeting button, see issue #73
Old issue description
- [x] We should make an interactions handler to dictate which consoles to interact with.
- [x] The current MinigameSolver system from pr #26 can be expanded to dictate which task consoles we should interact with (to allow for timer tasks to work correctly)
- [x] Also, we should only interact with doors if we are pathing to a point behind them.
- [x] Allow interaction with flying platform
- [x] Allow interaction with ladders
- [ ] (Maybe?) Allow interaction with cameras and implement record seen players' positions
- ~~(Maybe?) Allow interaction with admin table (but how would that help the AI though?)~~
As most of the interactables are being implemented in #68 for #66, the only thing remaining in this issue is interacting with cameras and admin.
I spoke to vedal about the idea of letting neuro interact with these two and we agreed that given the neural network we have and the way we are recording the data, there's no real way to get and parse data from admin, so it would be a waste of time to try to implement it.
However, as for cams, we can actually record player data for players visible on cams, and even spot murders/vents and report them to the language model.
Now we need to figure out how we're gonna implement this, what will dictate when cams are opened, scrolled, etc?
Currently the agent seems to like going to cams on polus, so opening cams whenever in range might not be a good solution. I also don't really like the idea of using random range. The same problem occurs for the meeting button, see issue #73
Old issue description
- [x] We should make an interactions handler to dictate which consoles to interact with. - [x] The current MinigameSolver system from pr #26 can be expanded to dictate which task consoles we should interact with (to allow for timer tasks to work correctly) - [x] Also, we should only interact with doors if we are pathing to a point behind them. - [x] Allow interaction with flying platform - [x] Allow interaction with ladders - [ ] (Maybe?) Allow interaction with cameras and implement record seen players' positions - ~~(Maybe?) Allow interaction with admin table (but how would that help the AI though?)~~