solution 2 stopsome crashes?

um, why dont they create somethng in the game to stop a certain amount of people entering an area <makes some BS about magical barriers ect...> surrounding certain major areas like the ToA temples ect... true it would piss a lot of people off not being able to get into places now and again but no one plays 24/7 <least i hope not >, places like Cornwall, cammy hills ect need not apply, they dont exactly crash the server do they, oh and while they r at it, why dont they just get rid of a lot of the pointless bullshit in some zones for instance -
Darkness Falls- No class can get up the two cliff-faces leading to each others entry ports, so why the hell do we have npc mobs there, to look nice maybe?, but they arent needed, just like 50% of the npc's that waffle on crap 2% of people ever bother to read, get rid of a lot of these npc's/mobs that dont do anything and less lag
just a thought, albiet slightly stupid cos i dont know what im talking about and im drunk

After a DAOCless night this post made me laugh so much

I need my daoc :wub:

if a realm attacking a relic keep does so without taking any keep the guards at the boarder keeps should close the doors for fear of invation and not reopen them for 1 hour. having said that, the realm thats under attack to just port over and camp the boarder keeps of the attacking realm. At least in the RvR revamp they will make it impossible to take a relic without taking keeps first.

Do you remember the campaign ran by GoA ? do you remember desperatly trying to take part but being unable to port to the modified zone due to it being full ?

Cap's are a bad thing and should only ever be considered as a last resort IMHO

For those who don't already know and are running ToA client under Windows XP. Right click on your camelot.exe. Under the compatability tab, check on "Run this program in compatibility mode for:" and select Windows NT 4.0 (Service Pack 5). This reduces framerate issues with the ToA client.

Vochdun said:

For those who don't already know and are running ToA client under Windows XP. Right click on your camelot.exe. Under the compatability tab, check on "Run this program in compatibility mode for:" and select Windows NT 4.0 (Service Pack 5). This reduces framerate issues with the ToA client.

Click to expand...

WRONG.

Camelot.exe is the launcher.

You need to do it with game.dll as that is the actual DAoC game.

Sharma said:

WRONG.

Camelot.exe is the launcher.

You need to do it with game.dll as that is the actual DAoC game.

Click to expand...

Wrong!!

You cant change the compatibility settings for game.dll!

Thegreatest said:

Wrong!!

You cant change the compatibility settings for game.dll!

Click to expand...

true, a dll is nothing more then a set of functions/methods a prgram can call, a dll will never RUN the game, it just helps it execute.

Sharma said:

WRONG.

Camelot.exe is the launcher.

You need to do it with game.dll as that is the actual DAoC game.

Click to expand...

hmm don't you want to make the launcher run in NT mode, as then it'll make anything it launches run in NT mode as well (ie game.dll)?

Wrong. Well.. sort of (you're right too!).

In this case, the game.dll is just a renamed game.exe (rename it to game.exe! Cant start it because the launching process has to be login.dll) (you can bypass this, however).

Thegreatest said:

Wrong!!

You cant change the compatibility settings for game.dll!

Click to expand...

You can change *.dll file compatibilty just as you can do a *.exe.