itch.io

Thanks for your work! It should nail it down. Don't worry about the extra tags. It is not bad to remove them with a Python script.

If I recall correctly there is one point that is not an anagram but an action around then. It isn't meant to be anything too crazy.

Again, I'll look into this with my current build, and I'll try and verify it in the build that's up on itch. I think I did a lot of testing of the GLEAN feature, so it may be fixed already, but I want to make sure it is, if that's the case. What you're seeing should never happen. 

Poke me in a few days if I don't respond. Thanks again! This may be the motivation I need to throw out a new release ... there are a lot of small features like speeding the parser up, and there are other things fixed too.

BTW, the typo you caught?  My source control says it was fixed on May 26, 2024. So I really do need to update the binaries! It's good to have the motivation.

Another question, as I just looked into the code: what you're seeing is for if someone tried, say, GLANE or AGNEL. It (as you guessed) really shouldn't happen with GLEAN or ANGLE. If nothing else, the game should say

> You see a small story unfold.

> Unfortuanately, I didn't account for this game state, but I should have. Let me know.

(Also, this should not lock you out of winning the game. I can give a hint to an individual puzzle. But again I want to fix the bug!)

Ouch! Glad you're enjoying it so far, but can you give a transcript of where it doesn't work? Also, what happens? Does it just say "nothing here" or is the text actively misleading? (Either way, I want to fix it. But the more serious it is, the more likely I am to fix it quickly.)

To get a transcript, you can just type TRANSCRIPT at the command line, then give a score and note what you've done, then TRANSCRIPT again. (Even a screenshot works, though you can also feel free to cut and paste text and print it here.)

If you're on a web browser, I think the game saves *somewhere* but I'm not sure where.fac

I have planned to put out a new release & fix bugs like this. So if I can add this to the pile that would be motivation. The release is overdue.

Hey, thanks or the nice comment and the follow -- it reminded me I had an update planned & motivated me to get started on that update again. Along with updates for other games I wrote in this vein.

Nothing earthshattering, no new puzzles, just fixing bugs and adding new cover art, but it's something I wanted to do for a while.

I liked this. Hope you are able to get the full dialogue together in another work. It'd be worth checking out!

I was amused by what happened when I tried to go through faster the 2nd time through. The title reminds me of what I thought the Internet would be like now. It's a bit different.

Belated thanks, I *hope* this is fixed in the latest build if you're interested. I actually think this was an erroneous fallthrough -- the TLDR is that I had a "return;" inside a loop when it should have been outside. I had a lot of work to do with the hints. It feels like there might be some special cases still to knock out, but this one seems fixed.

