u/JHawke12

https://preview.redd.it/p6tmft1fp3ih1.png?width=788&format=png&auto=webp&s=ec9f3cec1e6c4dae9a46294bf25e48345446ff1a

So funny story behind this node right, when i read this i thought it was like the Huck atlas node in PoE where he provides a pretty solid buff right while you're mapping except Masque would give you defensive buffs which is great as i play HC anyway. However, I was curious on what the buffs actually are as for Huck you can easily see but after extensive searching, there was literally no info on this at all.

I then a while ago tried asking on this discord and literally no one knew there and i was memed for taking this node lol. After being persistent in the ask the devs channel i think one of the mods "Yayifications" replied saying that:

"He doesn't provide a passive buff, rather his abilities provide small buffs when they hit you, such as an amount of ward. Unfortunately I can't get more specific info than that right now as it would require the team to dive into the code."

So basically,. Masque is actually less than useless. First of he attacks slowly, the ward amount he gives is pityful and there is no clear indicator in the UI for this. So no defensive aura, no actual buffs, does 0 damage and worst of all, none of this is known to the player when reading the node. It's bad that even EHG doesn't know unless looking into the game code. Anyway im bringing this up again now cause the mod that replied to me is no longer on the discord and they said they would add it to their notes so idk if EHG is aware of this but please fix Masque to not be useless for 1.5 and to more importantly, update the description of the node so that in alt view at least, you can see this info rather than the useless memory amber info there is now there.

Hey everyone, I’m building a free public alpha called Scenario Conductor for people who use AI to write long-form fictional scenes, fandom/source-grounded AUs, or story plans.

Link: https://www.scenarioconductor.com

The basic idea is that a lot of AI writing eventually turns into one huge chat thread where the model starts losing track of the premise, cast, continuity, tone, or what the current scene is actually meant to do.

Scenario Conductor is my attempt at a more structured workflow. You create a scenario workspace with the story baseline, what has changed, the current situation, cast/context notes, source cards, memory, and the next beat you want to explore. Then you can draft a scene, inspect what context went into the prompt, critique it, repair it, retry it, continue it, or accept it and move forward.

The newer parts I’d especially like feedback on are:

• Scene Direction / Director’s Assistant for working through future beats, constraints, continuity notes, and scene briefs before generating
• sturdier critique, repair, retry, and continue flows
• reusable Knowledge Library/source context so canon or setting notes can carry across scenarios
• clearer docs for setup, model roles, budgets, workflow terms, and what each part of the app is for
• optional advanced local model setup for people experimenting with Ollama/LM Studio, though OpenRouter is still the more tested path right now

It is not meant to be a one-click novel generator. It is more like a director’s desk for writers who still want to guide the story themselves, but want help keeping the scene coherent and the context visible.

I’d love feedback on whether this workflow makes sense for how people actually write with AI, especially for longer scenes where normal chat starts drifting. Thanks!

Hey everyone, I’m building a free public alpha called Scenario Conductor, and I’d really appreciate feedback from people who use AI for writing long-form fictional scenes, fandom/source-grounded AUs, or story planning.

It is bring-your-own OpenRouter key, so the app itself is free, but generation runs through your own OpenRouter account.

Link: https://www.scenarioconductor.com

I built it because most AI writing workflows eventually become one giant chat thread. That works fine at first, but after a while the model starts forgetting things, drifting from the premise, rushing the story forward, losing character context, or treating every “what if?” idea like it needs to resolve the whole plot immediately.

Scenario Conductor is my attempt at a more structured writing workflow.

Instead of only prompting in a chatbot, you create a scenario workspace with things like:

- the canon or story baseline

- what has changed from the original setup

- where the scene is right now

- the cast

- character and context notes

- the next beat you want to explore

Then the app helps draft the next scene, inspect what context went into the prompt, critique the draft, repair it, retry it, continue it, or accept it and move forward.

It is not meant to be a one-click novel generator. It is more like a director’s desk for people who still want to guide the story themselves, but want help keeping the scene coherent.

A few current features:

- scenario workspaces for long-form fictional scenes

- reusable character profiles and cast notes

- context/source cards that can be included in prompts

- inspectable prompt/context packets

- draft, critique, repair, retry, continue, and accept workflows

- browser-local scenario storage

- optional MediaWiki/Fandom-style lookup for source/reference snippets

Your scenario data is stored in your browser. You can use a session-only OpenRouter key or save it locally in your browser profile.

I know the BYO key setup makes onboarding more technical than a normal AI writing app, so feedback on the first-run experience would be especially useful. I’d also love to know whether the scenario/context workflow makes sense for how you actually write.

Hey everyone,

Here is the public alpha of my Scenario Conductor live: https://www.scenarioconductor.com

I built it because normal character chats kept leaving me wanting a different kind of workflow. I didn’t want a model to just roleplay one character back at me; I wanted more of a director’s desk where I could set the canon baseline, define the AU/divergence, keep cast/context/memory visible, and generate the next scene one beat at a time. There’s also a General chat area for one-off AU/canon brainstorming when you want to explore an idea without turning it into saved story state.

What it does right now:

- Creates browser-local scenario workspaces for fictional anime/game setups

- Lets you bring your own OpenRouter key, either session-only or saved in your browser

- Gives you control over which models handle generation, discussion, critique, repair, Helper, and personalisation

- Has a General tab for loose AU/canon brainstorming without changing saved story state

- Keeps context cards, character profiles, cast, memory, and preferences inspectable before generation

- Generates scene drafts with critique, repair, continue, accept, and undo flows

- Exports browser-local backups without provider API keys

It’s definitely still alpha. Text-first, no account system, no bundled key, no character/lore packs, and you'll need your own OpenRouter key!

I’m hoping this is useful for other people who’ve used the popular chatbot sites and felt the same friction such as wanting more structure, more visibility into context and more control over the writing flow. I definitely procrastinated on releasing it because I kept wanting to polish more, but it’s finally at a point where I’m happy to share it and would really appreciate feedback!