Conflicts

I forgot to mention, I tested this on 2020-09-02aRagexeRE and 2021-01-07-aRagexeRE, both giving me the same results, so yeah it might be broken for 2020+ clients.

Since this has been updated fairly recently, I decided to give it a try. However, I can't seem to get it to work. I'm sure I've applied everything correctly. The test script gives me this; For `itemlink2`, I've tried with other items, other random options, same result. For the regular `itemlink`, only the item ID and refine works, it doesn't display the card(s) you input.

Recently started adding garments and I can't overstate how awesome this patch would be. Great suggestion! I thought Gravity just messed up a patch (which happens a lot) and accidentally added the base sprite one folder above.

Before anything else, I hope rAthena staff would let me answer stuff like this as it directly involves something I own. Alright, you ordered a server ($9.95) and got everything as stated on our website, automated 10-minute setup after successful payment. This included latest rAthena, 2015-11-04 Client, INSTALLERS (Lite / Essential / Full) which are updated to around May 2017 kRO, FREE subdomain, FluxCP Setup, and even a free opensource forum software on top of that. The reason that we work hard to make sure our automated setups are as hassle-free as possible, is to cut down on "Support" questions such as these; For those who are interested, here's a redacted screenshot of his service's welcome e-mail. (Huge image, please view Full Size) Everyone has to start somewhere, we understand that. And that's one of the reasons why we offer a ready-to-play solution WITHOUT any customization, we see it as a fair ground between "making it easier for the customer which is presumably a new and inexperienced RO Server owner" and "spawning a breed of servers with the exact same settings / custom items / themes, that dies within a month or two". For things involving hardware / network issues, we reply pretty quickly. If there are further questions I'm pretty sure you can reach me via PM / my website. Thanks for hearing my side of the story.

I don't think an Abuse Notice from Hetzner is an "unreasonable reason" for me to suspend and subsequently terminate your server Stanley. AbuseMessage31009A14.txt Besides, everything seemed to be too conveniently timed for this to happen. Due to the following reasons; Your server was due in 4 days. (When the abuse happened) You were online during this whole thing, and amazingly, hopped on to LiveChat instantly after your server got suspended. You weren't as insistent about your denial on the issue (though of course you did deny it, just not at a level I expected). A network-level firewall blocks non-RO related ports, and surprisingly the perpetrator used a common RO port (Map Server Port in this case, 5121). We do not have an approved Paid Service on rAthena so I can't mention anything about our services other than for the intent of responding to your question, we support 2015-11-04 client right out of the box.

Seems like I've missed this one, I'll be following it from now though. Great work curiosity!

Hello. We haven't been quite active in documenting our changes and updates, but RagnaShield is in constant development. Here's a list of changes from 1.0.0 to 1.0.8; Version 1.0.1 Added shared encryption key. Added GRF file hashing. The RagnaShield logo on startup now closes once the client's main window shows up. Version 1.0.4 Fixed packet conflicts between RagnaShield and the packet obfuscation feature. This error would show up in your emulator's map-server console as "unsupported packet : 22 or 26 in length". Updated startup logo. Other minor bug fixes. Version 1.0.6 Improved RagnaShield's CPU usage down to almost 0%. The usage was already pretty low, except now it uses Windows' events to detect new process creation. This means it no longer needs to scan your process list at every specific interval of time. Fixed a bug regarding the third-party protection blocking false-positive process. Hidden processes are now detected. Version 1.0.7Fixed a bug regarding the GRF hashing process; this bug would crash your exe without any warning. The third-party protection module for Windows XP was unable to launch properly, this has been fixed. Improved overall customization : clientinfo.xml is no longer hidden within the game guard. To edit the content, you must open RagnaShield\RagnaShield.xml, then it's just like a regular clientinfo.xml. This was changed to allow admins to add more GM accounts without us having to rebuild your client files. You will notice that the IP fields are protected as well the port fields (so the security is still the same as before). The allowed IP tags are "#PRIMARY", "#FILTERED" and "#LOCALHOST". The last one allows you to test your server on a local network. DATA.INI is no longer embedded within the client. You can edit the content and add as many custom GRFs as you want. The first two entries are reserved for RagnaShield The data folder can be read safely without having an impact on our protected sprites (job sprites). This blocks no-delay skills while allowing you to test custom changes. Common errors are now displayed in a more friendly manner (replaced some of the 0xF#####87 errors). Introducing a new file signature protection. This fully blocks any unauthorized processes from being executed at the same time as your client. Version 1.0.8 Added file version to the game guard to track down further issues. Added a custom crash report to help track down further issues and which will quite possibly help you solve other issues. The file is stored in ClientCrash.log Huge update on RagnaShield's third-party protection. It is planned to be improved, but newer cheat softwares should have a harder time to work. WMI errors will now show up in hexadecimal, this will be easier to track them down as well. Pressing Ctrl-Del ingame will crash the client and generate a crash log on purpose. Security upgrade regarding macro'ing softwares. Updated third-party definitions and rules.