Thanks for releasing the source! I learned a few things from it. In particular I'd never used the <TEXT> highlighting before & I think that'd be really useful in the future. It seems like one more good reason to try the betabeta. (I tried it in classroom and it didn't work.)

This was a worthy winner! I forgot to comment on it, but I liked a lot of the mechanics with placing stuff on the table and what happens if you do it wrong. They are very good bumpers without feeling too hand holdy.

I enjoyed replaying through once I was pretty sure I'd forgotten the precise solutions. I'm the sort of person who glosses over story at first to concentrate on mechanics/puzzles so I got a lot out of the second playthrough.

Very very belated thanks on this one! That's a good bug to find. I figured something like this might slip through. It's a few lines of code fix. Thanks for checking my game out too. Hope you're enjoying the other TALP entries. 

Thanks for letting me know, sorry about the problems but very good to hear from you! I'll check what happened ... so many old releases I want to fix but I never make the time.

Thanks for the report! The culprit was a build error. I'm sorry about this -- I recognized this sort of thing happens if I put too much off, but I may've tried to add too much. /__site/andrewschultz.itch.io/big-deal-oh/devlog/1507726/version-110-i-uploaded-... has the details. TLDR is I moved puzzle mechanics code from the west side room to the east side room but forgot to move the description code until a tester showed me and I fixed stuff.

You're not the first person to report this, and a voice in the back of my head told me not to add too much on the final day, even if it was relatively low-risk, especially since I always seem to find a way to bungle uploading stuff to Itch.

The TLDR is that you can see the end in the new version by typing TESTJUMP PERCH to get to where you have 26/29 points and are just south of the gate, and the rest should work, with the scenery you ROT13'd now in the correct place to the east. If you use the old version and go west and type your command, you'll get a point but (small voice) I delayed typing the conclusion in until the final day, so it just says "Narrative text." So I think it's better just to see the end with the TESTJUMP command.

I'd have gotten away with doing stuff so close to deadline if I'd just remembered to run a certain script. Because I didn't, I pulled an old version of the HTML file I compiled at 8 AM, not the very latest. I compiled just before 7 PM, which had a lot more low-risk things I implemented on the final day including implementing a lot of objects. (I could/should have uploaded a new build immediately once I fixed the bug! And I didn't give myself time to check the published-on-itch version. There are so many ways I could've worked around all this!)

The hints were also targeted with the final day's changes and so did not make it up. They still may be a bit wobbly. It's a long story but TLDR is, I had the HINT _ code rely on the number from X ME, and the I checked this *before* the loop for giving hints. So the game did very badly about offering hints when the next act wasn't a point solving action. 

I have a testing command that shows the results of typing HINT each move, and I'll need to use it during a walkthrough to catch straggling cases.

Thanks again for finding good bugs. The HINT was a feature I thought I could build on, given that I cut/pasted a lot of code from other games. And I realized there would be some confounders. But there were more than I thought.

I'm going through entries in the Short Games Showcase, and I played through this, and I'm glad I did! I've played a lot of Groundhog Day style entries where you control one person, but I don't remember many with two.

I like that there aren't *too* many choices to feel overwhelmed, and I like how you can "pass" to figure what the defaults are.

I'm amused at why I missed out the first few times, but I can't get spoiler tags to work so I don't want to spell it out.

I wondered about the significance of the stop names too. I googled and saw Lorem Ipsum and translated it, and it's cool to read more here in the comments. I'm glad I was exposed to this via the Short Games Jam!

Pickles looks like my old cat Simba, except he had a black nose.

I also made the mistake of rubbing his belly once before googling "do cats like their bellies rubbed." Oops.

Hey, somehow I missed this comment, but I'm really glad I saw it now. Thanks so much!

It was a nice boost to help me re-release the game with stuff that couldn't fit in the 4-hour window. I had a lot of fun making it and touching it up.

Excellent! Starting early should be a huge boon.

(See above for the answer.)

I had fun, but I just don't have any ideas to make a tutorial fresh. Otherwise, I would. Learning Adventuron was rewarding, but I've found myself looking at other projects recently. I don't want to spend time feeling bad about not entering.

Plus I remember how writing my entry got in the way of testing for you.  Not that your entry needed it, but ... I was disappointed I didn't make the time to.

I figured I should decide where my efforts will go, and they'll be to reviewing and testing.

(Also, I have a longer form Adventuron game planned for ParserComp, which I didn't enter last year. So I want to return to that and maybe later to TALJ.)

What the title says. I've always enjoyed playing through the entries & last year I wrote my first Adventuron game, which I always wanted to. It's a neat jam/comp to be a part of. And maybe I can help those folks who didn't make it in time last year or who need last minute testing this year.

blurglecruncheon@gmail.com. (Mods, if you'd rather we not display email addresses, I can change this.)

Ugh, thanks so much! And sorry for the inconvenience. This is something I thought I checked, but I was in a rush to get a post comp release out & didn't even check what was up. Should be fixed now. I checked the other 2 EctoComp games too.

(Also, this pointed out a weakness in my copy-over scripts. They copied a file to index.html and download.html. If I'd named the file, say, download-csda instead of download, it would've been immediately obvious. So this will make release 3 that much easier to release with less worry this will happen again!)

Well done. This reminded me of an incident of far less magnitude which I won't detail so as not to spoil things. But it helped provide closure to something uncomfortable, so I appreciate that very much.

Thanks for your comments! Yeah, it's a bit frustrating, I originally thought "oh it's straightforward" then I realized there were alternate pronunciations based on dialect but by then I had too much of a game to junk it.

I had lots of fun with this. Let me be another player to say, well done. Mighty Owl is a funny NPC.

Thanks! I think one thing that really helped was, I copied a *lot* of code from this one to the bigger ones. So that was a help. As was being able to auto-generate it and use speech to text.

Good job with your entry, too. I had planned to go back and look at the good IFComp entries I missed, and working through it definitely motivated it to get back around to your IFComp entries.

Thanks for your kind words! I was looking to make something that was simpler than the Inform stuff I wrote, because I realize it can get tangled, so it' good to know it was a move in the right direction. I had a lot of fun writingI wanted people to just have fun working through it too

Thanks, it was a runoff from my IFComp entry. I wanted it to just be fun. Comments like yours have been a nice boost to fix up the post-comp version.

Thanks! I was looking for a way to keep things simple so people wouldn't be bogged down as they are with my Inform games. I was going for a "fun" angle here.

And yes, I was especially pleased with the zoo. It was actually quite fun to google image search and draw MSPaint pictures based on them. (small voice: yes, also, I was too lazy to draw a Giraffe head. It was tricky at that resolution.)

Hope you find time to get through all the games. I hope to get through at least half.

Yeah, it was a close thing ... I did have to punt a few features to post-comp! It helped I was able to generate a lot of the similar code with a python script.

(And, of course, I double-checked that graphics didn't count against the time limit.)

Wonderful! I appreciate the quick response, too ... helped me fix a few other things so I can get the post-comp release out quickly.

Thanks! No problem there. I just put a note on the front page. If you'd rather I not, I can delete it.

Thanks! That helps me sort out the endings I got.

I'd assumed witch/zombie/ghost were 0/1/2 right.

I always enjoy a cute bitsy game!

Okay, we quickly see the cuteness is only in the graphics, and I enjoyed the subversion of the book very much. Poor munchkins!

The player can still solve the game if it is unfixed. However, it looks really bad. It's a quick fix -- I twiddled a boolean state wrong.

Is updating acceptable (it's not game-breaking, only graphics-breaking), or should I just put in a note "Don't (command that causes the bug)" on the front page?

Thanks! I was able to copy over a lot of repetitive code & also generate a lot too with a script from an earlier Adventuron game & speech-to-text saved a lot of time too. (It also helped that I had the idea in July, so I never felt rushed & I could plan out how to produce code.)

Adventuron's coding is also simple by design ... I'd be interested in what you could do with it if you had a fun small project. Adding graphics is especially easy.

Oh no! I forgot to mention HINT helps with the first puzzle. After that, it helps with the X ME hint-item.

Until then, you can try X ME to find a hint item that will tell you something about the right phrase. The game title is a clue.

Fun clever use of adjectives in Adventuron!

(small voice) I'm still figuring out the last one, though, I think. I've gotten a ghost, witch and vampire to appear and assume that's a clue as to which clothes I got right.

Very fun. Congratulations on making a maze enjoyable!

I didn't have the heart to be a brat the first time through. I visited all the houses.

I've definitely used EctoComp as an excuse to write more than one thing & I don't think I'm the only person! I've found the entries I started first generally tended to be significantly higher quality than my second ones, especially if I got the first ones done very early. So this is a poke to try and do something every day to have more than one entry.

Thanks so much! It's cool to get a note on something I wrote a while back, just for its own sake and for motivation to get (back) to work on my next project.

Great to see you updating things! Hope your other projects are going well--the BDB project looks formidable and worthwhile!