Inspiration

With "Did Liquid Win?", we wanted to answer just that. It’s a question that fans like us ask frequently, so we wanted to be able to answer it as quickly as possible. We often find ourselves scrolling through Twitter or looking through Reddit posts to find results. With our project, all it takes is just one click. Because of this, we think that our project is simple yet practical, and it even gives the option to dig deeper into the results if desired.

What it does

Our website is designed to check the result of each Team Liquid match from multiple esports titles including CS:GO, LOL, Dota 2, R6S, Rocket League, and Valorant. Our website will show you whether Team Liquid won or lost the game (with the score) with just a single click. No matter what games you play or watch, we will provide you with all the results you want to look at. Also, clicking on the score will redirect to the related game’s tournament page on liquipedia.net.

How we built it

While we have some frontend experience, we were not super knowledgeable on how to create a backend and access the liquipedia API. To do this, we ended up using express in conjunction with a node js backend. When making the frontend, we wanted to try something new, so we used React, and made calls to our backend using axios. We also made use of a few other libraries, including material-ui, concurrently, node fetch, and nodemon.

What's next for Did Liquid Win?

We could definitely make some improvements to our application. Currently, we only support a handful of games, such as LoL, CS:GO, and Dota 2, but are missing big games like Fortnite and Apex Legends. The battle royale titles have a problem in that even if Team Liquid won the match, they had more than one opponent, which the formatting of our score reporting feature does not account for. Other than that, we feel confident that we could expand the game library if given more time. Lastly, we could have made it to where we send users to match pages instead of the related tournament page, but we were limited by the liquipedia API in that regard.

Share this project:

Updates