Servers down for 30m changed something

Quote:

Originally Posted by Tw3ak Well SV still works fine so nothing changed to effect that..Wonder what else was effected other then cotobo...Smells like packet changes to me of some sort but not sure yet. Update: proxy doesn't work anymore either so that is 2-3 of the top hacks not working. 1) cotobo = dead 2) proxy = dead ( good! ) 3) SV uneffected for some reason and still working fine.

OH NOES THE SECRET IS OUT TQ INVENTED SV TO MAKE MORE MONEY :eek: j/p

:eek: Ok NOW My Cotobos not working and Neiters the proxy loggon :confused: A Day after the other servers :confused:

there was a problem changing pass, like if you changed your pass your old pass would still work as the login but its fixed now

Quote:

Originally Posted by scottdavey there was a problem changing pass, like if you changed your pass your old pass would still work as the login but its fixed now

:confused: I Still cant get the proxy to login, no matter what settings I try,,, wonder what therve done this time...

Quote:

Originally Posted by high6 Packet change would require a client update.

If they did plan to do that i dont think client update is needed. Need to check anyway.


My tools are still working, but they are not packet based. I got those login problems too, the one that you couldnt change the password in a successfull way, it is still bugging.

Theres a whole new Loggin packet, TQ where planning this...

Quote:

Originally Posted by giacometti If they did plan to do that i dont think client update is needed. Need to check anyway. My tools are still working, but they are not packet based. I got those login problems too, the one that you couldnt change the password in a successfull way, it is still bugging.

I meant a packet encryption change

My Guess they accidently found a way to stop proxy and cotobo in the last mishap that they had. when every one reported they couldn't use too or proxy, they rolled back to check what happened and I guess they found a way to stop us for now.

Quote:

Originally Posted by raptordin My Guess they accidently found a way to stop proxy and cotobo in the last mishap that they had. when every one reported they couldn't use too or proxy, they rolled back to check what happened and I guess they found a way to stop us for now.

You don't accidentally change an entire packet's structure, size, and encryption. The fix was intentional and will stop proxies for a bit. But my abilities in ASM are limited so it's difficult for me to find what I need.

Quote:

Originally Posted by bone-you You don't accidentally change an entire packet's structure, size, and encryption. The fix was intentional and will stop proxies for a bit. But my abilities in ASM are limited so it's difficult for me to find what I need.

:D I know how you feel, i was going mad doing the V3n0M ASM before, lolz, but your probably a damn lot better at it than me, well the conquer.exe file was equipp'd ready for this packet change in 4355 patch, so was obviously being planned for awhile. :rolleyes: Nasty TQ making us go without nadobot :p

this is so screwed lol......just when i try to log in, thinking in my mind that i will pwn a few pple today i get an error sign!!!!

well now its 6:50 pm in canada and the fu***** thing sais server maintainance....I am gonna assasinate TQ if he gets that other server maintainance that was supposed to happen at 9 pm !!!!

Quote:

Originally Posted by giacometti If they did plan to do that i dont think client update is needed. Need to check anyway. My tools are still working, but they are not packet based. I got those login problems too, the one that you couldnt change the password in a successfull way, it is still bugging.

Hmm, I would say that a client update would be needed as the client wouldnt be able to understand any new packet that the server sends, this can cause unwanted effects, happened when i was coding a private server, kept causing the client to just close.

The update was prior included. Anyway, I got my proxy working + I got it up to date a bit with the latest patches. I'll release it in a minute. ^^

I'm having the same issue. I woke up this morning and have the clients where running fine with CoTobo, the ones that got DC'd couldn't log back in with Cotobo. I've tried it on both 4354 & 4356 neither work. And multi-client still functions normal.

TQ is always screwing around with things lately, I wish they would just leave well enough alone.

Does anyone have a disconnect tool that works?