Fedi Plays - chat-reactive gaming on Fediverse streams
A community, dedicated to playing games interactively through stream chat on PeerTube.
Current Fedi Plays: Peertube Plays Chocobo Dungeon 2
Stream on pause for now: Fedi Plays Dragon Warrior: Monsters
Available commands:
Type these commands in the chat to control the game:
- up/u - Move up
- down/d - Move down
- left/l - Move left
- right/r - Move right
- triangle/t - Press triangle button
- square/s - Press square button
- cross/x - Press cross button
- circle/o - Press circle button
start - Press Start button select - Press Select button
use "x o 4" to do 4 "cross and circle" button presses. the number has to be the last character and it goes up to 15
I'm [solidheron] able to get the latency down to 7 seconds and hopefully the ability to string inputs will make fedi plays easier
How It Works
- enter a command into chat
- closets command to the 4 second check will get executed
- Multiple viewers' inputs create chaotic and unpredictable gameplay
GitHub Link to the python script being used:
https://github.com/solidheron/Fedi-plays/blob/main/fedi_plays.py
Thanks for the initial idea and current stream to solidheron:
https://dalek.zone/a/solidheron
https://mastodon.social/@Cattail
view the rest of the comments
the issue is with peertube chat. it only gives me down to the minute information on when a chat appears and I needed to prevent the same comment from inputting the same command, so repeated inputs in the same inputs not going through was the sacrifice.
the work around is to load the last 5 comments from chat and just see if there was a change in the last 5 comments so that way repeated commands would push out unique comments (both in content and time) making them go through, but I haven't been able to do that. on top of that doing the a4 commands helped fix the issue since "a4" and "a" are different commands.
other than that i have to put in a refresh commands for firefox browser because that cuts the programs connection to chat
Ah, that makes a lot of sense, I knew something must have been a more advanced issue, as I had noticed you did maintain the code, so it wasn't just some faults in there.
Great job, btw, this is lots of fun!