Building AI With MongoDB: Story Tools Studio Brings Gen AI To Gaming With Myth Maker AI

Mat Keep
February 27, 2024
#genAI

Story Tools Studio harnesses cutting-edge generative AI (gen AI) technologies to craft immersive, personalized, and infinite storytelling experiences.

Roy Altman, Founder and CEO at Story Tools Studio says, “Our flagship game Myth Maker AI leverages MUSE, an internally developed AI-powered, expert-guided story generator that blends a growing collection of advanced AI technology with creative artistry to weave real time narratives.”

The company’s founders have backgrounds in stage, film, and video production, and both share a deep love of gaming. When ChatGPT first launched, they immediately recognized an opportunity to redefine gaming experiences. And so Story Tools Studio and its MUSE engine were born.

MUSE (Modular User Story Engine) combines professionally crafted stories with user-empowered experiences. Players make intentional choices that guide the story with AI adapting to each decision in real time, providing a unique and personalized journey. MUSE separates the story from game mechanics, allowing the development of multiple game types. Its use of AI creates more agile teams with fewer dependencies.

Generating gameplay with AI

When a player starts a game in Myth Maker AI, they are presented with the option to choose their starting hero character. Under the covers, MUSE calls the GPT4 API, which takes the player’s selection and writes a fully customized adventure premise. From that initial personalized script, MUSE programmatically calls specialized AI models to collaboratively generate an immersive, multimodal gaming experience using images, animation, audio, and soon, video and 3D.

**Figure 1:** MUSE orchestrates multimodel genAI to create real time, unlimited stories

Altman says, “For story generation and text to voice, we run mainly in Azure’s OpenAI service. Visual assets are created via Leonardo AI, and we are constantly experimenting with new models to create richer modalities. Right now my team is working on generating enhanced 3D assets and video from text prompts. With the pace of AI advancement, the creativity of my team, and the input from our game testers, we are continuously deploying new features. And MongoDB with its dynamic and flexible document data model gives my developers the freedom to do that. This enables us to build a truly innovative, artistic platform, opening up a whole new world of experiences for both creators and audiences alike.”

By selecting MongoDB, we were able to create a prototype of our game in just 48 hours. It is only with MongoDB that we can release new features to production multiple times per day. We couldn’t achieve any of this with a relational database.
Roy Altman, Founder and CEO at Story Tools Studio

AI, transactions, and analytics with MongoDB

Altman’s engineering team has used MongoDB Atlas from the very start of the company. MongoDB stores all of the data used in the platform — user data, scripts, characters, worlds, coins, and prompts are all richly structured objects stored natively in MongoDB. The games are built in React and Javascript.

Beyond gameplay, the company’s developers are now exploring MongoDB’s ACID transactional integrity to support in-game monetization, alongside in-app intelligence to further improve the gaming experience through player analytics.

“By running MongoDB in Atlas, my engineering team is free to focus on AI-driven gaming experiences, and not on the grind of managing a database,” says Altman. “MongoDB has scaled seamlessly and automatically as we’ve graduated from our closed beta into public beta today. Every 24 hours we are organically adding dozens of new players with tens of gigabytes of new data streaming into the platform. We expect this to grow quickly when we kick off our marketing campaigns.”

What's next?

Myth Maker AI is just the start. Story Tools Studio has plans for multiple games in the next 12 to 18 months. At the same time MUSE is an extensible platform — the company is also looking to explore content generation outside of gaming in areas such as education and training.

Story Tools Studio is a member of the MongoDB AI Innovators program providing it with access to Atlas credits and technical best practices, allowing its engineers to freely explore what’s possible with gen AI and MongoDB. You can get started with your AI-powered apps by registering for MongoDB Atlas and exploring the tutorials available in our AI resources center.

You can also learn more about why the world’s largest games run on MongoDB.

← Previous

Anunciando o GA do Atlas Device SDK para C++

