Well, I made the mistake of upgrading to the new version and I now have some compatibility errors that I need to fix. Can anyone help me sort them out?
Hmm. Well I havenât defined a âthingâ as anything as far as I know, but then again Inform is finicky. All Iâve been doing is stuff like â(something) is a thing that varies.â Iâm afraid I canât really post the source as itâs way too big, but if you can tell me how I might have phrased something that defines the word âthingâ then I would probably recognize it.
This did only happen after the update, so Iâm wondering if this isnât to do with some kind of language change.
Ok, this is getting odd. This is the script in question and itâs still doing the exact same thing, but only for the âout of ammoâ line. Nothing else.
A ranged weapon has a text called the shots text. The shots text of a ranged weapon is usually "shots".
A ranged weapon has a text called the reload text. The reload text of a ranged weapon is usually "reload".
A ranged weapon has a text called the reload stem text. The reload stem text of a ranged weapon is usually "reload".
A ranged weapon has a text called the out of ammo text. The out of ammo text of a ranged weapon is usually "You pull the trigger, but nothing happens -- you're out of ammo! â¶[o]RELOAD[x]â".
It looks like [o] and [x] come from Hyperlink Interface by Leonardo Boselliâyou should make sure you have the latest version of it [snipped] rather than the version you can get from the old Inform extensions website. Those are often broken. (Although⊠I canât find anything different between the new version and the old version in that part of the code.) Itâs worth checking, in any case.
It seems like in any case thereâs a bug in the error reporting, because whateverâs going wrong the error message isnât being helpful. But I donât know if itâll be possible to get a simple enough case to reproduce the problem.
UPDATE: Well, I tried installing that version of Hyperlink Interface and it told me that Table of User Styles (continued)â didnât match the old Table of User Styles. I feel like this is a problem that people have encountered and solved before but thinking about it makes me kind of headachey.
DOUBLE UPDATE: It looks like the actual current version of Hyperlink Interface is not on github but on SourceForge, here. I donât really want to download a zip from SourceForge to test this, but if you donât have the latest Hyperlink Interface you might want to grab it from there and see if it fixes the problem.
I should note that failing to define the [o] and [x] substitutions would not cause the error listed above. You can write the test case
The Kitchen is a room.
A ranged weapon is a kind of thing.
A ranged weapon has a text called the shots text. The shots text of a ranged weapon is usually "shots".
A ranged weapon has a text called the reload text. The reload text of a ranged weapon is usually "reload".
A ranged weapon has a text called the reload stem text. The reload stem text of a ranged weapon is usually "reload".
A ranged weapon has a text called the out of ammo text. The out of ammo text of a ranged weapon is usually "You pull the trigger, but nothing happens -- you're out of ammo! â¶[o]RELOAD[x]â".
The error you get is ââŠI was expecting that âoâ would be something to âsayâ, but it didnât look like any form of âsayâ that I know.â
You are right that the [o] and [x] are defined by the hyperlink mod, and I think I should make clearer that it all compiled fine before I formatted the computer and upgraded Inform. Could this be caused by old versions of the automatically included files?
Thereâs lots of unicode up and down the text file so Iâm sure it canât be thatâŠ
I guess itâs not impossibleâa while ago I accidentally modified a built-in extension, and then when I tried to use it in a later version my older modified version overrode the newer built-in one. So you might want to check if thereâs a stray copy of one of the built-ins youâre relying on in ~/Library/Inform/Extensions.
It seems as though (on the Mac) if you look in the Extensions tab of the IDE, the built-ins should have little gray folders next to them, and extensions youâve installed yourself will have little blue folders (which you can click on to take you to the folder containing the extension in the Finder). When I had an old version of the built-in it had a picture of the Inform 6G60 icon with a red bar crossing it out. So if you see one of those, you know somethingâs gone wrong.
Have you tried renaming âout of ammo textâ to something without the word âofâ in it, like âout-of-ammo textâ?
Iâm thinking that maybe âThe out of ammo text of a ranged weaponâ is being parsed as âThe (out) of ((ammo text) of (a ranged weapon))â instead of âThe (out of ammo text) of (a ranged weapon)â, or that thereâs a similar problem elsewhere.
Hi! Iâm Leonardo Boselli. I think that the SourceForge version of âHyperlink Interface by meâ (that is a modified version of âKeyword Interface by Aaron Reedâ) should work with 6M62, at least with little modifications or as it is. Unluckily I havenât tested it extensively because another problem with the Italian Language Extension, discussed elsewhere, still force me to use the older Inform 7 version (since I write IF only in italian).
I hope that the Language Extension problem will be fixed someday (but this hope is OT in this thread).
Thanks a lot, it stopped complaining when I did that! Unfortunately this build of Informâs bug checker is apparently VERY badly broken. Iâm now getting nothing but this error for several bits of script that previously compiled and worked fine:
But when I remove those lines completely it just says:
When authors are avoiding a release thatâs been out for almost five months like the plague, there is something very broken here.
newbie: so I should download the latest the version of Inform?
oldschool: not if you want to have all sorts of incompatible issues with your game
newbie: whatâs wrong with it
oldschool: most extensions donât work with it
newbie: must be a newly released version?
oldschool: itâs been out almost five months
newbie: why donât they fix them?
oldschool: things move a little slowly around here
newbie: okay, so gluxe format is the new standard for larger, modern games?
olschool: yes absolutely. it is the future
newbie: i want to use cool graphics interpreters like Vorple and Parchment to make my presentation look good
oldschool: sorry not compatible
newbie: so youâve written all these cool graphical tools based only on the older, outdated format? That makes no sense.
oldschool: donât question our brilliance
newbie: when will this mess be cleaned up?
oldschool: no idea. could take years. weâre a small community
newbie: So thatâs why all these new authoring tools are surging past you?
oldschool: welcome to Inform noobâŠ