 |
|
 |
|
Admin
Administrator
Data inscrierii: 12/Mai/2008
Mesaje: 7
|
|
 |
|
 |
|
 Trimis: 12/05/2008 10:13 Titlul subiectului: Rules |
 |
|
ADMINS & HELPERS
* admin/helpers rules
1.
RESPECT, DIGNITY & KNOWLEDGE
2.
Respect to a higher access admin or helper, if you think that you are intimidated or offenced - address to superior hierarchic admin with logs, the last word & decision is reserved to #mIRCBOT manager: xlmpq .
* Do not even dare to kick, deop or ban a team member on service channels (penalty automate remuser).
* Do not quarrel, dispute on service channels (penalty 2 weeks suspend for provoker & 1 week for provoked).
3.
"Disce, sed a doctis, indoctos ipse doceto" - Learn, but from the learned: teach th' untaught.
4.
In order to maintain your #mIRCBOT access status all your activity must be conformed to #mIRCBOT helping rules.
* A global access can be given or removed only by #mIRCBOT manager xlmpq according to become #mIRCBOT admin & helper rules.
* A local access on service channels (for future helpers) can be given only by a global owner according to become #mIRCBOT admin & helper rules.
* helping rules
1. The user can be helped only by one helper: the 1-st who gave voice to user - no one else can intervene, if you think that the helper provides inadequate help or wrong information - inform him politely in private
2. If you think to be unable to help with a specific trouble - ask help on service channel.
3. Once the user helped - ask him politely to part & devoice it, having been insured it does not need anything else.
4. Every user must be helped in an average of 180 seconds period.
5. Do not help users in private or on their channels - everything must be done on #mIRCBOT (everything will be logged & used to evaluate your competence & will be used as proof of your activity).
6. Do not offence directly or indirectly any user, if done - 1 week SUSPEND.
7. Do not ask any favor (like access, shell, bnc, etc. ) for your services, if done - REMUSER.
8. Do not chat on #mIRCBOT channel, this is a service chan & all logs are analysed in order to evaluate your competence & activity, if done - 24 hours BAN.
9. You must help on #mIRCBOT at least 21 hours per week in order to maintain your access status, if less - REMUSER.
10. If you will be inactive for some time, do post a thread in #mIRCBOT forum, specifying the period of time you will be offline. Inactivity period can not extend one month for every 4 months.
12. 3 BANs = 1 week SUSPEND; 3 SUSPENDs = REMUSER.
* purge/suspend rules
1. no-(access|autoop)|banned - PURGE, noreg for 1 week.
2. no-users (9- user average) - PURGE, noreg for 2 days
3. abuse ( bots, 18+|20%+ clones) - PURGE, noreg for 4 weeks (for the channels which have the BOT for 60+ days - SUSPEND, manager convocation).
4. 3 abuses, banned by manager - BLACKLISTED.
5. take|invte|key|limit (channels with no ChanServ, X, Q, etc) - PURGE.
6. flood-(ban|kick|deop) (by users with same/higher level access) - SUSPEND, manager convocation.
USERS
o rules of use for #mIRCBOT BOTs
1. Keep your chan populated, you must have an average of 10+ users.
2. 3d party BOTs: you can have only one BOT per chan - no other 3rd party BOTs, no flooding BOTs, no clones.
3. X & ChanServ services: #mIRCBOT BOT must have 499 access on X, SOP on ChanServ or +oa on L.
4. OP chan status: if you don't have X or ChanServ on chan setup autoop for #mIRCBOT BOT on your bnc (/adduatoop #YourChan:*!BotIdent@BotHost).
5. No BANs, KICKs or DEOPs for #mIRCBOT BOT. If you want the BOT to purge, templeave or cycle use the stipulated commands.
6. Be sure to read FAQ & commands on our site, pay attention on "PURGE TEMPLEAVE CYCLE & SUSPEND" section of FAQ.
o terms of use for #mIRCBOT BOTs
1. Because #mIRCBOT is a free of charge BOT lending service, there is no warranty for our service. #mIRCBOT provides the serivce "as is" without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The entire risk as to the quality and performance of the service is with you. Should the service prove defective, you assume the cost of all necessary servicing, repair or correction.
2. #mIRCBOT reserves the right to refuse any chan for any reason, whether listed here or not.
3. #mIRCBOT reserves the right to remove the BOT from any chan for any reason, whether listed here or not.
4. Only the channel manager/founder can ask/demand an #mIRCBOT BOT (must have 500 X, founder on ChanServ, +n on L or, if not registered, OP on chan)
5. If you had already an #mIRCBOT BOT & it left your chan since of nonconformance to our rules & terms, you will have the right to apply again in a period of 1-4 weeks depending of graveness specified by an #mIRCBOT admin (according to purge rules).
Copyright @ starbots.info |
|
| Autor |
Mesaj |
|
|
|
|
Admin
Administrator
Data inscrierii: 12/Mai/2008
Mesaje: 7
|
|
|
|
|
|
| Trimis: 18/10/2008 14:22 Titlul subiectului: Re: Rules |
|
|
| Admin a scris: | ADMINS & HELPERS
* admin/helpers rules
1.
RESPECT, DIGNITY & KNOWLEDGE
2.
Respect to a higher access admin or helper, if you think that you are intimidated or offenced - address to superior hierarchic admin with logs, the last word & decision is reserved to #PBC manager: xlmpq .
* Do not even dare to kick, deop or ban a team member on service channels (penalty automate remuser).
* Do not quarrel, dispute on service channels (penalty 2 weeks suspend for provoker & 1 week for provoked).
3.
"Disce, sed a doctis, indoctos ipse doceto" - Learn, but from the learned: teach th' untaught.
4.
In order to maintain your #PBC access status all your activity must be conformed to #PBC helping rules.
* A global access can be given or removed only by #PBC manager xlmpq according to become #PBC admin & helper rules.
* A local access on service channels (for future helpers) can be given only by a global owner according to become #PBC admin & helper rules.
* helping rules
1. The user can be helped only by one helper: the 1-st who gave voice to user - no one else can intervene, if you think that the helper provides inadequate help or wrong information - inform him politely in private
2. If you think to be unable to help with a specific trouble - ask help on service channel.
3. Once the user helped - ask him politely to part & devoice it, having been insured it does not need anything else.
4. Every user must be helped in an average of 180 seconds period.
5. Do not help users in private or on their channels - everything must be done on #PBC (everything will be logged & used to evaluate your competence & will be used as proof of your activity).
6. Do not offence directly or indirectly any user, if done - 1 week SUSPEND.
7. Do not ask any favor (like access, shell, bnc, etc. ) for your services, if done - REMUSER.
8. Do not chat on #PBC channel, this is a service chan & all logs are analysed in order to evaluate your competence & activity, if done - 24 hours BAN.
9. You must help on #PBC at least 21 hours per week in order to maintain your access status, if less - REMUSER.
10. If you will be inactive for some time, do post a thread in #PBC forum, specifying the period of time you will be offline. Inactivity period can not extend one month for every 4 months.
12. 3 BANs = 1 week SUSPEND; 3 SUSPENDs = REMUSER.
* purge/suspend rules
1. no-(access|autoop)|banned - PURGE, noreg for 1 week.
2. no-users (9- user average) - PURGE, noreg for 2 days
3. abuse ( bots, 18+|20%+ clones) - PURGE, noreg for 4 weeks (for the channels which have the BOT for 60+ days - SUSPEND, manager convocation).
4. 3 abuses, banned by manager - BLACKLISTED.
5. take|invte|key|limit (channels with no ChanServ, X, Q, etc) - PURGE.
6. flood-(ban|kick|deop) (by users with same/higher level access) - SUSPEND, manager convocation.
USERS
o rules of use for #PBC BOTs
1. Keep your chan populated, you must have an average of 10+ users.
2. 3d party BOTs: you can have only one BOT per chan - no other 3rd party BOTs, no flooding BOTs, no clones.
3. X & ChanServ services: #PBC BOT must have 499 access on X, SOP on ChanServ or +oa on L.
4. OP chan status: if you don't have X or ChanServ on chan setup autoop for #PBC BOT on your bnc (/adduatoop #YourChan:*!BotIdent@BotHost).
5. No BANs, KICKs or DEOPs for #PBC BOT. If you want the BOT to purge, templeave or cycle use the stipulated commands.
6. Be sure to read FAQ & commands on our site, pay attention on "PURGE TEMPLEAVE CYCLE & SUSPEND" section of FAQ.
o terms of use for #PBC BOTs
1. Because #PBC is a free of charge BOT lending service, there is no warranty for our service. #PBC provides the serivce "as is" without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The entire risk as to the quality and performance of the service is with you. Should the service prove defective, you assume the cost of all necessary servicing, repair or correction.
2. #PBC reserves the right to refuse any chan for any reason, whether listed here or not.
3. #PBC reserves the right to remove the BOT from any chan for any reason, whether listed here or not.
4. Only the channel manager/founder can ask/demand an #PBC BOT (must have 500 X, founder on ChanServ, +n on L or, if not registered, OP on chan)
5. If you had already an #PBC BOT & it left your chan since of nonconformance to our rules & terms, you will have the right to apply again in a period of 1-4 weeks depending of graveness specified by an #PBC admin (according to purge rules).
Copyright @ starbots.info |
|
|
 |
|
FAQ 
Mesaje private 