A plataforma de dados para desenvolvedores do MongoDB foi projetada para oferecer flexibilidade e escalabilidade incomparáveis para desenvolvedores. Ao simplificar a integração de estruturas de dados complexas e Real-Time Analytics, e acelerar o desenvolvimento e a implantação de aplicações de missão crítica, sua adoção agregou um valor significativo às empresas de todos os setores. Hoje, continuamos nossa missão de oferecer a melhor experiência para os desenvolvedores e temos o prazer de anunciar a disponibilidade geral (GA) do Atlas Device SDK for C++ . As atualizações desta versão são resultado de várias iterações orientadas pelo feedback de nossos usuários de visualização e visam ao desempenho e à portabilidade. O Atlas Device SDK para C++ permite que os desenvolvedores armazenem dados sem esforço em dispositivos para acesso offline e, ao mesmo tempo, sincronizem perfeitamente os dados de e para o MongoDB Atlas cloud em suas aplicações C++. Ele serve como uma alternativa fácil de usar ao SQLite, oferecendo simplicidade devido à sua natureza de banco de dados orientado a objetos, eliminando a necessidade de uma camada de mapeamento separada ou ORM. Alinhado à missão da plataforma de dados para desenvolvedores do MongoDB de simplificar o processo de desenvolvimento, o SDK C++ incorpora a lógica de repetição de rede e a funcionalidade avançada de mesclagem de conflitos, eliminando a necessidade tradicional de escrever e manter códigos de sincronização extensos e complexos. Por que escolher o Atlas Device SDK para C++? O Atlas Device SDK para C++ é particularmente adequado para aplicações em dispositivos incorporados, IoT e cenários entre plataformas Ele serve como uma camada de persistência orientada a objeto abrangente para dispositivos de borda, móveis e incorporados, oferecendo suporte integrado para sincronização com o MongoDB Atlas como um back-end cloud. No cenário em evolução de dispositivos conectados e inteligentes, a demanda por mais dados, incluindo dados históricos para tomada de decisão automatizada, destaca a importância de camadas de persistência eficientes e tecnologias de sincronização em cloud em tempo real que sejam robustas em relação a mudanças nas conexões e interrupções de rede. O banco de dados incluído no Atlas Device SDK para C++ tem mais de uma década de história e é uma tecnologia madura, rica em recursos e pronta para empresas, integrada a dezenas de milhares de aplicativos no Google Play e na Apple App Store com bilhões de downloads. Seu design leve é otimizado para ambientes com recursos limitados. Ele considera fatores como computação, memória, largura de banda e uso da bateria em seu design. A incorporação do SDK diretamente no código da aplicação elimina a necessidade de tarefas adicionais de implantação e simplifica o processo de desenvolvimento. A natureza totalmente orientada a objetos do SDK orienta a modelagem de dados, fornecendo uma abordagem direta e idiomática. Isso contrasta com tecnologias alternativas, como o banco de dados SQLite, que exige uma biblioteca de mapeamento objeto-relacional, o que aumenta a complexidade e torna os futuros desenvolvimentos, manutenções e depurações mais desafiadores. Além disso, o armazenamento de dados subjacente do SDK permite integração perfeita com camadas reativas de UI em vários ambientes. No Atlas Device SDK para C++ damos exemplos de como integrar com o framework Qt , mas outras camadas de UI também podem ser adicionadas. Aprimoramentos na versão GA A nova API foi desenvolvida com base em medições de desempenho com foco e esforço coordenados para melhorar as operações de leitura/gravação da camada de dados. Houve grande interesse dos principais OEMs automotivos e de manufatura, e esse feedback foi inestimável para orientar nossa API final. Algumas das alterações adicionadas ao Atlas Device SDK para C++ incluem: Alinhar nossas APIs com outros Atlas Device SDKs, por exemplo, controle aprimorado do estado do banco de dados com monitoramento e compactação manual Tunelamento HTTP Melhor controle para as sessões do Atlas Device Sync Suporte ao Windows Compatibilidade com o OpenWRT entre outras distribuições Linux, com suporte a musl Suporte ao Android Automotive com arquivos de compilação Blueprint/Soong O que vem a seguir Olhando para o futuro, estamos trabalhando para o suporte geoespacial , bem como a capacidade de construir com uma variedade de gerenciadores de pacotes, como vcpkg e Conan. Agradecemos e valorizamos todos os comentários. Se você tiver comentários ou sugestões, compartilhe-os por meio do nosso projeto GitHub . Pronto para começar? Instale o Atlas Device SDK para C++ — comece sua jornada com nossos documentos ou vá direto para exemplos de projetos com código-fonte. Em seguida, registre-se no Atlas para se conectar ao Atlas Device Sync, um back-end móvel como serviço totalmente gerenciado. Aproveite a infraestrutura pronta para uso, os recursos de sincronização de dados, o manuseio de rede e muito mais para lançar rapidamente aplicativos móveis de nível empresarial. Por fim, diga para a gente o que você acha e participe de nossos fóruns . Nos vemos lá!

February 22, 2024

Next →

The Developers' Developers: Two Australian Developers Share Their Connections to Customers

