Noctis

http://forums.apexdc.net/index.php?showtopic=946# Okay, I'm gonna try to write a few lines about this (for ApexDC++). Raw commands are used for triggered actions (fake share, forbidden file in share etc. = cheats), your client detects the cheat and the raw command is executed. You don't give them out by yourself, but you can set the raws in your client, and you can assign the raws to certain cheats. First of all you need to name the raw command, so you can indentify them later (when assigning cheats to them). You can do this in File\Settings\Advanced\Misc at the bottom "Raw texts". It's practical to name a raw after its content or after what it does (for example: Kick ) The next step is assigning cheats to the raws. The simplest way and place to try them is (Settings\Advanced) the Fake Detector. After you select a cheat (Fake Share Raw for one) you can select the raw command for it under the cheat list (Set Action... what a good thing we named them before ) Now that you have successfully set a raw to a cheat, you actually need to input the raw command (which will be executed) in Favorite Hubs, in the properties of the hub where you want the raw to work, possibly several ones ("Raw command", above Connection, right to Hub and Indentification ). I am not gonna write here the guide how to create raw commands, Sidey's raw guide is here. If you need any help with them, you can find me @ Tech Geeks Online. A short example for a fake detector cheat is here: $To: %[userNI] From: %[myNI] $<%[myNI]> !kick %[userNI] %[userCS]| If you are in a verli, you only need... <%[myNI]> !kick %[userNI] %[userCS]| Remember: the end of each raw command is always the pipe | (%[userCS] varies depending of the cheat, it contains the cheat all the time, with this the same command could be used for a lot of cheats - in case of the Fake Share Raw mentioned above, something like this "x xxx xxx B - the share size had too many same numbers in it") If you assigned the cheat to the raw, and set the raw in favorites, you are ready to go... You can do the same way with the other cheats in Fake Detector Raw can also be assigned to ADLS entries and client types in ApexDC++. For ADLS: open the entry's properties, and there select the raw (make sure it's enabled ) For (bad) clients: first, you'll need a client list loaded into your client (a good one is http://adminmasterlist.no-ip.org/files/zion/). Then you can select what client or client cheats you wanna banish (I strongly recommend ApexDC++ Speedmod ), just select the client/client cheat in the list, click on Change, and set the raw command for it (left bottom). **PLEASE NOTE** These two last will work only if you use "Check users on join" or you manually check filelists/clients... The ones in Fake Detector are working automatically (Disconnect, Fake Share etc.), of course only if you're OP in the hub. I hope I could be of some help to anyone... (and sorry for the typos)

It doesn't take much time to set it up. Personally I don't pick up new hubs too often, I use the ones that are in my Favorites, and all settings are set there as needed.

Maybe one of the OPs' client automatically checks users' client when they enter... in that case, it detects that it is ApexDC++ emulating.

The point in it is that most hubs will let you in if emulation is turned on. If add the hub to your favorites you can disable it yourself.

Not sure about that, my guess would be no, but never tried. Only way to find out is to try it yourself.

"Why are you sharing with an OP client?" Why wouldn't you? DC about file sharing, and you use (share with) whatever client you want to if we're talking about "legitimate" clients. Some people OP with plain DC++ or non-OP clients, wouldn't it be dumb to bombard them with "Why are you OPping with an user client?" ;)

When you first enter a hub the client automatically enables emulation (I think), and it's also available from favorites as Satan said.

Currently there is no "Refresh IP every [preset] minutes" feature in ApexDC++. Either use "Auto update IP on startup" if it's enough and works out for you, or follow the guide and get a dynamic DNS (no-ip is good too).

Excellent idea, second it. :stuart:

It's not a bug, ApexDC++ simply doesn't have it. Don't make hub selection too complicated, just use Shift + click and Ctrl + click.

Just merge the raw commands with the PtokaX/Grimoire hub side commands.

I experienced something similar like this right after quitting from a game, but waiting a few seconds in my case works out.

Don't use speedmod, it screws up everything. ;-)

Use Shift + click.

Don't replace TGO! ;)

What about the incorrectly displayed uptime? It didn't exist in the previous versions.

It's also available in File menu - Refresh file list.

If you enter a comment for an entry and use %[userCS] the comment will be shown in the kick message.

I think the comment for ADLS is enough for this. :crying:

I would gladly fix scanner settings if I'd be asked to, or I would gladly help work on some hubs as it happens.

That's the bot's bad settings. It's safer just to replace or skip message.

It's a bit hidden, because I couldn't find it in Settings, though it's not invisible... but hey, take a good look around next time. :lol:

I usually search the forums for a crash to see if it has been already reported... but it's not accurate enough if the crashes are not directly posted in the posts (but attached).

Because they don't like if *someone* leeches the sh*t outta them. Get real and don't use fake mods, stick to the original Apex and don't want to finish your downloads in 10 minutes.

Code: c0000005 (Access violation) Version: 1.0.0B4 (2007-08-07) Major: 5 Minor: 1 Build: 2600 SP: 2 Type: 1 Time: 2007-08-13 16:42:18 TTH: 7CNQCQXDGEV7S2IDTUSYEW73M722LLS7BVOOXDI ntdll!0x7C918FEA: RtlpWaitForCriticalSection ntdll!0x7C90104B: RtlEnterCriticalSection d:\cvs\apexdc++\trunk\client\queuemanager.cpp(1431): QueueManager::saveQueue d:\cvs\apexdc++\trunk\client\queuemanager.cpp(1691): QueueManager::on d:\cvs\apexdc++\trunk\client\timermanager.cpp(40): TimerManager::run d:\cvs\apexdc++\trunk\client\thread.h(161): Thread::starter f:\sp\vctools\crt_bld\self_x86\crt\src\threadex.c(348): _callthreadstartex f:\sp\vctools\crt_bld\self_x86\crt\src\threadex.c(326): _threadstartex I was switching to Download Queue window with the intention to remove a file from it, because I accidentally (re)queued a file, that was finished downloading minutes ago.