You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original issue 66 created by brazilofmux on 2006-09-09T05:15:12.000Z:
On Thu Jul 27 23:28:47 2006, Brazil reported:
Annabelle@Shangrila suggests:
Hi again. If page can't make a prompt (like the y/n question suggested in
5/53), then I think maybe there should be an option. For example
&PAGE_NEWBIE me=1. Then the code for page could be something like:
if '=' in message
do exactly what page always does;
else if first word of message doesn't match a player
do exactly what page always does;
else if this player's PAGE_NEWBIE not found or not == 1
do exactly what page always does;
else
tell this player the page might be a mistake and quit
endif
For example if my PAGE_NEWBIE option is set to 1 and I type 'page name
whatever',and name matches another player, I might see a warning like:
"Your page has no = sign but starts with the name of another player.
This looks like a mispage. If you wish to begin pages with the name
of a player please type '&PAGE_NEWBIE me=0'."
The advantages of this are:
Players who don't have PAGE_NEWBIE set will never see any difference;
Even when you have set that option, page still works the same as
always, unless you both begin your page with a player's name and
omit the '=' sign;
No extra ticks are used for pages that have an '=' sign (since page
always needs to check for an '=' anyways, right?);
When no '=' is found most pages only use enough extra ticks to try
for a match on the first word of the message.
This would be better implemented as a flag, or better a power, I would
think. If there were a @toggle framework like in Rhost that can turn on and
off behaviour options, that could be good too.
[REF: Job 314]
The text was updated successfully, but these errors were encountered:
Comment #1 originally posted by brazilofmux on 2006-09-10T00:38:19.000Z:
Actually, page works as intended. This hobbling of page for users not familiar enough
with the syntax to prevent using it incorrectly would be an enhancement.
Original issue 66 created by brazilofmux on 2006-09-09T05:15:12.000Z:
On Thu Jul 27 23:28:47 2006, Brazil reported:
Annabelle@Shangrila suggests:
Hi again. If page can't make a prompt (like the y/n question suggested in
5/53), then I think maybe there should be an option. For example
&PAGE_NEWBIE me=1. Then the code for page could be something like:
if '=' in message
do exactly what page always does;
else if first word of message doesn't match a player
do exactly what page always does;
else if this player's PAGE_NEWBIE not found or not == 1
do exactly what page always does;
else
tell this player the page might be a mistake and quit
endif
For example if my PAGE_NEWBIE option is set to 1 and I type 'page name
whatever',and name matches another player, I might see a warning like:
The advantages of this are:
Players who don't have PAGE_NEWBIE set will never see any difference;
Even when you have set that option, page still works the same as
always, unless you both begin your page with a player's name and
omit the '=' sign;
No extra ticks are used for pages that have an '=' sign (since page
always needs to check for an '=' anyways, right?);
When no '=' is found most pages only use enough extra ticks to try
for a match on the first word of the message.
On Fri Jul 28 00:02:48 2006, Ashen-Shugar added:
Why not just @hook it?
On Fri Jul 28 00:06:43 2006, Draken-Korin added:
This would be better implemented as a flag, or better a power, I would
think. If there were a @toggle framework like in Rhost that can turn on and
off behaviour options, that could be good too.
[REF: Job 314]
The text was updated successfully, but these errors were encountered: