#inform 7

[prokopetz]

By contrast, the putting it on, inserting it into, and eating actions are not specified to apply to a carried thing: they perform an implicit taking attempt during their check rules, or may perform one in the eating action's case. [...] [T]he primacy of the carrying requirements rule [means] that numerous actions for which a better response would be an error regarding absurdity instead [attempt] an implicit take, e.g., if the moon is a backdrop, put moon in me would attempt to take the moon and dryly reply: "That's hardly portable."

—Proposals for the evolution of Inform E-0015: World model enforcement, subsection "Implicit taking"

While a discussion of the particulars and motivations of this proposed set of bug fixes is beyond the scope of a Tumblr post, I thought this blog's followership might appreciate the fact that, in Inform's present implementation, attempting to stick the Moon up your butt fails solely because the "inserting it into" action generates an implicit "take" action during its setup, and scenery objects are not valid targets for "take".

[manonamora-if]

Neo-Twiny Jam lil' entries

Because of course I made some. Filled up the max like last years.

The Lady with the Camellias

This is a short prototype parser, inspired by the titular book from Dumas fils. I thought 500 words would be enough to adapt one of the scenes from the book. It obviously wasn't. But hey, I learned how to make a simple Inform 7 game. If yall are lucky, maybe a longer version drop one day.

machina caerulea

A short sci-fi Twine game inspired by the tale of Bluebeard. Similar in style to last year's Collision. There are 3 endings to this one.

Bon Dieu ! Et une lessive aussi ?

Only available in French. A short surreal Moiki game, inspired by an IRL moment. It's really stupid, and it just took me a few hours to make. Make Moiki games, it's simple and fun!

[golmac]

This week on let's make IF...

[randomarceus]

You know what? Fuck you. [silently randomises your perception stat and changes the 'look' dialogue depending on what you got]

[definitelynotplanetfall]

me when i'm good at code

[bleedchan]

in inform 7, i’d like if it was easier to quickly pare parser verbs and overwrite the default responses, as well as enable things like lowercase only. i know how to do these things, but as a writer with i guess you could say a modern sense of prose it’d be nice to have it tied to like a ui option rather than having to write the same chunk of text yet again

this would involve a bunch of work that would all be similar i’d imagine. like the parser paring would probably be best as some kind of like, scrollable vertical list of entries and fields you can quickly change, or maybe tabs of categories, or something…

in a world where people could probably see i7’s syntax and mistake it for an llm, i think the best path forward is to embrace the totality of control creators have over responses, and the lack of embarrassing unintentional hallucinations that break character or immersion. exposing things like this in ui when it’s simpler and easier to do so is ideal, i think… it all compiles down to i6 in the end anyway, right..?

[sleepingcitadelstudios]

I know SC is made in Twine, do you have any experience in other IF coding languages? I'm trying to learn Inform 7 and it is Kicking My Ass

I am only barely familiar with Twine, sadly, and not at all familiar with Inform 7. However, @golmac has been working on a series of posts about Inform 7 for beginners and his game Repeat the Ending’s current version uses Inform 7.

Hope this is helpful!

[manonamora-if-reviews]

The Loneliest House by Tabitha O’Connell

IFDB - Game - @tabitha-writes Note: this was a La Petite Mort entry, and submitted to the Bare-Bones Jam

Summary: You’ve always been drawn to the lonely old house on the hill outside your town. It’s been abandoned for as long as you’ve lived here; you’ve never seen it get any care or attention. To everyone else, it’s just a part of the scenery. But to you it’s always been something more–a mystery, an omen, a promise.

This is a short parser letting the players use only one command: examine (X / L), where the point is to examine the abandoned house, and its different element, as if you were exploring it. Examining an element gives you a description, which focuses on other smaller elements, which if you examine those will describe further details, and... so on and so forth until the details are simply too small to see, or until you examined all elements to reach the end.

The gameplay reminded me of Nested, where checking an element gives you details you can look out, each if checked will give out subsequent details, and... Except, unlike Nested, TLH doesn't loop back to repeat ad infinitum if you take one specific path.

