Akkarin

Script_commands.txt suggests setting the variable to 0 in order to clear it. It basically removes the variable.

No worries. Update: Updated package to include newly updated GRFs (patched to 2017-01-22) and includes latest RSUs

https://github.com/rathena/rathena/wiki/Custom_Items

GoDaddy doesn't open ports on their shared hosting platform.

The process for withdrawals hasn't changed at all. It's still inactive and won't be available until there's an announcement, which is coming soon.

Well.. as eAthena is no longer being worked on i think its safe to suggest that you should use rA instead. Check in all of those GRFs to see which also has a clientinfo.xml file. GRFs are loaded with the highest number first, then all the others will overwrite data when they're loaded.

If you want to do the second option, yes.

o.O?? One or the other. There's no point in doing both.

No, i gave you two different options. The first is to use LUA to include an additional file with all your custom items in. The second is to tell the client that the iteminfo file is located somewhere else. This option will mean you need to have your customs and official items all in the same folder, but it won't get overwritten when you update your kRO.

Use LUA to include your customs when starting the client, or you can use NEMO to tell your client where your custom iteminfo file is when diffing your client

In your RO folder, look for a folder called data. Also look at your DATA.INI file to see if you have any other GRFs loading other clientinfo files. eAthena works in the same fashion as rAthena, except eA is no longer updated nor supported by anyone.

1. We don't support eAthena. 2. Check your data folder for an overriding clientinfo.xml

There's a few different solutions. You could run a lightweight webserver on your vps that has php to check ports and report back to your site via Cron, or you could move to a provider that doesn't block ports on their webserver, or you could host your site on your vps. Other than that you'll struggle.

1. Use built-in Pages module to create a page with all the details you want, then change the link in /themes/<theme name>/header.php or designers generally add a list of links in main/nav.php or something. 2. "does not work" doesn't help anyone diagnose your problem. Do you get an error message? 3. Add the freebies module. 4. Link to server info page or wherever you like <a href="<?php echo $this->url('server', 'info')?>" >img here</a>

You were part of the legacy Limited Members group. Limited Members needed to make one post in order to complete verification as of a short while ago. Congratulations - your 7 month old account has finally been setup. Thank you so much for your valued contributions to our project.

http://www.learn-c.org/

You need to compile rAthena in Pre-Renewal mode, ensure your /db/packet_db.txt is set to the correct version and set the same client date in /src/common/mmo.h. The missing images files are for the pincode system which is not supported on your desired client version: //=================================== // Pincode system //=================================== // NOTE: Requires client 2011-03-09aragexeRE or newer. Disable it in /conf/char_athena.conf. The rest should work if your packet versions are correct.

You can't. Newer client features don't have backwards compatible diffs that far back. If you want to use them, use a newer client.

The log database is not the main database, though most users foolishly have all the tables in one database. You can find everything you need in the doc folder in terms of scripting.

Issues like this don't just randomly popup, they are caused by a configuration issue. This one in particular is about the username and password not matching the credentials in the database. Are you using a custom theme?

Your syntax is wrong so that line is being left out. The top of that file tells you the structure. All custom stuff in the db folder is supposed to go into the import files to prevent merge conflicts.

Is there a real reason you necro'd a post that's more than 3 years old? The error tells you that your SQL credentials are wrong.

The error tells you it's a Login error. If you're using an old theme that doesn't have email confirmation that could be a cause. You could also check your error logs.. The error message comes from: if (!$loginAthenaGroup->isAuth($username, $password)) { throw new Flux_LoginError('Invalid login', Flux_LoginError::INVALID_LOGIN); } Essentially this means your username and/or password is wrong. Check for MD5 usage in FluxCP configs and within your database. This is the more likely cause.

For logging specific strings you'd need to alter the src to check each string and compare it against an array of words.. which is very resource intensive. You could achieve the same thing in NPC scripting which is easier to code and manage, but would use more resources than the src version. // Log CHAT (Global, Whisper, Party, Guild, Main chat, Clan) (Note 3) // LOGGING FILTERS // ============================================================= // 0 = Don't log at all // 1 - Log Global messages // 2 - Log Whisper messages // 4 - Log Party messages // 8 - Log Guild messages // 16 - Log Main chat messages // 32 - Log Clan messages // Example: // log_chat: 5 = logs both Whisper & Party messages // log_chat: 8 = logs only Guild messages // log_chat: 63 = logs everything log_chat: 0 SQL logging is enabled by default. log_chat should be 63 to log all chats.

The instance being created either doesn't have a db entry, or the instance being called doesn't match the name in the db.