Faqs MOOps alpha!
Questions about MOOps 1.2 alpha
Answers
Why have the buttons in the worldtabs different colors?
The buttons on the worldtabs are in general red and will turn yellow when
MOOps receives data. When you aren't in this world at the moment, they
turn blue till you open the textview of this world, on which occasion they
will turn red. If nothing happens in the worlds while you are away, the
buttons stay red. So when you are connected to multiple worlds you can see
if something happens in a world you aren't viewing.
What is autofollow?
In MOOps you have the choice to set the textview to follow or not to follow.
This is convenient when you want to select and copy a part of the text or
want to read some text again. With autofollow MOOps stops immediately when
you select some text and follows directly after you deselect. You find autofollow
in the menubar behind options.
Will MOOps get a playerlist?
IIn the beta-version of MOOps we are already experimenting with a playerlist.
For more details about new features check out our develop-page develop
Help, I can't connect?
Some MOOs or MUDs have different commands to connect. So when you encounter
a problem with automatically connecting this could be the case. To
adjust this in MOOps go to sessions menu choose the session in which you
encounters a problem. Click on edit and go to commands. Change by login
CO in connect or whatever else command the MUD uses, save and try again.
Some MUDs however
have a protocol to login. On the moment MOOps is not configured to use these
kinds of protocols.
Why can't I use the (dis)connectbutton beneath the inputbar?
This is a precaution so you can't by accident disconnect your connection.
Use instead the button in the toolbar or F4.
Why can't I start the editor in some MOOs/MUDs?
A client-editor is only standard in some MOO/MUD-clients and in most MOOs/MUDs
normally not active. You can activate it with @edit-options +local. When
the editor still doesn't start than the core of your MOO/MUD is using a
different command. Seek advice by one of the Wizards of the MOO/MUD.
I am programming a verb and I can't start the verbeditor.
Probably you started your programming session in the MOO-editor and is your
verb not yet compiled. Compile the verb first or save your verb in a text-file
first, remove the verb and start all over again.
Start now the MOOps-editor with >> /e <name>:<verb>
It is also possible you haven't got a programming-license in the MOO. Ask
the wizards of your MOO.
Can I copy and paste in the inputbar?
Yes that is possible! You can paste with Ctr-v and copy with Ctr-insert.
He, I made a mistake by programming a verb?
Oops, You can use ctr-z or alt-backspace to undo the changes in the verbtext
;). As long you haven't send you verb to the MOO this will correct your
mistakes! See also tips
I am in the editor of MOOps, how do I reach the MOO and how do I send my verb to the MOO?
You can reach the MOO-chatview with F5 or with shift + F5. This option let
you walk through the text-pages.
You can send your verb text to the MOO with the Save and the Save
and Close buttons, try also the shortkeys F7(save) and Ctr + F7(save
en close).
Blink doesn't work?
Whenever the background of the chatview is a picture, blink doesn't work correct.
