autopilot wrote:

Zeus wrote:Its not a server side block on the WAN IP. I just tested using Departures 9.2 236 work and brought 2 black names into the same room.

It is a Server side block and the reason that Dep's solution works is that it sends random garbage info for the machine spacific info that the pal server requests.

If you really want to know if its the random infomation sent to paltalk servers via the Paltalk Cr@#k then instead of using cr@#k, use the memory loader but use the memory on an unpatched version of paltalk, because the memory loader only removes the check "if paltalk is already running" code within paltalk, If you can not join a room with more than 1 nick with memory loader, then it means paltalk are looking at the client infomation to determin if the same user has more than 1 nickname in a room. And if thats the case we can simply modify our info by sending random crap to paltalk server when we login as is done with the paltalk cr@#k. On the other hand.................... If you CAN join the room with more than 1 nickname then there should be no reason multipal should'nt work because its pretty much based on the same thing, to get around the check if mulitple instanst of paltalk exsist.