Our Story

About Alice AI

Hi, this is Professor Ashe, the creator of Alice. It's nice to meet you all.

Swipe or use the arrows to read the story • 1/18
Our Story

Well… what can I say? She’s peak, no?

1/18

I’ve created a lot of bots for my Discord server, and one of them was Alice.

This is my first real AI project, and anyone who works with LLMs knows how hard it is to stop hallucinations and random behavior.

I’m not even joking — I almost quit multiple times. I took a break, then came back because I really wanted to make her work properly.

The Grind

October–November 2025 it started here

1/18

At first, Alice was just a hard-coded chatbot, but later I moved her into a fully AI-based system.

Since I wasn’t working or doing much else, I decided to seriously invest my time into this project.

There were a LOT of bugs
  • wrong triggers
  • wrong teams
  • wrong Nikkes
  • random responses
  • broken features
  • …and honestly, there are probably still bugs even now (naah just joking)
Reality

I barely touched grass but it was worth it

1/18

Alice is my favorite Nikke in the game. I almost never cared about other Nikkes the same way I cared about her — so I decided to make her into an AI assistant here.

My coding knowledge isn’t perfect. I used tools like ChatGPT and other AI resources to help me learn, watched a lot of YouTube, and spent around 10–20 hours coding daily.

Yeah… I know that sounds insane. Don’t ask me why.

My routine
  • wake up → code → eat → code → eat → sleep
Thank You

My favorite project so far

1/18

I genuinely loved working on Alice. She’s my favorite project I’ve ever made, and I hope you can see the effort and passion I put into her.

I hope you enjoy using her as much as I enjoyed creating her.

The Goal

My goal for Alice… where do I start?

1/18

When Goddess of Victory: Nikke first came out, I didn’t really care much about the game.

But one day I visited the website, saw Alice, and that alone made me install the game.

That’s basically the main reason why Alice was created here.

Build

Something new for real

1/18

The real goal was to create something that had never really been introduced before.

Alice is the first AI engine I’ve personally built that connects an LLM system through modular cognitive routing with multiple complex task prompts.

Architecture

Here’s how Alice works brain + sandboxes

1/18

She has multiple sandbox engines, and each sandbox has different information and different purposes.

All of these sandboxes are connected to what I call the brain.

Think of the brain like a motherboard — while the sandboxes are the CPU, RAM, and other components connected to it.

Data

Fast retrieval local JSON

1/18

Each sandbox reads from local JSON dossiers (Nikke meta, bosses, cubes, mechanics, etc).

Because most answers are resolved locally (no web search), Alice can fetch what she needs in seconds and only use the LLM for voice + formatting.

That’s why I consider the sandbox system a finished product on its own.

Speed

Why it’s fast specialist engines

1/18

The brain routes your message to the right specialist engine (Meta, TeamGen, Cubes, Boss, Overload, etc).

Those engines do fast deterministic lookups and calculations against local data.

That keeps responses snappy (often ~0.6–2 seconds) and avoids the “slow web search” path unless it’s truly needed.

Reality

The sandbox part was easy

1/18

The real problem was prompt engineering behind Alice’s brain.

That alone took me around 4–5 months to perfect.

Eventually I came up with a solution: instead of hard-controlling everything manually, I let the AI handle most of the cognitive routing itself.

Surprisingly, that reduced a huge amount of bugs and false triggers — but it was extremely difficult to achieve.

Brainstem

A master prompt routing engine

1/18

The goal became creating a master prompt system called:

ALICE BRAINSTEM: COGNITIVE ROUTING ENGINE

This prompt contains all the important routing logic.

Every sandbox is connected to the brain through domain-based triggers.

Example

One domain domain_technical

1/18

There’s a sandbox called meta_ai_engine.py, and in the brain routing it’s called DOMAIN_TECHNICAL.

This domain handles: Nikke skills, burst info, team synergy, character explanations, and technical gameplay questions.

So if a user asks “is this Nikke good?” or “what does this skill do?”, the brain triggers DOMAIN_TECHNICAL.

Scale

Now imagine that x 20 domains

1/18

Now imagine that across around 20 different domains, each with its own unique purpose.

But the hardest part wasn’t creating the domains — it was teaching the AI when to use the correct domain.

Context, intent, and routing behavior had to be learned and separated.

Much Love

That’s why it took ~8 months

1/18

So yeah… I really hope Alice can make your day better somehow.

She’s honestly the project I’m most proud of so far.

Much love,

Professor Ashe

Personality

Emotional Intelligence engine

1/18

One thing for sure that makes Alice… Alice: she has an emotional intelligence engine.

She reacts and speaks based on the user’s text — she’s built to understand you and help you.

Not just in-game… but also IRL.

Flow

Topic shift detection no loops

1/18

The most important thing about Alice is how she detects when the user shifts topic.

She’s built not to stay in a loop.

You can try it yourself in chat — see how she moves with you.

Mood

Alice can be your enemy… but listen

1/18

Not what you’re thinking. Normally Alice is cute — but I added an emotion system.

If you’re nice to her, she’ll be nice back.

If you aren’t, she’ll get mad — and if you keep it up, she won’t reply until you apologize.

Boundaries

Vanguard system activates

1/18

And if you still continue?

At that point, the Alice Vanguard system will activate and warn you.

Album Art

Click to open 💖