Git Product home page Git Product logo

bout-dashboard's Introduction

bout-dashboard's People

Contributors

mknepprath avatar

Watchers

 avatar  avatar

bout-dashboard's Issues

Add mock Twitter data

Will want the ability to go through bout flow - but eventually, we need to be able to handle actual Twitter data. When hitting a button, we know an attack/move is correctly directed and valid - when dealing with tweets, we'll need to make sure the tweet is valid (or even intended to be a move within bout).

Gen bouts in state

Currently only handles one bout at a time - should handle multiple. Will need to create a bouts array in state... Perhaps add a new bout button. Also turn should be added to each player object so that the players can be mapped.

Create item illustrations

Would be cool to have an illustration for each item, then attach them to the initiation tweet in pairs.

Initial bout illustration

Nice graphic that includes some info about how to play. This would get posted with the first tweet when someone is challenged.

Create landing page with more info

Can look nice, but should contain instructions, moves, extra moves, etc. Maybe should link to a more wiki-like page detailing out the specifics of each item and other tricks.

Store all tweet_ids

Only stored newest tweet_id before - but this would cause issues if that tweet (or more) were deleted. Should store all tweet_ids that have been addressed to compared against.

Don't require in_reply_to @bout_bot

Players may reply to each other with moves while playing - I don't think they should be prevented from doing this. Just have to make sure @bout_bot is mentioned and that there is a valid move present (#throw, #slash, etc).

Store player data

For the future - may be cool to track a players win/loss track record. Even if I don't show it, it may be useful for making sure items are balanced.

Bout ids

Need some way to make sure when two players are in a bout, they can't create a new one - check to to see whether they have one in progress already or not. Easiest/ugliest solution, include a unique bout id in @bout_bot's tweets.

Actually, this may be easy regardless - bout id should just be the two player Twitter ids concatenated, so a @mknepprath vs @benlundsten bout id would be 15332057-52533282. Make sure the "smaller" of the two always goes first so that a second bout 52533282-15332057 won't be created.

And perhaps make it bout-15332057-52533282...

Update all copy

Current text was rushed - add some randomized options as well.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.