Date: 13-04-2018 – 06:06am CEST
| #25 August 03, 2013 :: 09/01/2013 New Server
the new server and thus all services will be online on September, 01st 2013.
We are sorry for the inconvenience. Hier finden Sie die besten automatenspiele kostenlos, Sie haben Zeit, sie zu bekommen!
| #24 June 21, 2013 :: Moving to a new Server
||We are moving to a new Server with much more capacity and efficiency. Brand new compact rowing machine. This is exactly what you need! This is where you will find free pokies online. Follow the link!
The request system and all bots will be offline from July 25th until August 4th.
| #23 July 27, 2009 :: Security on QuakeNet
||Over at Quakenet we thought we should remind you, our users, of a few important things that affect your security when using our network. Try your luck with casino spielen kostenlos ohne anmeldung. Start winning now!
We take security very seriously, and although we work very hard to ensure our users are as safe as possible, you yourselves can take measures against auth phishers and generally nasty people.
This is an often overlooked feature – but if you hide your IP address, people will not be able to do anything nasty to you (such as denial of service attacks) unless they get your IP address from somewhere else. Simply use /mode yournickname +x when authed to Q to hide your IP.
Unfortunately there are nasty people out there who would love to steal the password to your Q account and probably any channels you own. Of course, Q reminds you every time that you should not give your Q account password to ANYONE, not even Quakenet Staff. Please ignore any messages you get asking you to change your password. Report these to #help immediately and we can deal with them for you. Also, please do not type any strange looking commands, if you do not understand what a command does – do not type it! Ask #help if in doubt.
If you were to lose or forget your Q password, you can request it to be sent to your registered E-mail address. But, if you have changed this or can no longer get to that email address, we will not be able to recover your Q account for you. So, please keep your email address current on Q – see /msg Q help email on IRC.
- Keep your details up to date with Q.
We have spent a lot of time writing our Frequently Asked Questions section to help with the common problems and questions about Quakenet and IRC. Before asking #help, take a look at the FAQs first. This goes double for the Security FAQ which contains further details and useful hints and tips to keep yourselves safe and secure on our network.
Of course if there are any questions which are not covered by the FAQs, feel free to ask in #help at any time. We would prefer seeing you asking a silly question that keeps you safe, rather than having to retrieve stolen accounts and channels! 🙂
- Do not forget about our FAQs!
| #22 January 01, 2009 :: Happy New Year 2009
||The whole ErazorBots Team wishes a Happy new Year 2009 to all Quakenet Users.
We hope you enjoyed the last year and prepared well for the new Year. Some new changes will follow concerning our System in the following year.
We wish you once again best luck and well-being!
| #21 June 28, 2008 :: ErazorBots Birthday
time passes… and ErazorBots is 4 years old today.
It`s a really long time and we would like to thank once again
our loyal users who are always on out site.
We do really enjoy our time with you and think that the comming year(s) will be even more better than the last ones.
Thanks for your confidence in ErazorBots team.
| #20 March 24, 2008 :: Q upgrade
||Directly taken from www.quakenet.org
As many of you have noticed we’ve just upgraded our main channel service, Q, to a new version.
This is a fairly major upgrade (the new Q has been rewritten from scratch) but it does replicate all the previous features of Q and add some new ones. There may be very minor teething troubles but we hope to have those resolved pretty soon 🙂 All of your old channel, access flags and other settings have been migrated from the old Q so there’s nothing to worry about.
One of the major changes this upgrade brings is that L has been replaced with Q as well. All channels that had L now have been ‘upgraded’ to Q automatically. L will no longer be on QuakeNet. A list of some of the new features are as follows:
The new Q is a rewrite from scratch, so all the messages the bot uses have been rewritten. This means most responses will be slightly different even when commands are otherwise the same. One general change in this area is that many commands now send confirmation after making a change, e.g. if you use CHANLEV to alter someone’s flags it will show what their flags are after the change for confirmation.
You can now configure Q to either send you NOTICEs or PRIVMSGs. This is done using the new USERFLAGS command:
/MSG Q USERFLAGS +n – sets to NOTICE (default)
/MSG Q USERFLAGS -n – sets to PRIVMSG
Some new flags have been added to users (CHANLEV):
+k KNOWN – This is a new level of access below VOICE (+v). It doesn’t entitle you to getting op/voice on the channel, but it identifies you as a known user. This allows you to set personal flags, and use the INVITE command. It is also used in conjunction with the +k chanflag (see below).
+g GIVE VOICE – Similar to L, this combines with +v to give you autovoice when you join the channel. Note that +av will no longer do this (and in fact is no longer allowed, see below).
+p PROTECT – This protects your op or voice on the channel (i.e. restores it if it is lost for any reason). It has the same effect as +p CHANFLAG, but on a per-user basis.
+d DEOP – This is a “punishment” flag that prevents the user ever getting ops.
+q QUIET – This is a “punishment” flag that prevents the user ever getting voice.
Personal flags are a new category of chanlev flag. Accessed via CHANLEV as normal, these can only be set and cleared on yourself and cannot be seen from others. Note that you will need at least known (+k) access to set these on a channel. The personal flags are:
CHANLEV operation changes
+w HIDE WELCOME – you can set this if you get bored of being spammed with the welcome message every time you join the channel
+j AUTOINVITE – if you set this, Q will invite you to the channel when you AUTH.
Q is now strict about not allowing non-sensical combinations of flags. For example, you can’t be banned (+b) if you are a master – since masters can just remove +b. You can’t have autoop (+a) without op, and you can’t have autoop and autovoice at the same time. Also, the new PROTECT (+p) flag includes autoop/voice functionality so you can’t have +a/+g set if you are +p.
Like L, you can remove any of your own flags (except +b, +d or +q).
A new command GIVEOWNER has been added for the purposes of giving +n to other users. This is no longer possible via a normal CHANLEV command (although CHANLEV still allows for owner removal). The GIVEOWNER command needs to be run twice – the second time using a code provided the first time. This should make accidentally giving away +n a lot harder.
Channel ban features
Q now has a few new functions related to bans, these are:
Channel mode feature
You can configure Q to kick banned users off the channel automatically. This is controlled by the +e chanflag.
You can configure Q to auto-remove channel bans after a certain time. This is controlled by the new BANTIMER command.
You can now set “Q bans” with an expiry time, using the new TEMPBAN command. For clarity, the old BAN command has been renamed to PERMBAN (but BAN still works for now).
You can configure Q to enforce, or prohibit, any combination of modes on the channel (including limits and keys). This is done via the new CHANMODE feature – CHANMODE +mode will enforce that mode on the channel, and -mode will prevent it being set. Note that because both + and – modes are allowed, you have to specify the complete list of modes whenever you change it. This replaces the SETINVITE feature of L, and the +k and +l chanflags and associated KEY and LIMIT commands from Q.
Auth history feature
A new feature to track auths to your account has been added. Accessed via the AUTHHISTORY command, it shows you the last 10 logins to your account with the hostmask (and disconnect times). The old AUTHHISTORY command from Q is now called CHANOPHISTORY.
The list of available channel flags has been overhauled, and the following flag settings are now available:
+a, +g, +p (AUTOOP, AUTOVOICE, PROTECT) These have exactly the same effect as giving the chanlev flag to every eligible user. So you can turn autoopping on and off for the whole channel in one place – although the chanlev flags can still be used as well (either being set is enough).
+c, +f, +t, +b, +p, +w (AUTOLIMIT, FORCETOPIC, TOPICSAVE, BITCH, PROTECT, WELCOME) function the same as the old Q
+e (ENFORCE BANS) – see above
+v (VOICE ALL) – This chanflag will cause Q to voice everyone who joins the channel, unless they have +q chanlev flag set.
+k (KNOWN ONLY) – This chanflag will cause Q to kick anyone who isn’t known (+k or above) out of the channel. Useful for extra security for private channels. It will ban users if they aren’t prevented from rejoining by +i.
Note that +k and +l have been removed, replaced by CHANMODE as described above.
You can now get some statistics including maximum size and total number of joins on your channel. Statistics are maintained from the time each channel is created, but “resettable” statistics are also kept that can be reset. Use the CHANSTAT command to view these statistics, or reset them.
Channel user list
It’s now possible to get a list of all the users on the channel, who they are authed as and what flags they have on Q. In order to get the list you need to be known on the channel and be on it. Use the USERS command to see the list.
And that’s it! We hope you like the additional features the new Q provides, and the upgrade of all channels to Q from L. Have fun!
| #19 February 29, 2008 :: New Quakenet Update
Directly taken from the Quakenet Site:
Channel mode changes:
Channel mode +m (updated):
When the channel is moderated (channel mode +m) regular users (users without a voice or ops) cannot change their nicknames.
Channel mode +r (updated):
When +r is set on a channel (only authenticated users can join) any regular users (users without a voice or ops) in the channel who are not authenticated are unable to send anything to the channel and additionally are unable to change nicknames.
Channel mode +M (new):
The NEW channel mode +M allows unauthenticated users to join a channel, but does not allow them to send (speak) to the channel or change nicknames until they authenticate.
Channel mode +T (new):
The NEW channel mode +T disallows any multi-target messages that are sent with PRIVMSG (normal messages) or NOTICE. This blocks (for example) anything sent by /AMSG with certain clients from showing in channels with +T set.
/AUTH command (new):
All QuakeNet servers now support an easy to remember AUTH command. This command can be used instead of the old method to authenticate to our main network service, Q. For example:
/MSG Q@Cserve.quakenet.org auth [username] [password]
can now be:
/AUTH [username] [password]
This update also reduces confusion in remembering what you have to authenticate to and increases security.
/SILENCE command (updated):
The /SILENCE command now supports multiple hostmasks in a single command, for example:
/SILENCE now also supports exceptions by prefixing the hostmask with a ~ character, for example:
will allow you to see messages and invites from that user even if their host matches another silenced hostmask. /SILENCE now supports CIDR masks to silence a large block of IP addresses for example:
Please note that only CIDR masks that are /16 and greater (up to /32) are allowed for security reasons. /SILENCE now supports authnames using the +x hostname format to silence users by their Q account name, for example:
/WHO command (updated):
The /WHO command now has two additional flags to compliment our other upgrades, these are the a flag to match authnames (account names), which for example can be used as:
/WHO [authname] a
which will return a normal WHO reply for any user with that authname. The a flag can also be used on conjunction with the other /WHO flags such as:
/WHO [authname] a%h
and so on. The other additional flag added is the d flag which lists users hidden by the delayed join (channel modes +D and +d) and can be used as:
/WHO [#channel] d
/LIST command (updated):
The /LIST command now supports pattern matching for channel names, for example:
matches any channel with the string channel in the name. Whereas:
matches any channel without the string channel in the name.
Please use /LIST help to see a full list of options for the /LIST command.
Ident rules relaxed:
The minimum requirement for idents have been relaxed to the following rules:
- Only one ‘-‘, ‘_’, or ‘.’ is allowed (or two, if not consecutive), but not as the first char
- No other special characters are allowed
- Name must contain at least one letter
| #18 October 04, 2007 :: ErazorBots Member left
||Our Trial Member Desajn has left ErazorBots.
The reason of his parting was: no time.
We wish him all the best and good luck for the future!
| #17 September 07, 2007 :: ErazorScript 1.6
||A new version of our ErazorScript has been released.
The changelog is included in the .zip file! [Download here]
The importest script which has been added is an auto updater.
From now on the menu checks itself if there is a new version available and informs you.
Please update your existing script to our current version!
| #16 August 12, 2007 :: ErazorBots conversion
||We decided that it is the best if we return to our old ErazorBots team.
Qrone, Juupke and Trixzaz have left our team.
Thanks guys for the nice co-operation.
New members who joined our team are Desajn and Monken.
We hope that due to the conversion something becomes better and with ‘something’ we mean Support.
| #15 August 03, 2007 :: Webrequest edited
||Although the Webrequest worked without any problems, I decided to edit it once again.
It is more quicker now and the Style has changed.
| #14 June 28, 2007 :: ErazorBots got Birthday!
||ErazorBots became 3 years old!
Another successful year with many users and many support. We think it can only become better!
Several updates and actions have been made.
Webrequest has been edited and the members of EB have also changed.
| #13 September 29, 2006 :: Requirements have been changed
||The requirements for requesting a bot had been changed. Now the bots don’t need master-flag on L/Q. In fact this was against the rules of QuakeNet we were forced to fix it.
| #12 September 20, 2006 :: Updated botscript to version 1.1d
||After that what happend on #ErazorBots yesterday a pre-update has been applied today.
All “auth-bugs” should be fixed now.
Update to version 1.2 will follow soon, hopefully I’ll be able to finish and apply it this weekend.
See you on #ErazorBots
| #11 August 13, 2006 :: Notice
||Some Quakenet User do not want to get it!
We won`t remove any Bots on request!
The only User who is able to remove a Bot is the requester.
Please accept this rule.
| #10 June 28, 2006 :: ErazorBots got Birthday!
||Today ErazorBots became 2 years old!
We would like to thank all users who believe in us!
The beginning was hard, but we grow up more and more.
With the time we became more experienced and our system became better.
For the future we want to provide the best security and support to our users!
Yours ErazorBots team!
| #9 June 06, 2006 :: Webrequest done!
||Today we finished our work at the Webrequest System.
Now you can request also via this page.
In the past there have been some users who have had the same question:
“Why do my team mates get banned?”
I want to explain once again, that only masters and owners are allowed to perform any actions without getting punished!
*Thanks a lot to ziro for scripting the TCL base!
| #8 April 13, 2006 :: ErazorScript 1.4
||A new version of ErazorScript has been released!
Several bugs have been fixed, the menu structure has changed, the help file has been updated and more.
You can download it here!
Notice: This menu is not a full TCL script of our Bots.
It is written in MSL and makes the administration of our Bots much easier!
| #7 February 27, 2006 :: New Server!
we switched to a new Server, which has more perfomance and is much more reliable to us.
So all Bots are back at QuakeNet to offer you a superior quality of our ServiceBots.
After the USV failed in the Computingcentre, it was our desire to use the upgrade Option on the Server.
Special thanks, goes to our Carrier (Hetzner) !
Best Regards, PlusOne / Ziro / Johnny.
| #6 November 26, 2005 :: Server problem
We have had a problem with our Server and we are really sorry about what happened.
The problem was that our harddrive crashed and we had to set up the server again.
It took a lot of time but finally we got it, thanks to PlusOne!
Tomorrow we will reset the whole database so that everybody is able to request a bot again.
We hope the bots will be online thit weekend.
Thanks for your support and your trust in ErazorBots!
Yours, ErazorBots Team.
| #5 November 06, 2005 :: Welcome crichton!
||Today the ErazorBots team got 1 new Member,
It is crichton.
His supported languages are german and english.
The whole ErazorBots team welcomes crichton and wishes him best luck!
Have fun with us crichton!
| #4 November 06, 2005 :: Suspension check
||We have included a new function on our website where you can check if your channel is suspended or not.
| #3 October 12, 2005 :: ErazorScript 1.3 released
||A new Version of ErazorBots mIRC plugin ErazorScript has just been released!
You can find the changelog in the zip-archive.
| #2 October 08, 2005 :: New Update has been released
||Today a new Update has been released!
Several Bugs have been fixed and a new function has been added.
User complained about that the Bots react slowly sometimes. This problem has also been solved.
You can read everything at our Board !
If you find any Bugs or have any suggestions please tell them us.
| #1 August 15, 2005 :: Update
||We lowered the requirements.
The old limit of 30 User has been changed to 15 User.
Enjoy our Bots !
Current server uptime: 122 days, 21:41h
If you have a question or a problem, join our
or send us an e-mail at firstname.lastname@example.org