Off-Topics
Everything is non related to this forum
Subforums
9,861 topics in this forum
-
- 62 replies
- 4.4k views
-
-
-
- 4 replies
- 574 views
-
- 0 replies
- 642 views
-
- 5 replies
- 651 views
-
- 3 replies
- 537 views
-
- 6 replies
- 456 views
-
- 2 replies
- 381 views
-
- 5 replies
- 787 views
-
- 4 replies
- 532 views
-
- 0 replies
- 371 views
-
- 3 replies
- 577 views
-
- 1 reply
- 397 views
-
- 7 replies
- 1.4k views
-
- 29 replies
- 2.1k views
-
- 9 replies
- 1.1k views
-
- 12 replies
- 779 views
-
- 2 replies
- 662 views
-
- 0 replies
- 367 views
-
- 5 replies
- 471 views
-
- 4 replies
- 712 views
-
- 9 replies
- 567 views
-
- 8 replies
- 737 views
-
- 20 replies
- 1.4k views
-
- 15 replies
- 1.5k views
-
- 1 reply
- 546 views
-
- 4 replies
- 1.2k views
-
- 6 replies
- 659 views
-
- 24 replies
- 1.8k views
-
- 22 replies
- 1.8k views
-
- 2 replies
- 687 views
-
- 15 replies
- 1.4k views
-
- 15 replies
- 1.3k views
-
- 2 replies
- 588 views
-
- 7 replies
- 584 views
-
- 1 reply
- 398 views
-
- 21 replies
- 2.1k views
-
- 6 replies
- 724 views
-
- 0 replies
- 364 views
-
- 6 replies
- 751 views
-
- 3 replies
- 527 views
-
Posts
-
-
By NeoPacket0041 · Posted
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: -
This is a bump: https://databay.com/ -
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
-
