UnrealIRCd Forums

Well, that's your opinion. I can assure you if I put it to a vote, it would not be 99% agree with you, it would be about 50-50. I talk to many people who hate the prefixes and refuse to enable them. There's virtually no functional difference between the two, so what the fuck does it matter? Choose ...

And how is Anope supposed to know whether prefixes were enabled or not?

Well, maybe if you guys would make up your damn mind and standardize it already, we wouldn't have this problem.
It shouldn't have been a changeable option in the first place....

Again, false info. Prefixes have NOTHING to do with services. They are only sent to clients, NOT servers. So whether Anope handles & and ~ is irrelevant That's why Anope still sets users +qo & +ao right? (+q & +a is all that's needed with prefixes enabled)

Modes AOz: I still think support is not ...

That statement is grossly inaccurate. I talk to the Anope coders almost every day and they are constantly working to add support for new features in Unreal and all the other IRCds it supports. Anope works perfectly fine with 3.2. Not really. Just try using any of Unreal3.2's new/changed features ...

Currently the best for Unreal3.2 would be IRCServices. Anope and other services haven't yet been updated to support anything past Unreal3.1.x.

And 25ish human users (without fservs/xdccs/bots) don't use that much bandwidth. You'd probably be fine with outlandz's 10GB $8/month IRCd starter shell (and it includes 3 bg processes, enough for 1 IRCd, 1 services, and 1 NeoStats process).

http://www.outlandz.net/ is my current shell provider. They're great.

I saw that same error trying to compile Unreal on FreeBSD once... think it had something to do with the environmental variables I had set.

It is my understanding, if I want SSL, and ZIP links as well, it will not be
as simple as you make it out to sound. Actually, it's quite simple.

OpenSSL support:
1. download Win32 OpenSSL v0.9.7d and install to C:\WINDOWS\OpenSSL
2. edit the OpenSSL configuration in Unreal3.2\makefile.win32 so ...

k. According to all I found out from Googling, the Toolkit DOES NOT include nmake.. so, I guess I'm screwed.. ;_;

I installed the Core SDK, and Visual C++ Toolkit 2003, and am unable to run nmake. Searching for *nmake* finds only "C:\Program Files\Microsoft SDK\Bin\Win64\nmake.exe" (this is for Windows 64-bit, right?)..

C:\dev\Unreal3.2>nmake -f makefile.win32
'nmake' is not recognized as an internal or ...