Ah wow. The scripts you create are amazing. May it be for the good and bad reasons. I'm afraid we'll start seeing alot of servers with 1k+ players. Or maybe even 10k

I just had to chime in after reading through all that. I'm quite positive it's related to the New Prontera. If so this link might help you; http://www.mediafire.com/download/7hcz6u9vl4vjhb4/newprontera.grf(Credits to Tokeiburu) The whole post is on Hercules, you can search for it there, "What do you think about the new Prontera?" topic. If that fails, I could provide you an automated client setup using 2013-08-07 for free, just send me a PM. So yeah, I totally don't think Client Setup is all that confusing. With all the tools that are currently available (NEMO), it's actually pretty easy. I understand that it can be frustrating at times, but to keep flaunting your "10 years of RO experience" doesn't help you one bit.

I actually had the same idea not long ago. However I decided to postpone it due to other work. This wouldn't belong to Web Releases forum as there isn't any actual release. Unfortunately I don't have enough permissions to move it. Anyway, this is pretty good. You've got a really promising Feature Plan there. Mind putting some screenshots of this CP? Perhaps that would motivate people to donate for your cause.

You're awesome! I could definitely use these.

I think that should be; bonus bAllStats,5;

You need to check your Item #4205 (Mimic Card), I think that's whats causing you these warnings.

All high and mighty, I see. Guess it was a futile effort trying to get my point across after all. Oh well.

I'm afraid you totally misunderstood my post. I said "server re-opening announcement", the server was ONLINE and running 1 week after AsuraHosting closed. But that's besides the point; we're going around in circles here. So how about a summary? 1) Our transaction is totally unrelated to my current hosting business, and my previous server. 2) I cannot give you access to my e-mail once again, nor would I forward all of my e-mails to your inbox. 3) You can use the Harmonize.it account (it's yours), I can PM you the details, however you'd have to be contented with me having to manually send you the Harmony Package files when I am available. Unless perhaps Sirius magically appears and changes the e-mail.

^ The post above is too long to quote. And, say what? As for the images you have posted, that has absolutely nothing to do with you, nor your purchase. That was when AsuraHosting suddenly closed their services. And no it was nothing but a coincidence that I decided to make my server re-opening announcement 20 days after your payment. Besides, the server was ONLINE during that period, albeit unstable, and without a website. So please get off your high horse.

Typical response, I must say. Let me try to break this down for everyone who would read this; I am removing images containing real names, personal e-mails and account credentials from the posts. As it is my right to privacy. Feel free to feast on this drama though.

