Cheap scenery extension has several improvements, like conditionally adding some scenery, making it easy to let some objects be “them”-objects (i.e. the player can “EXAMINE CURTAINS. PULL THEM”, and a debug verb to find problems.
Talk menu extension has some improvements, like removing the need for initialization, and defaulting to printing quote marks around what characters say.
Flags extension has two new functions, to easily check if any of 2-3 flags are set or clear, e.g. if (AnyFlagIsSet(F_DOG_ATE_HOMEWORK, F_MARTIANS_LANDED)) ... .
We try to avoid breaking changes in PunyInform, but every once in a while we feel the benefit makes it worth it. When this happens, we typically increase the major version number, like now. This version does have some breaking changes - be sure to read the notes on upgrading in the release notes!
Retro text adventure library PunyInform v5.1 is out.
This release has a number of optimizations. A minimal game now compiles to a 22822 byte z3 file , which is 588 bytes or 2.5% smaller than with PunyInform v5.0.1. This translates to smoother gameplay on retro computers.
Sorry I forgot to announce it. I’ve updated the Inform6Unix package to use PunyInform 5.1. It has been up at https://661.org/proj/if/ for a while now. I’ve just now uploaded the update to the IF Archive.
Please try to coordinate between yourself: Dave releasing his Unix package with Punyinform 5.1 then Frederick releasing PunyInform 5.2 17 hours later is spectacular…
Meanwhile, we’re running a jam. This tends to lead to more people than usual working a lot with the library, which means more problems are discovered, and us releasing a new version or two, so everyone can release jam games with as few bugs as possible.
You can now trust the InScope routine to be executed every time a scope calculation is called for. PunyInform has a habit of caching what’s in scope, to gain performance, and this used to mean that InScope couldn’t always affect scope. This has been fixed, with a very low cost in performance.
The global variable scope_reason which is used in the standard library, is now supported in PunyInform as well. It can be used to decide what’s in scope depending on why the scope is being worked out. E.g. you might add a wizard that casts nasty spells during the each_turn phase. You can safely use scope_reason for this in InScope, but not in add_to_scope property routines, as they aren’t run if the library decides it can use a cached copy of the scope.
A parser bug which would lead to the parser not printing an error message when it should in a certain scenario, has been fixed.
The inform6unix package is now updated with PunyInform verison 5.3. It’s available at 661.org now and the IF Archive when the curators move it to where it needs to go.
PunyInform v5.3.1 released, fixing a bug that made add_to_scope not work properly.
Also, it has an optimization which should make a noticable difference in speed for all games where OPTIONAL_MANUAL_SCOPE is not used and there’s often no user code to run during a turn.
TAKE ALL will now also take animate objects which you can take
talk_menu has shorter versions of the strings to describe the options to end the conversation and show the next page of topics, for screens with less than 40 columns. They’re actually adapted to the smallest screen size on any Ozmoo platform, the 20x15 mode of the Commander X16.
It’s a very minor update, which also means very little can go wrong.
Nah, the Z-machine doesn’t mind using a 1x1 screen. You could even have an LED on the side for MORE-prompts.
Z-machine version 4 and up have the screen dimensions in the header. Some games may refuse to run unless the screen is at least x characters wide, but that’s up to the game (or possibly the library). E.g. Trinity refuses to run on narrow screens.
A typical PunyInform game runs fine on 20x15. If it uses menus (most don’t), the menu options might be truncated due to the 20 character limit, but you can still navigate the menu and choose the different options.
It may be that some Z-code interpreters weren’t designed to handle narrow screens. Ozmoo adapts to any screen size it may come across (20x15 up to 80x60), showing more information in the statusline if there’s room for it.
