DecisionCraft

• 

  Homepage

• 

  Game Interface

• 

  Outcome

• 

  Timeline

Inspiration

When coming up with what we wanted to do, we had a lot of contention between things like an urban dictionary for converting modern brain rot slang into understandable language. However, we felt it was simple and didn’t have many in-depth developments required. As such after much deliberation we ended up working on an alternative history timeline. It’s something everyone has thought of once in their life, you know you say something absolutely horrific that you wish you could turn back time, then this is exactly for you. Where you could speed-run the end of the world. Or you could be bored and play it like its intended.

What it does

It allows you to go back into history and change the outcomes of those events. You can either cause a massive butterfly effect that the world could end. Or you could be boring and try to survive past 2027

How we built it

We used Python and Flask to develop a backend server that generates the payload for our frontend. Plus our backend server prompt’s the OpenAI API to help generate somewhat realistic historical accounts, despite being in an alternate history timeline.

Challenges we ran into

No existing LLM that has been trained on significant historical accounts and data

Accomplishments that we're proud of

Building our payload delivery system, and the ease of updating and adding more stuff.

What we learned

Using LLM prompts is horrible, and we should’ve done more research into it first.

What's next for DecisionCraft

Developing a dedicated A.I. for decision generation that takes into account historical accounts and data.

Built With

• css
• flask
• html
• javascript
• python