-        roomIdToolTipText = singleParagraph.arg(tr("Entered number is invalid, set the number of the room that this special exit leads to; "
-                                                   "if left like this, this exit will be deleted when <tt>save</tt> is clicked."));
+        roomIdToolTipText = doubleParagraph.arg(tr("Entered number is invalid. If left like this, this exit will be deleted when <tt>save</tt> is clicked."),
+                                                tr("Set the number of the room northwest of this one."));

etc. in spirit of #5556

I don't think it's wise naming the games here, because the list will change and this string will age unneccessarily

Then again, I never even knew of this prerequisite, or how to describe it better maybe.

I only found out when I looked to see where it was used - it isn't anything in the C++ core code but something in the Lua stuff that makes up that package and the original text always niggled me, it being "(Lua scripts need to be prefixed with \"script:\")" when I knew that wasn't the whole story...

OK but I was wondering, why is that required then?
Looking at the mudlet-mapper scripts, they actually have it coded:

  if string.starts(cmd, "script:") then
    cmd = string.gsub(cmd, "script:", "")
    loadstring(cmd)()

So now I am puzzled as to why Mudlet would hint at using a game-specific feature at all.
That is not done for other games, and not done for other features of the same script either.
To me it seems now, this is a slippery slope and maybe the text should actually be removed.
The script/authors usually should take care of informing how to use it, not rely on a client tooltip.

Let's remember that this has not been a source of confusion or a problem for anyone, I suggest not treating it as one until it actually manifests itself.

When there are two separate ideas, don't put a comma instead of full stop.

The ideas "No command or Lua script entered, if left like this" did not have any connection intended, did they?

Actually the ideas are connected - the absence of a command or script entry will, if not corrected, cause deletion.

Yes the two ideas are connected, but read that part again. It says: If you leave it like this, nothing is entered. They are not connected that way, no?
What you probably intended to say was ".. and if left like this, then .." so that is where I suggest the full stop instead of "and".

See suggestion from above

See suggestion from above

See suggestion from above

Keep it at 0, even though setting it to -23 could work as well, that sentence had too much info already.
Switch the options, mention the most simple one first.
Split the first idea off to make it shorter.
Replace more CAPS LOCKED words.
Use common "roomID" syntax.

Keep it at 0, even though setting it to -23 could work as well, that sentence had too much info already.

Sorry but I disagree, as it also warns that any value less than one will always cause exit deletion and not just that single value of zero - and in English, when referring to a number with an absolute value less than 100 it is usual to spell the number out in words...

Switch the options, mention the most simple one first.

The simplest one is click on the exit and press delete - and it works on multiple exits at a time (but I wasn't going to mention that)!

Split the first idea off to make it shorter.

Not sure about that as the previous point also alludes to click-and-drag to select several exits at a time. I guess it does improve the readability if it is a separate sentence.

Replace more CAPS LOCKED words.

Well, I thought that using OR helped to separate the alternatives, but will try with an "... either: xxxx; or yyyyy; or zzzz." form.

Use common "roomID" syntax.

Yeah, I am making that change throughout - even though it offends my sensibilities - as we have previously had that discussion about identity (noun) / I(dentiy) D(ocument) --> ID (abreviation) / Identity (English, capitalised, proper noun) and the democratically derived result was ID...