The world’s 28 million software developers are writing the foundations of our future, propelling innovation for their organizations through lines of code by creating game-changing new apps. Indeed, the US Bureau of Labor Statistics predicts that between 2022 and 2032, the number of software developers, quality assurance analysts, and testers will grow 24%, “much faster than the average for all occupations.” Fueling this innovative workforce is another group of developers, the people working behind the scenes to build the tools, technologies and platforms that other developers need to be successful: the developers’ developers. Many developers at MongoDB—which after all was built by developers for developers, and is beloved by enterprises and startups alike—fall into this camp. To learn more about what makes these developers tick, we talked with two Australia-based senior software engineers at MongoDB who love to code for their peers. For Lavender Chan and Angus Lee, there’s nothing like seeing the ripple effect of the code they have been working on and the impact it has on their customers. What’s more, the opportunity to be a “developer’s developer” has allowed Chan and Lee to find a space for deep technical work while thriving in an autonomous environment. At MongoDB we believe developers will build the future. First, can you share more about your roles and what you’re working on? Lavender Chan (LC): I work on the Relational Migrator tool, which allows developers to migrate SQL data onto MongoDB. I joined the company two and a half years ago, and have been part of the Sydney technology scene for the last 10 years. The appeal of joining MongoDB was that it’s a large global company, but in the engineering team you are able to have a big impact and a lot of autonomy. Relational Migrator was a greenfield project, and our team has been able to take the original product idea built out of the US and run with it. I’m a full stack developer and have touched on every feature of the tool. A lot of the engineers were able to contribute and work on new ideas. There’s also a strong emphasis on culture here which practically means a lot of the people I work with are excited to be here and passionate about their roles. Angus Lee (AL): I work in the MongoDB Charts team in Australia and think our team is a sweet spot for developers. I’ve interned for other tech companies and started my career at MongoDB. Since then I’ve been given responsibilities where I can create a lot of impact. My role at MongoDB in Sydney has also given me great opportunities to connect directly to the developers we are creating products for in a way that pushes my work to a higher level. Your roles are focused on products targeted to other developers. How does developing for developers affect your approach to your work? LC: In our roles we are creating directly for other developers, so the work that I am doing is deeply technical and specific. As Migrator is a newer product, we are able to interact directly with our customers—other developers—and often a lot of their questions are quite complex and specific, which means I go on a learning journey in debunking and fixing their problems. AL: We have a strong team culture in that as developers we want to be our own users. That means we want to use other MongoDB team products, and they use ours, so we can better identify pain points and issues for our customers. There’s a term that developers use called “dogfooding” that really sums up how we think on this, which basically means to use your own product. It means for me that I think about writing clean code to help any other developers extend on this, and how effective what I do will be for the user. What I’ve also learnt is how our product helps other products thrive. We should have done all the hard work to transform data and show it through data visualizsation tools so it’s easy for the customer. Can you tell us more about this connection to customers and how MongoDB empowers developers? LC: When Relational Migrator was released as a general product, I went to MongoDB World to work at the booth, and I talked to the developers and customers using the platform. As an engineer, it was an amazing experience and opportunity to see how it was being used and what else we could be doing. This connection of engineers with customers, as well as the ability to speak to them regularly in my role, is unique. In other companies I would need to go through support teams, to go through someone else just to push out a bug fix. Our team is very customer focused, so we can prioritizse features that our customers want. AL: One of the best moments for me at MongoDB was when I went to MongoDB World and I sat down with a customer to talk through a feature of Charts. It was a pivotal moment to see the improvements it makes for the businesses that use it, and the impact it generates for their customers beyond that. I could sit back and see the ripple effect of the code I’m writing. There is also a great feedback engine where our users can submit ideas and other users can vote for that feature. The product managers pick from these and push out features that are directly relevant to the developers using it. Where we really connect is in our aim to create an open forum for developers and customers to provide feedback and suggest ideas. Developers are problem solvers. As part of the MongoDB Love Your Developers campaign, we believe in championing the voice of developers and giving them the freedom to experiment and innovate. How do you see this in action? LC: In other places I was a small cog in a massive system. At MongoDB, I really have an impact, and can see directly how my work translates to our final product. In Sydney, we’re a satellite office, but it’s indicative of our company culture that there is huge trust placed in these teams. We’re given high impact projects and can run with them, which means I’ve been able to watch the Relational Migrator product go from a tiny product used by only a few customers, to one that is now generally available. Not many engineers get to work for a well-established,large company and still have the opportunity to work on and release products like a startup. There is a strong global interest in AI-driven innovations. How have your connections to customers led to innovations in this area? AL: We’ve been able to take an idea for a new AI feature, Natural Language Charts , and take it from concept to being released as a feature at MongoDB.local in London. We could see from our conversations with customers, as well as broader industry trends, that there was strong interest in new AI features so we were able to prioritizse it for Charts. We started with nothing and were given the freedom to research how this feature could work using AI, create a new proof of concept, and from there we were able to push it out into a feature which was a really proud moment. Having this agility and flexibility to prioritize something new is exactly what we want to provide to our customers. I never feel like I'm just churning out code. We are connected to the work and to our customers. MongoDB is built by developers, for developers. Become part of the team changing the way the world works with data!

May 9, 2024