Tip: You can configure an auto forward from a specific sender. Wow that's some real pro-tip right there. If I knew such a feature exists, there wouldn't have been an issue. Would you mind linking me to a guide on how to accomplish that? Cause all of my google searches doesn't seem to help. Link1 Link2 Link3 Further proof that I can not afford to lose the said e-mail, it's the very e-mail I use for my eAthena / rAthena / Hercules accounts. You can ask a Moderator / an Admin to confirm (and to be sure I haven't just changed it recently). I would also like to ask Orange00 to discuss this with me via PM, I'm pretty sure we could reach an amicable solution for this issue.

Hello Orange00, pretty detailed post I must say. However, I'm not sure why you didn't communicate with me first before all this drama. I have sold you a Harmony account with 2 IP slots, this account I was using since around 2010. Which, unsurprisingly, was tied to my main (non-RO related) e-mail. The deal went well, I gave you access to the account, and you were able to build your client (with Harmony) off of it. However, our complications start when you needed access to my personal e-mail. Having known how Sirius has abandoned Harmony, I didn't have much hope of getting the e-mail changed to your e-mail, so yes, I did give you access to my personal e-mail. I had trusted you to just read and download e-mails related to Harmony, but no, you did way more than that, I usually find read e-mails that I didn't remember opening. Everything fell off when you tried to change the email account's password. I have talked to you about it, and you said it'll be fine, and that you'll share the password with me anyway. So I let it pass. Then you were asking me about my security questions, after you have changed the mobile number to recover the account. Right then I knew I was going to lose my e-mail if I let that continue. While all of that was ongoing, I tried to e-mail Sirius a couple of times for an e-mail change, and of course, as expected there wasn't any response at all. I have kept all your server's IPs on the Harmony IP management page, and offered you that I'll just manually forward Harmony package e-mails from then on, I haven't heard from you since. PS: No, I don't remember blocking you on Facebook. And I even think you also have my old Skype ID. I'm really sad to be a part of such an issue though, but I hope I've explained my side.

We've made sure RagnaShield wont be too restrictive, in fact, you wont even need to re-build your client. Just change the setting ragnaban.enable: yes to ragnaban.enable: no on /conf/ragnashield.conf and it should be fine server-side. For the client-side, it's just a matter of replacing the custom cps.dll (and other components) we provided, and that's it.

For now yes. Even our cheapest $9.95 plan will have RagnaShield pre-installed.

RagnaShield Beta – Introduction What is it about? RagnaShield Beta is a free game guard presented to you by RagnaHosting Networks. Its goal is to offer a simple and reliable protection to prevent abuses and cheats client-side. It also offers a way to store hardware information, such as the MAC address, from the players without having to use a launcher. This hardware information can be easily used in your scripts to reward unique players or disallow dual-clienting on certain maps. There are a whole lot of other features that comes with it too, and it'll be in constant development, so we'll need your feedback / opinions / suggestions. Installation guide Client-side and Server-side The installation client-side should be straightforward. All you need is to do is copy the files from your RagnaShield package, which should include your client executable, cps.dll and msvcp100.dll. Your players may have to install the Microsoft Visual C++ 2010 SP1 Redistributable Package (x86) (https://www.microsoft.com/en-ca/download/details.aspx?id=8328). Server-side installation will be done for you by the RagnaHosting Team for free. We support the latest versions of the 2 major emulators, rAthena and Hercules. And we can install it for rAmod as well. If there are enough requests for eAthena / eAmod emulators, we will add support for those too. Features - Clientside Clientside Features Most of the features below can be further customized by requesting the Staff of RagnaHosting to rebuild your protection files. The ones which cannot be changed are the splash image and the IP/host of your clientinfo.xml, this would be the case at least until we are able to finish the RagnaShield Setup.exe tool which lets your customize your RagnaShield GameGuard by yourself. RagnaShield should work for all client versions, however, for best results, we recommend those that has support for Packet Obfuscation. Hardware IDsEvery time a player connects to his account, various hardware IDs are retrieved from the computer, such as the MAC Address, the CPU ID, Disk ID and Motherboard ID. This information is then sent to the server and stored in the `login` table. The purpose of this feature is to create a fingerprint of the player's computer capable of ensuring you they will not come back after a hardware ban. The player's hardware IDs are then compared to the ban list to see how much of a match they are. This setting can be modified from ragnashield.conf with ban_sensitivity. Advanced File Hashing (including those inside GRFs) You can hash as many files as you wish within your RO folder or your GRFs. RagnaHosting already provides a default list to prevent no-delay sprites by protecting the default job sprites, this GRF will take the highest priority and will be named JobSprites.grf. To customize this list and include your own files or sprites, contact the RagnaHosting Networks with the necessary information. If any of your hashed files fails the check, the client will show an error and it wont launch. This behavior cannot be changed. * This protection currently does not take into account the order in which your files are being loaded. If this becomes necessary, you might want to protect your DATA.INI as well. Dual Clienting By default, only up to two clients can run simultaneously. The choice of two clients is to allow your players to trade between their accounts. This feature can be modified as per user request. Hiding clientinfo.xml Your clientinfo.xml has been embedded to your RagnaShield protection components and the client will disallow any connection bypassing the one provided. This would protect you from most of those people trying to find your IP for some malicious intentions. This also ensures that you'll only be able to use this protection when you're hosted with us. Better compression (LZMA support) LZMA is a compression method allowing you to significantly reduce the size of your GRF files. The idea of this feature was introduced by Curiosity, for more information visit the following thread on rAthena : https://rathena.org/board/topic/95086-lessgrf-slim-down-your-grf. RagnaHosting uses this compression by default on your GRF files. As you may have noticed, the size of a fully patched Full Client is only about 1.4GB, the one RagnaHosting provides. In GRF Editor, you can use this custom compression by going in Tools > Settings > General > Compression method > Custom compression... and select the cps.dll provided in the thread mentioned above. * Do not attempt to load the custom cps.dll provided by RagnaShield in GRF Editor, you will crash and may end up having to reinstall the application. File Encryption (Unique GRF Editor keys) RagnaShield allows you to encrypt your GRF files' content using GRF Editor's encryption. You will receive a key.grfkey file which can be used directly by GRF Editor to encrypt or decrypt your content. File Encryption (RagnaHosting Shared Encryption) By being part of RagnaHosting, you will gain access to free or cheaper custom content for your server. This content is encrypted and will only work on ALL servers using RagnaShield as their protection. If you decide to leave the host however, you will no longer be able to use them. This feature itself warrants a post of its own, I'll be explaining in details how this works. Splash Screen Pretty self explanatory, RagnaShield will display a splash screen 250px by 150px in size when your client launches, and closes it as soon as the client fully loads up (the login screen appears). Third-party program restriction / blocking This feature is in constant development and there are already a handful of softwares being blocked by the game guard. You can choose whether or not you want to allow tools such as RCX to run on your server. Other programs such as CheatEngine will automatically be blocked. This feature is fully customizable as well to fit every server's needs. We do encourage you to submit cheat tools so we could block them for everyone. We believe there's no reliable way to block macros, and we want to make it clear that we're not advertising RagnaShield to be able to do that. What about bots? Blocking bots or other similar tools is not part of RagnaShield's protection. To prevent those, we recommend you use newer clients allowing packet obfuscation; it will block bots better than any features we could add to our game guard. By default, we'll include packet obfuscation support on the client we'll provide you, it'll use fully qualified keys, and it'll be unique for each server. Features - Serverside Serverside Features These complements the Clientside features, and makes use of the extra data the client sends. There are some other useful commands too like @execute and @ping. As usual, this part of RagnaShield will constantly be updated during this Beta stage. We will release our repo containing all the changes soon enough. Your suggestions / reports would help us a lot. Banning system It is important to understand the difference between an account ban, an IP ban and a hardware ban. Knowing when to use which can be a bit confusing at first, however RagnaShield's ban commands are more straightforward because they combine these together nicely. Banning a player bans both their hardware IDs and their account at the same time. Our custom bans take into account the level (group id) of the GM who is issuing the ban. As such, it is only possible for a GM to ban an account with a lower group id than his own. Therefore admins (group 99) can never be banned. The hardware ban, which is always applied regardless of the group id of the target, can be bypassed if the account's owner has a higher group id. Configuration file (ragnashield.conf) The configuration file is found at conf/ragnashield.conf. Hardware IDs Hardware IDs are stored on the server side when a player attempts to log in. All the info are also added to the loginlog table. RagnaHosting lists 4 kinds of Hardware IDs, namely; MAC Address, CPU ID, Drive ID and Motherboard ID. There's a 5th and special kind of ID which combines the latter 3 into a unique hashed ID, which can make it easier for you to integrate on your scripts. All of these information are added to the `login` and `loginlog` tables. Ingame @commands @ragnaban / @ban2 usage: @ragnaban <time> <player_name> {<reason>} ex : @ragnaban 1d "test player" Stole gears. Similar to @ban, this command does both a regular @ban and a hardware ban. The computer of the player will no longer be able to connect to your server. If the account ban's time is greater than the one given by the command, it will keep the longest one. When a player's name contains spaces, you must use quotes, otherwise it's not needed. The reason given for the ban is also optional but it is recommended. @ragnafullban / @fullban usage: @ragnafullban <time> <player_name> {<reason>} ex : @ragnafullban 1d "test player" Stole gears. This is the same as the previous command, except it will also ban all the accounts related to the player. It bans the accounts based on the last person who logged into them. @ragnaunban / @unban2 usage: @ragnaunban <player_name> ex : @ragnaunban "test player" This command removes the hardware ban of a player as well as removing the account ban of the player mentioned. @ragnafullunban / @fullunban usage: @ragnafullunban <player_name> ex : @ragnafullunban "test player" Same as the previous ban, except it unbans all the accounts connected with the player (using the hardware IDs of the person who logged into the account last). @showmacban usage: @showmacban Shows the current MAC addresses banned. @execute <system_command> usage: @execute echo Hello world! Executes a command on the server's VPS. This command allows you to customize server tasks outside of the game. The example command will display "Hello world!" in the map-server console. You could use it to recompile or restart your server, create a backup, etc. The possibilities are limitless for this command. We'll be writing scripts for everyone for you to make use of Linux commands and utilities from inside the game! This means you can tell your GM to type @execute sqldump before he hosts his event, just in case something goes wrong. Feel free to send us suggestions of what commands you want to see on here. @ping {<player_name>} usage: @ping This command asks the server to ping yourself or another player. The task is put on a background thread and you will have to wait a few seconds to retrieve the ping statistics. To retrieve the pong info, you'll have to type @ping again. Each ping has a hard delay of 10 seconds and the statistics will be erased from your server's VPS after 30 seconds. By default, players cannot use @ping <player_name>. If you want to allow lower GMs to use the latter command, you must give them the @ping2 atcommand permission ("ping2: true" in groups.conf). Script methods The following script methods are shortcuts to simplify your custom scripts. getcharmac({<account ID>/<character ID>/<character name>}) usage: getcharmac(); usage: getcharmac("test_player"); If no argument is specified, the currently attached player's RID will be used to retrieve the MAC address. gethardwareid(<type> {,<account ID>/<character ID>/<character name>}) usage: .@id$ = gethardwareid(0); usage: .@id$ = gethardwareid(4, "test_player"); Type 0 – MAC address Type 1 – CPU ID Type 2 – Disk drive ID Type 3 – Motherboard ID Type 4 – Unique ID (combines types 1-2-3) This command retrieves the hardware information from a player. Credits Conflicts - Project manager, started this whole project and gathered the team. Helped test the features thoroughly. Kept pushing for more features, and will keep doing that for the foreseeable future. Nanakiwurtz - Ported the source code for both rAthena and rAmod, scripted the sample scripts as well as general testing of the features. She will be taking care of your protection component customization requests. Tokeiburu -Responsible for the tools used for the generation of the game guard files. He's being humble though, to put it simply, RagnaShield wouldn't have been possible without him. Updates: Version 1.0.1 Added shared encryption key. Added GRF file hashing. The RagnaShield logo on startup now closes once the client's main window shows up. Version 1.0.4 Fixed packet conflicts between RagnaShield and the packet obfuscation feature. This error would show up in your emulator's map-server console as "unsupported packet : 22 or 26 in length". Updated startup logo. Other minor bug fixes. Version 1.0.6 Improved RagnaShield's CPU usage down to almost 0%. The usage was already pretty low, except now it uses Windows' events to detect new process creation. This means it no longer needs to scan your process list at every specific interval of time. Fixed a bug regarding the third-party protection blocking false-positive process. Hidden processes are now detected. Version 1.0.7 Fixed a bug regarding the GRF hashing process; this bug would crash your exe without any warning. The third-party protection module for Windows XP was unable to launch properly, this has been fixed. Improved overall customization : clientinfo.xml is no longer hidden within the game guard. To edit the content, you must open RagnaShield\RagnaShield.xml, then it's just like a regular clientinfo.xml. This was changed to allow admins to add more GM accounts without us having to rebuild your client files. You will notice that the IP fields are protected as well the port fields (so the security is still the same as before). The allowed IP tags are "#PRIMARY", "#FILTERED" and "#LOCALHOST". The last one allows you to test your server on a local network. DATA.INI is no longer embedded within the client. You can edit the content and add as many custom GRFs as you want. The first two entries are reserved for RagnaShield The data folder can be read safely without having an impact on our protected sprites (job sprites). This blocks no-delay skills while allowing you to test custom changes. Common errors are now displayed in a more friendly manner (replaced some of the 0xF#####87 errors). Introducing a new file signature protection. This fully blocks any unauthorized processes from being executed at the same time as your client. Version 1.0.8 Added file version to the game guard to track down further issues. Added a custom crash report to help track down further issues and which will quite possibly help you solve other issues. The file is stored in ClientCrash.log Huge update on RagnaShield's third-party protection. It is planned to be improved, but newer cheat softwares should have a harder time to work. WMI errors will now show up in hexadecimal, this will be easier to track them down as well. Pressing Ctrl-Del ingame will crash the client and generate a crash log on purpose. Security upgrade regarding macro'ing softwares. Updated third-party definitions and rules.

It's most likely related to this; Packet Obfuscation Support