At the moment you find 44 questions and just as many answers under 7 headlines which results in 6.3 answered questions per headline. Quite interesting, right?
/ME-command as I know it from mIRC?VERSION-requests?PING-requests?TIME-requests?*)?@ at the beginning of the nicknames mean?+ at the beginning of the nicknames mean?+o and they are marked with an @ at the beginning of their name in the nicklist of moepII) has the power over the channel; he can kick and ban others, he can change channel-modes and topic and many other things.+v, marked with a + in the nicklist of moepII) are allowed to speak even when the channel is moderated (channelmode +m). In most cases, being voiced hasn't any advantage. Thus, the +v mode has mostly only a symbolic meaning to show that this user is an important person.+m, in such case you need to be voiced with mode +v as described above). #first isn't compelling operator in #second.
IRCUtil.parseColors method).
moep.jar.
On windows sometimes programs like WinRar or WinAce set themselves as default application for *.JAR-files. Change this into javaw.exe. javaw -cp moep.jar org.schwering.irc.moep.MoepIRCjava -cp moep.jar org.schwering.irc.moep.MoepIRCmoep.ini, moepII displays the setup-window before making anything else. moep.jar, you have to add the compiled class to the archieve.
(This can be done with a normal compressionprogram.)
If your module is in a package, you also must consider the package when you add the module: a module modules.new.NewModule has the package modules.new. Therefore the class NewModule must be packed into a folder modules/new/ and then added to the moepII-classpath.
modules.conf in the directory of moepII (if the file does not exist yet, create it).
Just write in it: module0=YourClass. If there are already some modules, you have to replace the module0 with moduleX while X is the number of the last module + 1.
If your module has defined a package, you must write yourpackage.YourClass and not only YourClass, of course.
modules.conf, you can start the client.
By clicking Modules in the menu, then chosing the module and clicking Start, you execute the module.
Depending on the type of the module you also can/must/should stop it later. To do that, click Halt.
org.schwering.irc.moep.Module.
Then it doesn't need any constructor.
Instead, it must define a init() method in which the action takes place -- we could say the init() replaces a constructor.
This is very important, because the module should not affect the client's performance.
halt() method in the module's main class.
This method should do nothing else than stopping the module's action.
The halt() method is so important, because it is used by moepII to stop the module.
So please remind that this method _must_ be defined if your module should be haltable!
AUTOSTART with any value.
The modules which are to be started automatically are started directly after the perform is executed.
The client prints a string like # Automatically started Module: DCCGet to tell the user that the module is started.
/) shows the client that the following is a command and it should not be send as a channel. This command must correspond some standards you will learn later. The client prints the executed command on the open textwindow so that you notice that the command was executed.
.) behind the slash (/). This is useful if you want to send a password to a bot on an IRC network (also in the perform) or anything else to anybody which should not by seen by anybody other. PRIVMSG, the other the NOTICE.PRIVMSG-message is (note the colon (:)):/PRIVMSG <channel or nickname> :<message>MSG which is known to most IRC users from the IRC client mIRC. The syntax of the command isn't typical for IRC commands because it's just a shortcut and no real command of the IRC protocol:
/MSG <channel or nickname> <message>NOTICE, isn't used as frequently as PRIVMSG. Its syntax is very similar, just another command:
/NOTICE <channel or nickname> <message>NOTICE a shorthand, too:
/NOT <channel or nickname> <message>/ME-command as I know it from mIRC? (Top)/ME-command isn't defined in the IRC protocol (RFC1459) -- and that has a reason:
It just makes no sense. So moepII isn't going to support it any time.
The ACTIONs sent by other users with the /ME-command are just a /PRIVMSG which is lead by a special char and the word ACTION. At the end of such /PRIVMSGs there is a special char again.
The /ME-command is displayed as a usual /PRIVMSG lead by the word ACTION in moepII.
VERSION-requests? (Top)PING-requests? (Top)PRIVMSGs.
TIME-requests? (Top)Add button to add a banmask. You can also simply execute MODE <channel> +b <banmask>. You can get the banmask by whoising the user you want to ban.*)? (Top)+k anyKey) and the mode secret (+s).
For security purposes the channel-key is hidden behind a star (*). When you switch on the ChanCenter now, there the key-mode is activated but its value is just the *.* by the channel-key which was set. Of course you know the key, because you recently joined.
@ at the beginning of the nicknames mean? (Top)@ are operators of the channel.
Operators hold the mode +o in the channel.
+ at the beginning of the nicknames mean? (Top)+ are voiced in the channel.
Voiced users hold the mode +v in the channel.
@ or + mean that this is a normal user who holds no special modes in the channel.
Nicklist -> Order List ascending.
Ctrl + Page Up and Ctrl + Page Down to switch the tabs.
X or sending a PART-command.
You must use the special Options -> Window -> Close or right-click on tabs -> Close Brutally.
You should always use the part-function (the X button at the right top or right-click on tabs -> Part) instead of the close-brutally-function if you can.
1--\
A D---4
2--/ \ /
B----C
/ \
3 E