Post by miseri in a "moving" postmortem comments

Viewing post in a "moving" postmortem comments

Hello! Oh I don't mind you being nosy, lol. Thank you so much for the kind words; it means a lot coming from someone so experienced with the software! I loved playing all your point & click games <3

I downloaded the program, actually! I am using it on a Mac if that matters. But it kept crashing when I was first learning how to use Dialogizer properly within the field properties. I was trying to add transitions in it... And, I used like !go which made the system just crashes without warning. (I later learned to use go[] elsewhere in the script lol.) And even with autosave on (or when I saved it manually and exit the program), it didn't save everything.

However, I finally figured out the correct way to code -- it was rather smooth-sailing and I just didn't exit the program until I was finished with the game, haha.

I hope this make senses! Either way, thank you for looking into this!

Millie Squilly6 days ago(+1)

Hi,

So in theory Decker shouldn't crash, even if you write something that doesn't work. And the things not saving sounds like an issue. In the interests of figuring this out so it can be fixed for others, can you let me know what you'd put into Dialogizer that crashed things, so I can try and see if I can recreate it? And also, what sort of things weren't saving?

Also, just want to mention this was a really lovely project that turned out really well, great work!!!

miseri6 days ago(+1)

Oh, that's weird then. Hm. Luckily, I had saved a old build where I had kept that broken code. So, in the field property that I used as a "source" for my dialogue I had !go["Next" "SlideLeft"] . And when I playtest it, clicking the widget that suppose to start the dialogue, whenever it got to that function, it will actually do the function but the program just cuts off before it reaches its full completion.

And abt the saving, it missed like little things here and there like if I had changed a word on widget or moved it elsewhere on the screen. (What's funny is that I just checked my current build, and I see that it didn't save one word I change in the final build I had up, haha. Pretty sure, I had the autosave on.)

Let me know if I should send you the old build itself or anything to help fix this! And thank you so much for the kind words, I'm glad you enjoyed the final product <33

miseri6 days ago(+1)

OH! Also, thank you for the mention in your zine! That was a nice surprise to find out in the web, haha

Millie Squilly6 days ago

Yeah, if you can send me the broken build that would absolutely help!

miseri5 days ago

Sounds good! I'll DM you over on Bsky!

Millie Squilly6 days ago (1 edit)

So, when you quit Decker it pops up the thing about saving your changes, had you been clicking "save" on that? My understanding is Autosave runs periodically (like every however many minutes) so it may be missing the final changes if you make them right before finishing

Edit: I've been told that when autosave is on it will just save automatically so I'm guessing you're not seeing the prompt haha

Internet Janitor3 days ago(+1)

Millie helped me track down the source of your reported crash. A fix is included in Decker 1.60.

miseri2 days ago(+2)

Ah great! Appreciate all you guys' hard work <3

itch.io

Viewing post in a "moving" postmortem comments