Quote:
Originally Posted by alexander337
Hello epvp community , i just need some help in the following if you could help me what i need is source codes that you can share or willing to share with me
I need the following if you have them:
Filters
Bots
Addons
Auto events
Tools
Db tools
Media tools
Queries
Fixes
Etc
I will not use the souce code as is it wil be used as a reference to modofy my own project that I'm working on right now and i would really appreciate if you could help me
Also if you can help me by pointing me to threads that concerns securing the game and the vps , firewall, and protection against cheats etc that would be greatly appreciated
Sorry for my bad English and thank you for your help in advance
|
what design ***approach*** are you following for your project ؟
************************************************** ***************
icrosoft Windows [Version]
(c) Microsoft Corporation. All rights reserved.
C:\Users\romio10>cd C:\Users\romio\romio10\AI Reverse Studio
C:\Users\romio\Desktop\AI Reverse Studio>tree /F
Folder PATH listing
Volume serial number is 0C6F-BDE2
C:.
│ main.py
│ requirements.txt
│ sro_client.exe
│
├───ai
│ classifier.py
│ explain.py
│ rename.py
│
├───analysis
│ │ call_graph.py
│ │ class_analyzer.py
│ │ function_finder.py
│ │ function_linker.py
│ │ import_analyzer.py
│ │ network_analyzer.py
│ │ network_finder.py
│ │ opcode_finder.py
│ │ packet_extractor.py
│ │ packet_finder.py
│ │ report_generator.py
│ │ string_analyzer.py
│ │ string_finder.py
│ │ xref_finder.py
│ │
│ └───__pycache__
│ call_graph.cpython-311.pyc
│ class_analyzer.cpython-311.pyc
│ function_finder.cpython-311.pyc
│ function_linker.cpython-311.pyc
│ import_analyzer.cpython-311.pyc
│ network_analyzer.cpython-311.pyc
│ network_finder.cpython-311.pyc
│ opcode_finder.cpython-311.pyc
│ packet_extractor.cpython-311.pyc
│ packet_finder.cpython-311.pyc
│ report_generator.cpython-311.pyc
│ string_analyzer.cpython-311.pyc
│ xref_finder.cpython-311.pyc
│
├───core
│ │ analyzer.py
│ │ callgraph_database.py
│ │ database.py
│ │ function_database.py
│ │ linked_graph_database.py
│ │ logger.py
│ │ memory_mapper.py
│ │ pe_loader.py
│ │ string_database.py
│ │ string_extractor.py
│ │
│ └───__pycache__
│ callgraph_database.cpython-311.pyc
│ function_database.cpython-311.pyc
│ linked_graph_database.cpython-311.pyc
│ memory_mapper.cpython-311.pyc
│ pe_loader.cpython-311.pyc
│ string_database.cpython-311.pyc
│ string_extractor.cpython-311.pyc
│
├───decompiler
│ cpp_generator.py
│ ir.py
│
├───disassembler
│ │ capstone_engine.py
│ │ function_finder.py
│ │
│ └───__pycache__
│ capstone_engine.cpython-311.pyc
│
├───plugins
│ └───silkroad
│ opcodes.py
│ packets.py
│ signatures.py
│
├───projects
│ └───sro_client
│ callgraph.json
│ full_report.json
│ functions.json
│ linked_callgraph.json
│ network_map.json
│ opcode_table.json
│ packet_map.json
│ strings.json
│
└───ui
hex_view.py
main_window.py
project_tree.py
C:\Users\romio10\Desktop\Reverse Studio>
This is the current directory structure of my **AI Reverse Studio** project.
The project is designed as a modular reverse engineering framework, with each directory responsible for a specific part of the analysis pipeline.
* **ai/** contains AI-powered modules for function classification, automatic renaming, and explanation of discovered code.
* **analysis/** contains the core analysis algorithms, including function discovery, call graph generation, packet analysis, opcode extraction, string analysis, cross-reference analysis, network analysis, and report generation.
* **core/** contains the framework infrastructure, such as the PE loader, memory mapper, databases for functions and strings, logging, and common analysis utilities.
* **decompiler/** is responsible for intermediate representation (IR) generation and C++ code generation.
* **disassembler/** wraps the Capstone disassembly engine and performs low-level instruction and function analysis.
* **plugins/silkroad/** contains Silkroad Online–specific knowledge, including opcode definitions, packet structures, and function signatures.
* **projects/** stores the output of each analysis session, such as extracted functions, call graphs, packet maps, opcode tables, network maps, and other generated reports in JSON format.
* **ui/** contains the graphical user interface, including the project explorer, hexadecimal viewer, and the main application window.
The goal of this architecture is to keep the project modular and extensible. Generic reverse engineering logic is separated from game-specific logic, making it easy to add support for other applications in the future by simply creating additional plugins.
Ultimately, the framework is intended to automate much of the reverse engineering workflow for Silkroad Online, including discovering functions, reconstructing call graphs, identifying packet handlers, extracting opcodes, analyzing network communication, and eventually generating a higher-level representation of the original program.
In addition, this architecture is designed to provide a solid foundation for recreating compatible server-side components for Joymax's Silkroad Online. By combining reverse engineering, static analysis, packet analysis, AI-assisted code understanding, and protocol reconstruction, the framework can help rebuild the game's server architecture and communication protocols based on the analyzed behavior of the official client. The long-term objective is to support the development of fully compatible server files that faithfully reproduce the original game's functionality while remaining modular, maintainable, and extensible.
Through this design, I have established a comprehensive roadmap for rebuilding server-side functionality from the original client itself. The objective is to derive the implementation directly from analysis of the official Joymax software and protocols, rather than relying on existing community server implementations or modified projects as a starting point. This architecture is intended to serve as the foundation for an original, independently developed, and fully compatible server implementation.