2.0/FAQ

From AnopeWiki
Revision as of 12:59, 8 December 2024 by Sadie (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Anope IRC Services - 2.0 General Frequently Asked Questions

When was Anope 2.0 Released? 
Anope 2.0 was released stable: March 23rd, 2014.
How long was Anope 2.0 In Development? 
Anope 2.0 Development lasted for about 5 years before stable was released.
When will Anope stop supporting 1.8/1.9? 
Because Anope 2.0 is considered the latest "stable" version, we strongly recommend upgrading as soon as possible. However, we will continue to provide 1.8/1.9 support until 1 year past the release date of Anope 2.0 (March 23rd, 2015 is when support stops.)
Why should I update to 2.0? 
Why not? Anope 2.0 is the lastest version. Just like when you update the anti-virus software on your computer, it's important to keep Anope updated. Anope 2.0 includes the implementation of many old modules of 1.8 and 1.9, (meaning they are now included with a basic installation.) Anope 2.0 also includes security fixes, and many new and improved features.
Where can I get support for Anope? 
We offer "live" support on irc.teranova.net in #anope. There, our contributors and team members can assist you with any problems.
Does Anope offer Development Support? 
On our IRC Network, you can join #anope-devel to discuss Anope Development.
Is there Anope Support in other languages? 
Anope's wiki translates into multiple languages for the ease of our users. You can also join #anope.fr #anope.es or #anope.de for language support on our IRC Network.
Are there any other places I can get Anope Support?
Although it is the preferred method, If you are not available to use the IRC Network for support, you can post for support on our Forums.
I think I found a bug in Anope! What do I do? 
Please report all bugs on the Bug Tracker.
Be sure you include as much information about replicating the issue as you can. Debug logs are the most helpful.

Anope IRC Services - Changes with 2.0 Frequently Asked Questions

Where did MLOCK Go? 
Use /msg ChanServ MODE Channel LOCK {SET|ADD} modes
See /msg ChanServ HELP MODE for more details.
Why does my chanserv password show up in the channel description? / Where is my ChanServ Password 
ChanServ no longer requires passwords when registering channels. It is linked to your NickServ account instead. They new syntax is /msg ChanServ REGISTER channel description. If you registered your channel, and your password is in your description, you should /msg ChanServ DROP #channel, then re-register. This change also includes the removal of Chanserv IDENTIFY, and ChanServ LOGOUT.
Where did defcon go? 
Defcon is now disabled by default. You simply need to enable it in operserv.conf
Where is the selection for <my language>? 
This is done via nickserv. If nickserv's help set language does not list your language then you need to make sure locale is properly installed on your system. For *nix this is usually done during installation, and can be added via your system's package manager. Each system's method is different, but Debian based distributions will usually use apt-get install locale, while Opensuse will use zypper install locale, other flavors of linux and unix may use similar commands.
Where did the NICKSERV GHOST and RELEASE commands go? 
Both commands were replaced by the RECOVER command. You still can activate this command by editing your nickserv.conf. (search for "ghost" to find the right place)

Anope IRC Services - 2.0 Installation Frequently Asked Questions

I'm getting this error while installing CMAKE_CXX_COMPILER ? 
For Debian and Ubuntu based, or derived OSs type: apt-get install build-essential - Then try again. For other OSs you need to make sure the correct packages are installed.
When I type ./services, it says it cannot find the file. 
You need to cd to the directory you installed services to. Try: ~/services/bin
How do I install a module? 
  1. Download your module into <anope_source>/modules/third/
  2. Type: ./Config -quick to generate the correct makefiles.
  3. Type: cd build
  4. Type: make install
  5. Update your config files in services/conf/
  6. Issue a /msg operserv restart, or use /operserv modload <module_name> to load the new module.