Jump to content

Recommended Posts

Posted

Hahah how u know it?! xD

U saw it already ?? U licked ?? xD xa0x0a Owned ...

 

GrisoM Ban him ... !! That his bro did so he deserve for BAN!

 

U're SHERIFF SO NOONE CAN BLAME UR FAMILLY!

brzoza did you just get pay to say that ? or you just follow  grisom ass ?

Nothing my business but damn you answer all holysmoke flame's... -.-

Posted

 

Clicked nothing happen ... :P ^^

 

GRISOM BAN HIM HE DESERVE FOR BAN BY BLAMING UR FAMILLY!! (Holysmoke)

 

Grisom did you pay to say that ? or you just follow his ass?

Nothing my business but damn you answer all holysmoke flame's... -.-

 

I just want to reach this topic 500 PAGES!!!!!!!

Posted

You'd better learn some english dude..

 

 

 

And u should teach ur bro some manners!!!

 

@Edit: soz u cant ... u need to learn also -.-"

Posted

First of all he's older and he's just said it for fun.He doesn't even know the ranks here aka he knows nothing about mxc..

you have not to apologise to anyone. (only to grisom)

Posted

First of all he's older and he's just said it for fun.He doesn't even know the ranks here aka he knows nothing about mxc..

 

NOT MY PROBLEM!!! AND BLAMING FAMILLY IS FUN!? LOL !!! IMO U HAVE 2 FATHERS ?? FAIL

Posted

This is a forum not a damn fight can someone add some cool videos to calm this guys -.-

 

@HolySmoke

So if GrisoN ban you is for fun too ^^

 

Im Here to reach this topic 500 pages!! :P

And yes u're right ban for fun uh i love it ^^!!

Guest
This topic is now closed to further replies.



  • Posts

    • LIVE VERIFICATION? SUMSUB? “IMPOSSIBLE”? ▪ Spoiler: it is possible — if you know who to work with. A client came in with a task to pass **live verification** on **WantToPay**, a Telegram virtual card service. On the platform side — **Sumsub**: liveness check, SMS, manual review. “Fast” and “by eye” simply don’t work here. › What was done: → analyzed the verification scenario and Sumsub requirements → built the correct flow: phone number, email, timing → **completed live verification remotely, without account handover** → handled SMS and confirmation codes → brought the process to final approval ▪ Result: → verification passed → access granted → no flags or repeat requests ▪ Live verification is not luck. It’s scenario-based preparation — not hope. › TG: @mustang_service ( https:// t.me/ mustang_service ) › Channel: Mustang Service ( https:// t.me/ +6RAKokIn5ItmYjEx ) *All data is published with the client’s consent.* #verification #sumsub #livecheck #kyc #case
    • IMPORTANT INFO: In a few days, I will switch to completely new code, written from scratch with a new download system, patch building and management system. The Updater will become true 2026 code with "foolproof systems". I'm going to create a Discord server for customers to request new ideas and features. FIRST CUSTOMERS ARE ALREADY USING THE NEW UPDATER ON LIVE SERVERS! Watch this topic for upcoming info because the new updater is around the corner! Yes, you can still use self-update on the previous updater! No, the new updater won't be compatible with the old patch system! A new build is required, but players who already have game files won't have to download the entire patch again! New templates and updates to existing templates are coming soon! Sneak peek:  
    • i used guytis IL project and source. i found in his project there are 3 Client version source... 1,CliExt_H5   --->this one cant be compiled in VS2005,i did know why..is it for H5 client? 2,CliExtNew  --->this one is IL version ,but when i compiled it and use it.player cant login game,MD5Checksum wrong.i check the source code,but not found any hints. 3,L2Server    --->this one for HB client?im not sure...   so my question is what are the differences between these three versions of cliext.dll?how can i fix the issue of the MD5Checksum not matching problem?   01/29/2026 21:04:11.366, [CCliExt::HandleCheckSum] Invalid Checksum[1130415144] vs [-721420287] packet[dd] len[29] sum[2698] key[30] HWID[] Account[]! 01/29/2026 21:04:11.366, SocketLimiter::UserSocketBadunknownprotocol 11111111111 01/29/2026 21:04:11.366, [usersocket]unknown protocol from ip[113.137.149.115]!      
  • Topics

×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..