gHx8
> Bremen is rivals with Lonelywood, Targos, and Termalaine.
When you write it, you effectively get 3 pieces of metadata for 'free' without any extra code:
> Lonelywood is rivals with Bremen. Targos is rivals with Bremen. Termalaine is rivals with Bremen.
> A race is a kind of person. Dwarf, elf, and half-elf are kinds of race.
> A town has numbers called friendliness, services, comfort, and population. Leadership relates a person to a town. The verb to lead implies the leadership relation. "F [friendliness] / S [services] / C [comfort] / P [population]".
> Rivalry relates various towns to each other. The verb to be rivals with implies the rivalry relation. The verb to be rivals of implies the rivalry relation.
Then you can make a town like this:
> Bremen is a town in Ten-Towns. "Founded by dwarf prospectors, the sleepy town of Bremen sits on the west bank of Maer Dualdon, at the mouth of the Shaengarne River.". It has friendliness 3. It has services 1. It has comfort 2. It has population 150.
> Dorbulgruf Shalescar is a dwarf. Bremen is led by Dorbulgruf Shalescar.
And now inform7 can be used to query or act on all this metadata:
> Every turn when the player is in a town: repeat with town running through towns: say "Rivals of [town]: [list of towns that are rivals with town][line break]";
This is the kind of thing you have to work hard to represent in ink because you only have functions, variables, and lists (a hashmap<variable, boolean>). As you add more metadata to inform7, it can make EXTREMELY sophisticated queries or conditions like "list of weapons that were in hidden rooms which are gilded". So for very little work, you can have inform7 reason about whether a player can 'wear' a specific item by checking what they're wearing, how the item affixes to things, and what attachment points you've defined (which can be as broad or granular as you want). And as a bonus, it's also very little code to comment on the player wearing a strange thing (like pants on their head) or wearing colours a specific character thinks clash with eachother.
This kind of query is one of ink's notable weaknesses (and requires quite a lot of lists or very clever lookup functions to achieve). But, ink can leverage its frontend (often a general purpose programming language like C# or javascript) to provide that functionality.
Inform7 is a declarative programming language with english-like syntax. It's quite good compared to ink at simulating objects with a lot of metadata. However, the runtime isn't quite as portable as ink; as a result, Inform7 has no easily located Unity or Unreal packages. Ordinarily, I would recommend Inform7 where you need to process lots of content and randomly generate things. But it seems in addition to having an arbitrary runtime entity limit of 1000 things, those things must exist before you randomize them. Although counterintuitive, procedural generation is more challenging in Inform7 than ink!
Use Inform7 when you need a language that can reason "because Alice's relation to Bob is at -50, Alice hates Bob. Because she hates Bob and he is walking nearby, she can trip him. If she does, he will take a random amount of damage and Bob's relation to Alice is reduced by 20."
Use ink when you need a highly portable language that can script /other/ frontend frameworks or languages. Ink has been used in 2d games, 3d games (notably Heaven's Vault), on the web, and on three different game engines (Unity, Unreal, Godot). Ink is also very good at making variations on text and tracking how often parts of the story have been visited.
They're both excellent tools for interactive fiction, but they excel at wildly different things.