Here is a list of things I currently have on my TODO list. It's all a subject to change, and some of these can be simply ideas that might be discarded. Feel free to comment and suggest things based on this list in the forum.
  • ==== REFACTOR ====
  • A major refactor is needed. The whole system should be modularized, the bot itself should be completely decoupled from f-list. It should have different 'adapters' to be able to connect it to different chat systems and custom frontends, both throug internal and extrnal APIs. It should be threaded and it should have a message-in and message-out queues. It should also be possible to plug in different game modes into it.
  • ==== WILL WORK ON ====
  • Try to create "typing" indicators for bot maybe? Really the whole thing should be rewritten to work asynchroniously or with threading and message queue. The architecture might be as follows - receive queue receives messages and immediately spawns processing threads, processing threads add results to send-queue, and then a simple sender thread sends messages from send-queue every X seconds (where X seconds is the f-chat rate limit)
  • Add FighterState table to database, and move all attributes like Health into it. This should make it easier to handle continuing of battles with !continue, especially if there will be more stats and stuff added later.
  • Rework News system to not record news as separate events, but rely on existing database of Battles and fighters and their creation\update dates and states to show latest events
  • Write it down that bot will only message players if their status is set to looking or as a response to their command
  • Gameplay update: Add 2 more moves. They can either enter the classic extended RPS system, or they can be different, for example they can beat every other move but with lower damage, or beat each other. Or there can be completely separate RPS 'wheels' for each attribute.
  • Change post-fight ending messages to include fleeing fighter's message in one way or another, as part of the it. Maybe ask players if they'd like to say something in the end, and choose appropriate message depending on that. So announcer is even more alive.
  • Add wardrobe concept, allowing character to have different outfits and use them in different roleplays
  • Voting for fight logs on the website, likes and dislikes system
  • Indication of permanently killed chars on profile
  • Gallery of permanently killed chars
  • Add ability to un-ignore someone
  • Fix lore page
  • Add !refresh_info command, to update gender and orientation data from f-list profile
  • Stage fatalities
  • Rename block to counter as it better reflects what it does.
  • Better format for !myinfo
  • Simple dice roll function for RP purposes. Only difference from f-list one is that bot will relay it to both players.
  • !draw command. Will allow to call for a draw between fighters.
  • Edit profiles through website
  • Bet system for public fights
  • ==== EXPECTED F-LIST 2.0 CHANGES ====
  • Adjust for any chat API changes
  • Pull profile data through new Website API
  • ==== IDEAS, MAYBE ====
  • Gameplay update: more moves; arousal, consciousness, stamina bars and gameplay
  • Subscribe to !fa updates instead of using this command over and over
  • Rework random bot status to use chance\rarity control to allow showing some statuses more often than others, or dont use random, use rotation instead, so every status is shown
  • Announcer comments during fight. Flawless etc
  • Sending messages to players by their stage name
  • Adding more stages
  • Stats under Ratios
  • Fighting mechanics improvements. Please, feel free to suggest ideas
  • Question prompt framework
  • Add "Do you accept a fight from X?" routine to the start of the fights
  • Add "Would you like to make log public?" routine to the start of the fights
  • Add "Event" database table for events which can be used for news and other stuff
  • Better onboarding process for new players, suggest starting a tutorial fight that goes over all the basics
  • Ability to accept or decline match before even getting into chat (X chellenged\matched to RP with you, accept or decline? decline reason will be required)
  • Better gameplay reward system to give more incentive for playing
  • graph of number of rps/chats per day served by bot
  • automate afk counter, if leave by same person and no messages (but first figure out what exactly I meant when I wrote this idea down in a hurry)
  • Hide OOC messages from public log viewing
  • Page with a list of stages
  • Pull and store orientation data during registration
  • Research possibility of using NLP to extract intent from user messages and suggest commands, or even execute them
  • ==== DECIDED AGAINST ====