mansueli

This was a good proof of concept. The fact that is is working for such a complex system as VTM, shows that the idea behind could work well in other domains or more broadly for similar systems.

It seems that someone flagged my other comment, I am not sure why.

Hi HN, I’m Rodrigo.

I built Vampiro Life because I was frustrated with generic AI wrappers for tabletop RPGs. LLMs write great atmospheric prose, but they suffer from severe context amnesia—they constantly hallucinate inventory or lose track of mechanics (like "Hunger dice") after a few turns.

I realized that to make a campaign last, the chat transcript cannot be the source of truth.

I decoupled the narrative from the canonical game state using React SPA and Supabase:

State Backbone: Postgres stores character sheets, bounded NPC disposition scores, and world entities. AI output must pass through explicit state transitions (tool calls) to become canon.

Tiered Memory Rollups: To keep retrieval costs bounded, memory is compressed via Edge Functions into tiers (recent -> older -> ancient).

Deterministic NPCs: NPCs don't rely on the LLM "remembering" you. The system persists qualitative relationship edges (e.g., Rival, Sire) to the DB and injects them only when that NPC is in the scene.

I wrote a deep dive on the architecture (including SPA SEO/GEO and Edge image optimization) on my blog: https://blog.mansueli.com/building-a-persistent-ai-game-mast...

I would love for you to poke around the engine, try to push a campaign far enough to break the memory limits, and let me know what you think of the architecture!

Hey HN,

There have been some interesting projects on Postgres.

The idea of this Extension (while exoteric) is to show the power of TLEs. You can even expand and play with things on hosted platforms like AWS and Supabase.

1: (https://github.com/DreamNik/pg_doom)

Have you tried this in databases with Trusted Language Exensions?

(https://github.com/aws/pg_tle)

How was the implementation? Is it in RUST?

Can you share more details on how you achieved this or the underlying changes that was needed?

Any changes needed on eszips for sub-hosting events?

Did you take a look at https://github.com/yasyf/compress-gpt?

What is the best way to find beginner friendly issues/start contributing to the core?

There ins't a issues tab in the main Postgres repo: https://github.com/postgres/postgres

Disclaimer: I work at Supabase.

Free projects: 0.5GB.

Pro tier: 8 GB included, then $0.125 per GB.

I can say that we helped a customer migrate a DB of over 1 TB over from RDS to Supabase. Feel free to contact us if you have any questions.