Larian Studios Forums Active Threads Since Yesterday

What stands out to me is how much this could lower the barrier for people who have creative ideas but no real experience with level design. I’d love to experiment with building my own locations without having to learn a complicated editor first. The biggest thing for me would be seeing how much freedom modders have to make their environments feel unique rather than generated from the same patterns.

I didn't look any deeper into 5e paladin oaths than respeccing Kerz, but that's the lawful alignment aspect of paladins. 2e-dungeon masters were even warned not to subject player paladins to certain moral dilemmas that allowed no lawful good way forward because they would lose their class. Back then, there was no path of atonement in the basic rules. You'd just end up as a regular fighter, or dying as a paladin. To my mostly chaotic tabletop group, being a paladin means you're some sort of dangerous loony.

Trying to get a custom level made with the MoonGlasses toolkit unlock to load in-game (Patch 8, Script Extender v33).

Setup: flat greybox level created from a terrain template. Also reproduced the same issue on a brand-new Basic_Level_A template level. The mod publishes fine via Publish Local, installs, and loads my save with no crash. But when I teleport into the level via the SE console with:

Osi.TeleportPartiesToLevelWithMovie("MyLevel", "", "")

the command runs with no error, then the client bounces straight back to the launcher (no crash dump is written). The Osiris server keeps running — it's the client/render that drops.

Editor Message Log on level load shows:
- "Failed to load chasms. Chasms need to be regenerated for this level"
- "Texture @ ...Generated/Public/Game/MaterialGrid/Materials.DOS, failed to instantiate! x22365"
- granny Gizmo_Trigger_Lighting.GR2 warnings

Key clue: the generated nav data is empty placeholders, and it's IDENTICAL on a brand-new Basic_Level_A template level and on my own level:
Ai/aigrid.data = 300 bytes
Ai/chasms.lsf = 113 bytes
So it looks like new levels come out unbaked.

Questions:
1. What's the exact procedure to regenerate/bake the AI grid + chasms (and material grid + lighting) for a level so it will load in-game?
2. Is there a "generate full grid" action I'm missing, or is the bake pipeline simply not wired up in the unlocked (MoonGlasses) toolkit?
3. Any known workaround to get a custom level enterable in-game?

Thanks in advance!

I'm playing a dwarf berserker.

Found the gnomes in Moonrise prison, and Tav tells Wulbren they want to help the gnomes escape.
Wulbren answers something like "why would you help us, you're one of them aren't you ?"

This gives the following response option which really made me laugh :

[INTIMIDATION][BERSERKER] ACCEPT MY HELP OR DIE. CHOOSE.

I absolutely do NOT agree. After the awesome BG3, I don't wanna go back to DOS2. DOS2 is more about combat than anything else — you get tired of these fights before you've even gotten out of the starting tutorial area. Everything's bright, with effects that make it impossible to even see the characters themselves. Yeah, lots of stuff, I'll get tired listing all the ways DOS2 is way inferior to BG3. I'd want them to build on BG3's ideas and game design first and foremost, not DOS2's. They'd just deepen freedom of choice, consequences and companion influence. The combat system is the least thing I care about at all — in BG3 it at least didn't piss me off like in DOS2.