As for the whole, it felt a bit voyeuristic, especially in the descriptions of each details of the house, as, even if it is abandoned, you sort of see yourself opening the door or looking out the scenery from the window. You wish you could be inside the house, but you can't. You're on the other side of the fency, gazing with envy at the house. It's pretty eerie...

Also: +1 for including a walkthough! -1 for not being able to pet the dog (/jk)

[kastelpls]

Closure

played *Closure* by Sarah Willson and i thought this was a really cute parser game about helping a friend overcome a breakup by infiltrating into this dude's room and finding objects to help her move on.

there's a lot of personality in the writing and i quite enjoyed the interactivity in the game. also, was surprised to see how the online version used instant messaging client-styled visuals.

that was adorable lol.

[firestia]

Little pony princesses 💗

[prokopetz]

For all the development issues it sometimes causes, I appreciate Inform's absurdly detailed world model for the unhinged debugging output it produces. Like, what do you mean you're checking whether the "must remove worn clothing before eating it" rule is applicable? Exactly how often did this come up that it needed to be part of the standard world model enforcement rulebook?

[ryllen]

the next thing u know, yuu would have the possession of malleus' bones

[golmac]

Do you remember when I posted about a new IF magazine about theory and criticism? The first articles are coming very soon. Please look forward to it!

[tomi4i]

It didn't started in 7 October

[definitelynotplanetfall]

Annoyances from dealing with backdrops in I7. Backdrops suck and you shouldn't use them.

Backdrops are objects that can be seen and interacted with from multiple locations, as opposed to most objects which have exactly one location at a time - except this is faked. They are regular objects that Inform moves around to follow the player and the player specifically. If you have a "sky" backdrop that is in every outdoor room, checking "if paul can see the sky" when Paul is not in the same room as the player, it will fail even if he is in a room that the sky would be in if the player was there. If you want NPCs to do stuff independently while the player isn't watching, and need them to do these things programatically/simulationistically rather than teleporting and hardcoded-state-setting between setpieces, then you had better hope they don't need to interact with any backdrops to do this.

When you create a backdrop you can set its location in 3 ways:

as an arbitrary set of rooms.

as everywhere in a given region. (functionally the same, as regions cannot change during play.)

as a description of rooms - it will show up in every room matching some description.

Let's say I want to make a door that can be moved around, because I7's built in doors cannot (I gather because they are shackled to the specification of I6). Consider this code. (>'s are because tumblr handles indentation poorly.)

When play begins (this is the initialize pseudoor locations rule): >repeat with D running through pseudoors: >>move the D backdrop to all rooms connected by D.

This does not compile. The reason this does not compile is it assumes the stupidest possible intention: to store "rooms connected by D" as the condition for rooms the pseudoor is in. The compiler wags its finger at you because at the time the condition will be checked, the variable D will not exist. There is no way to bake the description so it becomes "all rooms connected by <whatever the current value of D is when the code runs, and then keeping that value when D changes or goes away>". This makes descriptions great for enabling sweeping rule conditions and the like, but makes them basically useless to store as a value.

Well, you could get the list of rooms connected by D, and that's a static list of objects you could store somewhere if you liked. Except there is no way to move a backdrop to an arbitrary set of rooms during play, only when it's initially created. This limitation exists, as far as I can tell, for literally no reason.

Okay, so you can make your own backdrop-ish kind and handle the movement yourself, right? Well that's complicated.

Visibility checks are easy. There is an activity, "deciding the scope of something," which is run exactly once when anything's visibility is checked. So you can move all your backdrops in a "before deciding the scope" rule. A little computationally expensive but not that bad.

There is no place to hook in to run code once per touchability check. There are "reaching inside" and "reaching outside" rulebooks, but these are run potentially mutliple times per touchability check and if you add your code to them, will still fail if you move your pseudo-backdrop to the right location, because all the reaching-inside and reaching-outside checks are already lined up based on where the object was. From within the reaching inside/outside rulebooks you cannot decide overall touchability, only the outcome for that particular layer.

This means that, for rigorously correct behavior, you must update positions before every touchability check that might run for a custom backdrop, everywhere in your code, including rewriting rules and phrases added by extensions, because you cannot add to or override the overall touchability checking logic in the necessary way.

[mlpoutofcontext]