djetelina / xleague Goto Github PK

An error has occurred: <[Failure instance: Traceback: <type 'exceptions.UnicodeDecodeError'>: 'ascii' codec can't decode byte 0xe2 in position 264: ordinal not in range(128)
C:\python27\lib\site-packages\twisted\internet\tcp.py:298:connectionLost
C:\python27\lib\site-packages\twisted\web\client.py:213:connectionLost
C:\python27\lib\site-packages\twisted\internet\defer.py:382:callback
C:\python27\lib\site-packages\twisted\internet\defer.py:490:_startRunCallbacks
--- ---
C:\python27\lib\site-packages\twisted\internet\defer.py:577:_runCallbacks
XLeague\main.py:340:callprocess
XLeague\main.py:345:cardprocess
]>

After database restructure, we can start porting commands and rewriting database.py to match our needs

Kyle and I talked for a bit. In order to simplify user experience and still have our account system, it would be great to have chat app/protocol, that had OAuth. We could link chat auth with our database and build gamification etc. on top of that.

Here's few things we discussed and their advantage/disadvantages

• Slack

https://slack.com/ - They have OAuth, they support bots, but I couldn't figure out a way to embed their client to our frontend

• Twitch.tv IRC server

OAuth present, IRC network, so no need to rewrite our bot logic in something else. Embeding could work either through iframe of their popout chat, or inject OAuth into irc command to connect

I haven't really explored the options indepth too much, as this requries a lot of thinking I cannot afford during exam period. So while I'm busy studying, you can talk here about different variants, solutions, or just say that current system is good enough (GameSurge auth through IRC, separate accounts in our database).

This post might be a bit chaotic, if you need any clarifications, lemme know

I'd love to hear what do you think new database architecture should look like, please add on to these, or say if you think some of them are extra. Also if you come up with shorter/better alternative name, please say so.

We don't want to build account system, it's ok to rely on GameSurge so far. But having extra information for potentional player profile pages is good.

• ID (INT)
• Created (TEXT - with date)
• Name (TEXT)
• About (TEXT)
  • Markdown?
• Vouched (1/0)
• Judge (1/0)
• Admin (1/0)
• Warnings (INT)

For both Constructed and Limited

• ConstructedHiddenRating (REAL)
• ConstructedPublicRatingFactor (INT)
• ConstructedPublicRating (INT)
• CGamesPlayed (INT)
• CGamesWon (INT)
• CGamesLost (INT)
• CMathcesPlayed (INT)
• CMatchesWon (INT)
• CMatchesLost (INT)

• GameID (INT)
• Winner (TEXT)
• WinnerGameScore (INT)
• Loser (TEXT)
• LoserGameScore (INT)

anything else that should be stored?

Not much has to change here

• ID (INT)
• Running (1/0)
• MatchesPlayed (INT)
• QueueType (TEXT) - equivalent to pod size, but more understandable (Sealed2, Sealed4)
• Leaderboard (TEXT) - Limited/constructed
• Player 1 (TEXT)
• ...
• Player 8 (TEXT)

Another option is to have multiple tables for each QueueType and their public ID then be QueueType-number