Ghiaor
Data inscrierii: 06/Iun/2008
Mesaje: 10
|
 Trimis: 06/06/2008 14:43 Titlul subiectului: GLOBAL USER FLAGS |
 |
|
* Q (authorised user) #L&L specific flag. It is given automatically when the user does auth on BOT, if the user has userset permident on BOT he does not need this flag.
* W (X, ChanServ user) #L&L specific flag. Identifies nerwork channel services like X or ChanServ.
* B (#L&L bot) #L&L specific flag. Identifies #L&L BOTs.
* A (antihack) #L&L specific flag. It is given automatically when the user enables antihack option.
* R (reporting) #L&L specific flag. It is given automatically when the user enables reporting option.
* I (invisible) #L&L specific flag. It is given automatically when the user enables invisible option.
* b (bot) standard eggdrop flag. Identifies any BOT, here included #L&L BOTs.
* t (botnet master) standard eggdrop flag. Grants access to botnet master commands.
* x (xfer) standard eggdrop flag. Grants access to file-area & to xfer commands.
* j (file-area master) standard eggdrop flag. Grants access to file-area & to janitor commands.
* p (party-line) standard eggdrop flag. Grants access to party-line & to party-line commands.
* c (common) standard eggdrop flag. Identifies a common-access user record. When 2 or more ppl use the same entrance & as consequence have the same user@host - in order to prevent all these ppl to appear as a single person - a common user record is created & for anyone who will match this record (when added to BOT) a new user record will be created which will identify them by nickname.
* u (unshared) standard eggdrop flag. A +u access level user will not be sent to other share-bots. BOTs can be set up to share user records but if you need a particular user not to be on the rest of BOTs - this flag is to be used.
* h (high-light) standard eggdrop flag. User will see highlighted text as output.
USER SETTINGS
* antihack - enalbed, blocks user's current hosts & will accept commands only from these hosts. No commands will be accepted from any other hosts, even if a maltreater will try to authorise with user's correct password, he will be ignored. Besides, if somebody will try to authorise with user's hand on BOT from an unknown uhost & reporting is ON, the BOT will store a note for user with the details of this attempt (nick, uhost, time & password he tried to use).
Example: !userset antihack on
* info - set a global or local infoline for user (if channel is set +greet, the info will be used as greeting).
Example: !userset info anything about you
* permident - enabled, allow the user to command the BOT from the given host (mask) without authorisation, be sure to specify a unique host. updating.
Example: !userset permident *!*@xuser.users.undernet.org
* reporting - to store a report - when antihack/secure is enabled ?
Example: !userset reporting on
* mail - personal mail.
Example: !userset mail Ghiaor@Ghiaor.NeT
* url - personal web page.
Example: !userset url [url=http://www.ghiaor.net]WwW.Ghiaor.NeT[/url]
* invisible - allow other users to see your information or not ?
Example: !userset invisible on
BOT FLAGS
* s (share) standard eggdrop flag. BOT is sharing user records, aggressively.
* p (share) standard eggdrop flag. BOT is sharing user records, passively.
* g (global share) standard eggdrop flag. Share all channels.
* h (hub) standard eggdrop flag. BOT is auto-linked at highest priority.
* a (alternate) standard eggdrop flag. BOT is auto-linked if no hub bots can be linked.
* l (leaf) standard eggdrop flag. BOT is not allowed to link in other bots.
* r (reject) standard eggdrop flag. BOT will not be allowed on the net.
* i (isolate) standard eggdrop flag. Isolate the party line across a botlink. |
|
