Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/01/2021 in all areas

  1. https://onedrive.live.com/?authkey=!APitgjgAKsU5Vns&cid=8D5D925728D418FA&id=8D5D925728D418FA!433&parId=8D5D925728D418FA!432&o=OneUp
    1 point
  2. function script my_global_func { mes "this message from 'my_global_func' function from out the npc"; return; } prontera,0,0,0 script func_test 444,{ function my_func; my_func(); next; my_global_func(); next; callfunc("my_other_global_func"); end; function my_func { mes "this message from 'my_func' function from inside the npc"; return; } } function script my_other_global_func { mes "this message from 'my_other_global_func' function from out the npc"; return; }
    1 point
  3. Happy Thanksgiving everyone. Since I couldn't get the turkey, I thought I would bring this instead. Without further ado, Let me introduce... WARP (Windows Application Revamp Package) Why this name? Because I like using acronyms and this name sounded apt. Plus it's the function & features that matter more. And no, I am not gonna change the name. Why not just fix up NEMO? The codebase for NEMO is pretty much ancient at this point. So rather than fixing it up, I decided to go the route of creating it fresh from scratch. The end result is a far superior product. OK, but what if you end up AFRO (Away From RO)again? Well, I can't promise that I will be around forever. However, this time around, I am releasing the source code for the tool as well. So, exactly what has changed? Well, quite a few things. Let's start off with how the GUI looks now. As you can see, the GUI is much more modern and aesthetically pleasing thanks to @Haziel & @Hadrias . The package comes with 3 tools - Console version (for simple patching), Main GUI, and Tester GUI (for batch testing). A big salute to @4144 for keeping NEMO alive while I was AFRO . Ok, jokes aside, I discussed with him about the changes he made and I have incorporated almost all of them but with some differences. Language & Styles are now on the bottom as you can see. All the remaining menus have now been shifted to drawers (moving side panels). To reveal them you can either swipe from the respective edge or click the button at the top. The right side drawer houses all the Extensions (Used to be called 'Addons' in NEMO). They are now loaded independently of the client. This avoids unnecessary redefinitions and now you can also use Extensions for activities that don't need a loaded client. All the common functions have been added to the 'Quick Actions' group and all the remaining ones are in the left drawer, which is not many. If you have suggestions for more features let me know. Moving on to the Back end (This is of no use to the regular user. So you can skip this part if you want) It was high time for us to have a proper input file format. Enter YAML. Love it or hate it but it's here to stay. Frankly, I like it more than libconfig and INI. You would be seeing YAML being used for almost every file in WARP. This includes input files for Patches & Extensions, Files defining those two, Session files, etc. Writing patches is far more flexible now. Say goodbye to PTYPE_HEX and \xAB. Now we can do wild card searches with the actual wild cards inside hex codes. Of course, we still need to have some well-defined characters for that. Currently, we have 2 forms of wildcards - Nibble wise - For e.g. => A? , ?? , ?3 Bit wise - For e.g. => [1.0...01] If you have any suggestions about it let me know. Speaking of writing hex code, I have provided functions looking almost identical to Assembly instructions for generating their equivalent hex code. This helps in making the hex code more human-readable and adds a little more flexibility. User inputs have a few more types and little more flexibility in specifying constraints now. Scripts have proper segregation now. Please follow them when adding your own. Only the scripts inside the 'Init' folder gets reloaded each time the client is loaded. This avoids unnecessary reloads. exe has now become 'Exe'. But in addition to this, you get 2 more objects - System (for filesystem activities) & Warp (whatever is outside the scope of the other two) Many of the functions used for retrieving some constant information in the 'Exe' have become properties now. For e.g. PEoffset, ImageBase, BuildDate, etc. During patching, the Diff section is only added if you have inserted any code using one of the 'Add' functions. Also, the Diff section now grows dynamically as per requirement (in increments of Section Alignment of course). In addition to the Patched Exe, The tool also generates an (Extra Patch Info) file with the suffix '.epi'. It holds just enough info for the tool to recognize existing patches in an exe from a previous patch session. So how is it useful? Let's say you have a patched client and its EPI file. But you don't have the original anymore. Now you can remove 1 or 2 patches and keep the rest OR even restore the original from the patched exe. Last, but not least, I am providing documentation about everything including the API. But bear with me for a bit, as I am still working on the documentation part. I probably forgot more points to add here, but I think this pretty much covers the important stuff. Anyways you can read in detail at the Wiki Is it ready to be used now? The tool is definitely ready. I have added most of the patches but not all just yet. But I was not able to test all the patches in-game. So please don't attack me if something failed. I would appreciate a Bug Request in Github instead. You can also come to Discord as well, if you prefer that. Also note, that some patches are still failing for new clients, and some failing for old ones. However, I saw the same behavior in NEMO, so that would be part of the next stage of operations - Updating Patch scripts. So, where do I get it from? https://github.com/Neo-Mind/WARP How to use it? There is a User Guide in the git repo (best viewed from Github itself). Everyone is used to NEMO by now, so it shouldn't be difficult to use this even without the guide. Plus the Github wiki is pretty detailed. Any last words before we close this? Just like in the case of NEMO, my intention with WARP is to create a common tool for patching without being restricted to RO or which OS you use it in. For this reason, you will be seeing multiple branches in the Git repo. If you are planning to use WARP for patching some other application, Create a branch using the 'win32' branch as a starting point That's about it from me for now.
    1 point
  4. First of all, I apologize for the horrible English. The panel's official language is in PT-BR, if someone wants to translate they can send me PM or wait until I do a translation. ======= Hello guys, I present to you a panel that I developed in open source totally free for the community, developed in Laravel 8. Project Link: https://github.com/rscodexx/ragpainel Demo: https://rscode.com.br/ragpainel/ Functions [] General [] View users online. [] View accounts total. [] View chars total. [] View guilds total [] Top 3 players (PVP, WOE and MVP). [] User [] Register Account [] Login Account [] Change account (photo, password, email and birthdate). [] View last ip [] View days vip [] View cashpoints [] Forgot password [] Forgot login [] Admin [] View Logs [] Manager Credits [] Manager Vip [] Manager Staff [] Manager Bans [] Manager Tickets [] Configs Panel [] Rankings [] WOE [] MVPs [] Zenys [] PVP [] Events [] Database [] View Itens [] View Monsters [] Support [] NewTicket [] ViewTickets [] Donate [] To do Donate [] Consult Donates Layout Mobile Desktop Technologies The following tools were used in the construction of the project: Minimum Requirements PHP in version 7.3 or higher BCMath PHP Active Extension CtypePHP Active Extension Fileinfo PHP Active Extension JSONPHP Active Extension Mbstring PHP Active Extension OpenSSL PHP Active Extension PDO PHP Active Extension TokenizerPHP Active Extension XMLPHP Active Extension Install on Windows. Prerequisites: Before you begin, you will need to have the following tools installed on your machine: GIT, Apache, Mysql (Or any other type of database), Composer If you do not know how to install and configure a server environment, you can use tools that are all ready as: Xampp Wamp In addition, it is good to have an editor to work with the code as VSCode Running the Backend (server) # Clone project $ git clone https://github.com/rscodexx/ragpainel.git # Or download the project directly from the repository: https://github.com/rscodexx/ragpainel # Rename the file .env-example(is in the root folder of the project) to .env and config: DB_CONNECTION=mysql # DB Type DB_HOST=127.0.0.1 # DB Ip DB_PORT=3306 # DB Port DB_DATABASE=ragpainel DB Name DB_USERNAME=ragnarok DB User Name DB_PASSWORD=ragnarok DB User Password TIMEZONE=America/Sao_Paulo # Time Zone LOCALE=pt-BR # Language(only the one supported for now). FALLBACK_LOCALE=pt-BR # Language for erros(only the one supported for now) # Access the project folder on your terminal $ cd ragpainel # After entering the project directory, install the composer and its dependencies. $ composer install # Wait for the installation # Install the panel tables, still with terminal open in the project directory use: $ php artisan migrate # There, your server is installed and configured. Running the web application (Frontend) # Start your server, to access the panel you need to access the public folder, an example below: $ http://localhost/ragpainel/public # You can also run the application without the need for an apache server configured through php artisan. # Access the project folder in your terminal $ cd ragpainel # Type the command: $ php artisan serve # Just click on the generated link to start the panel. # Use the command CTRL + C to shut down the server. How to contribute to the project? Post all the bugs and errors found here: https://github.com/rscodexx/ragpainel/issues If you want, you can make a DONATION
    1 point
  5. Olá pessoal, apresento para vocês um painel que eu desenvolvi em código aberto totalmente gratuito para a comunidade, desenvolvido em Laravel 8. Link do projeto: https://github.com/rscodexx/ragpainel Demonstração: https://rscode.com.br/ragpainel/ Funcionalidades [] Geral [] Visualizar jogadores online. [] Visualizar total de contas. [] Visualizar total de personagens. [] Visualizar total de clãns. [] Top 3 jogadores de (PVP, WOE e MVP). [] Usuário [] Criar conta [] Registrar conta [] Alterar dados da conta(foto, senha, e-mail e deta de nascimento). [] Visualizar quantidade de acessos. [] Visualizar data e hora do último acesso. [] Visualizar último ip acessado. [] Visualizar quantidade de dias vip. [] Visualizar quantidade de créditos. [] Esqueceu sua senha [] Esqueceu seu login [] Administrador [] Visualizar Logs [] Gerenciar Créditos [] Gerenciar Vip [] Gerenciar Equipe [] Gerenciar Banimentos [] Gerenciar Tickets [] Configurações do Painel [] Rankings [] WOE [] MVPs [] Zenys [] PVP [] Eventos [] Database [] Visualizar Itens [] Visualizar Monstros [] Suporte [] Criar Ticket [] Visualizar Tickets [] Doações [] Fazer Doação [] Consultar Doações Layout Celular Desktop Tecnologias As seguintes ferramentas foram usadas na construção do projeto: Requisitos Mínimos PHP na versão 7.3 ou superior BCMath PHP Extensão ativa Ctype PHP Extensão ativa Fileinfo PHP Extensão ativa JSON PHP Extensão ativa Mbstring PHP Extensão ativa OpenSSL PHP Extensão ativa PDO PHP Extensão ativa Tokenizer PHP Extensão ativa XML PHP Extensão ativa Instalação no Windows. Pré-requisitos Antes de começar, você vai precisar ter instalado em sua máquina as seguintes ferramentas: GIT, Apache, Mysql (Ou qualquer outro tipo de banco de dados), Composer Se você não sabe instalar e configurar um ambiente de servidor, pode utilizar ferramentas que já vem tudo pronto como: Xampp Wamp Além disto é bom ter um editor para trabalhar com o código como VSCode Rodando o Backend (servidor) servidor) # Clone este projeto $ git clone https://github.com/rscodexx/ragpainel.git # Ou baixe o projeto direto do repositório: https://github.com/rscodexx/ragpainel # Renomeie o arquivo .env-example(está na pasta raiz do projeto) para .env e configure. DB_CONNECTION=mysql #Tipo de banco de dados. DB_HOST=127.0.0.1 #IP do banco de dados. DB_PORT=3306 #Porta do banco de dados. DB_DATABASE=ragpainel #Tabela do banco de dados. DB_USERNAME=ragnarok #Usuário do banco de dados DB_PASSWORD=ragnarok #Senha do banco de dados. TIMEZONE=America/Sao_Paulo #Horário LOCALE=pt-BR #Idioma geral. FALLBACK_LOCALE=pt-BR #Idioma das mensagens de erro. # Acesse a pasta do projeto em seu terminal/cmd $ cd ragpainel # Após entrar no diretório do projeto instale o composer e suas dependências. $ composer install # Aguarde a instalação. # Instale as tabelas do painel, ainda com cmd aberto no diretório do projeto utilize: $ php artisan migrate # Pronto, o seu servidor está instalado e configurado. Rodando a aplicação web (Frontend) # Inicie o seu servidor, para acessar o painel é necessário acessar a pasta public, um exemplo abaixo: $ http://localhost/ragpainel/public # Você também pode rodar a aplicação sem precisar de um servidor apache configurado através do php artisan. # Acesse a pasta do projeto em seu terminal/cmd $ cd ragpainel # Digite o comando: $ php artisan serve # Basta clicar no link gerado para iniciar o painel. # Use o comando CTRL + C para desligar o servidor. Como contribuir para o projeto? Poste todos os bugs e erros encontrados aqui: https://github.com/rscodexx/ragpainel/issues Caso queira, pode fazer uma DOAÇÃO.
    1 point
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use and Privacy Policy.