The Lipomancer's Realm [šŸŽ„UPDATEšŸŽ„ 12/25/2025 V0.6.3]

1 Like

Do you have a screenshot of this one? Usually the position of the error can help me close in on the source.

isn’t or aren’t, depending on the value of _is.

Anyway, I should have every bug I’ve been able to track down sorted out, including some really old bugs that have slipped under the radar for a concerningly long time. Enjoy the patch!

Can you tell I was working on this very late at night? lol

Using equip doesn’t apply the curse as well.

EDIT:

I don’t think you’ve included a passage to reach the curio shop after leaving it the first time.
There’s a missing <</if>> for your set $vielcurio to 2 statement.
Every option for dispelling curses has the same error:
Error: <<if>>: bad conditional expression in <<if>> clause: State.variables.hat.special.filter is not a function - Probably because special is a string and not a list that would make sense to filter? I assume you thought ā€œWhat if something has multiple cursesā€ when designing the curse removal shop.
If you decline to have anything appraised there’s no way to go back.

1 Like

There’s a contingency for if the player is wearing multiple cursed items, not for if an item has multiple curses. However, my intention was to check and see if the $[item].special string contains ā€œCurseā€ (or ā€œCurse ofā€, I don’t quite remember) so I don’t have to make a full list of every curse to check for. I’ll have to look into making that work.

Edit: Can you tell I’ve been sleep deprived while working on the last several updates? Lmao

Edit 2: Because I sure can, holy smokes there’s a lotta silly screwups in the code!

The latest patch should hopefully fix everything.

3 Likes

I can no longer enter the alchemist’s shop.

2 Likes

Oops, patched it. Apologies for the inconvenience.

Still not letting me in for my save. Here’s the full error log if it helps.

Error: <>: bad conditional expression in <> clause: undefined is not an object (evaluating ā€˜State.variables.quest11.stage’)

<<if $alchhomelock is true or $quest11.stage is 2>>It would seem that the Alchemist is rather busy at the moment. At least, she doesn’t seem to be opening her door…

<<include ā€œDechraumarketā€>><><<switch $quest3>><<case 2>>You knock on the (rather unusually) fortified-looking door of the Alchemist’s house, and a slot slides open.

ā€œWho goes there?ā€ A stern-sounding voice says, presumably from the person behind the door who appears to be looking you over, presumably the Alchemist.

You identify yourself and inform her that you’re from the Adventurer’s Guild. She slides the slot closed and, after a few moments, opens up the door. ā€œWell then hurry on in! Her Eyes could be anywhere!ā€

Before you are able to ask the Alchemist what she’s talking about, she drags you into her home and closes her door.

[[Continue->MeetingTheAlchemist]]<<case 3>>You knock on the Alchemist’s Door and a slot slides open. ā€œAh, look who decided to show up again!ā€ The Alchemist says, her squinted eyes glaring at you through the slot. ā€œDid you reconsider my offer?ā€

[[Yes->helpalchemist1.5]]

[[No->donthelpalchemist1.5]]<<case 4>>You knock on the Alchemist’s Door, but you don’t get an answer. Perhaps she’s too distracted with an experiment to hear you.

[[Continue->Dechraumarket]]<>You knock on the Alchemist’s Door and a slot slides open. After a quick looking you over, she opens her door and lets you in.

[[Continue->Enter Alchemist’s Home]]<><>

1 Like

I’m starting to have a strong dislike for Objects…

Try this patch on for size.

It’s probably worth adding if ndef checks immediately before something is referenced to create a default version of the object when it doesn’t already exist. That would give backwards compatibility to older saves when you introduce new objects.

1 Like

Yeah, that it the current plan. I also don’t intend to touch any of the old variables since they work well enough.

1 Like

Still no dice I’m afraid, new error message this time as well.

Error: <>: bad conditional expression in <> clause: Unexpected identifier ā€˜State’. Expected ā€˜)’ to end a compound expression.

1 Like

Pain. Suffering, even. I’ll have to look further into this in the morning.

4 Likes

The error with the Alchemist’s House is fixed by removing the $ prefix from ā€œdefā€ in the following line:

ā€œif $alchhomelock is true or ($def $quest11 and $quest11.stage is 2)ā€.

1 Like

This is a minor problem, but the Noble’s ā€œundignified clothesā€ blurb fails to display. This seems to be due to it being pushed as ā€œblurb-undignifiedā€ while it’s defined as ā€œblurb-undignifiedclothesā€.

1 Like

Yeah, that’d probably do it. Patched.

1 Like

good game but, for later in development i think it would be a cool mechanic for ways to counteract immobility without just losing weight, like the magical equivalent of a mobility scooter or something. and then any later weight stage could be locked behind that. would add a lot more depth id say

2 Likes