Akkarin

If the line is in db2 then your custom item takes priority regardless of what the item has as stats in the normal db. We already have the functionality you're looking for, were not going to change the process in order to arrive at the same outcome. Custom stuff has always gone into db2, this process has worked fine for thousands of servers since the code was created over a decade ago.

o.O? FluxCP uses a socket approach to pinging ports. This means you only need to be able to send outbound traffic to those ports - FluxCP doesn't require a pong event, so the incoming ports are irrelevant.

The SQL files should be ran in order to update your database. If you have any customs or amendments to official items, they should be in *_db2. That is the purpose of those tables. Anything in there is read after the base table, so if you have a Red Potion in item_db with normal item script, you can have a Red Potion (501) in item_db2 and whatever stats this item has will supercede the item stats from item_db. We set this up to prevent anything from being overwritten.

If-statements with more than one line of code to perform should be in curly braces: OnInit: if (gettime(3) >=0 && gettime(3) <=3) { $@isnight = 1; night; } if (gettime(3) >=4 && gettime(3) <=7) { $@isnight = 0; day; if (gettime(3) >=8 && gettime(3) <=11) { $@isnight = 1; night; } if (gettime(3) >=12 && gettime(3) <=15) { $@isnight = 0; day; } if (gettime(3) >=16 && gettime(3) <=19) { $@isnight = 1; night; } if (gettime(3) >=20 && gettime(3) <=23) { $@isnight = 0; day; } end; Don't forget that gettime() now uses constants:

Your script has a few curly braces in the wrong place. Try this: hoh_v5,120,143,6 script Room 1 858,{ mes "[Woman]"; mes "Please enter your password"; next; input .@var$; if (.@var$ == "password") { mes "[Woman]"; mes "Well done, you typed it correctly."; next; switch(select("Enter your room:Cancel")) { case 1: warp "hoh_v5",27,236; break; case 2: break; } } else { mes "[Woman]"; mes "Sorry, you got it wrong."; close; } end; } Please use the Codebox in future

The item and mob sql files can be imported into your database at any time and will keep your tables up to date. The SQL Synchronisation commits keep the SQL files up to date with the txt databases.

No idea. OboroCP was supposed to be a paid/licensed control panel. You should obtain support from the developers of that CP. For all intents and purposes, FluxCP works well enough.

\data\texture\À¯ÀúÀÎÅÍÆäÀ̽º

Client modifications are achieved with a program called NEMO https://rathena.org/board/topic/90204-nemo/ The background is in your data folder. You can rename the client the same way you rename any other files.

It's so you can use your own image/logo. Don't be lazy.

All of the text at the top of the image can be changed - they're all in separate layers.

We don't provide support for eA/rAMod users. Ask the person you "purchased" it from.

Disabling Quake effect is a client diff, it has nothing to do with encryption or your GRFs.

You're supposed to update the topic with your solution in order to help someone else that may come across the same issue as you.

Click RSS Feeds under Content Discovery in ACP Click Create New button, then select "Topics" and give it a name. You'll then find the link under the orange RSS button at the bottom of all your forum pages Use that link as the RSS Feed URL.

What version of Invision are you using?

You update the rss feed url, probably found in a settings file in the theme directory somewhere.

The latest upgrade of IPS has been installed and with it comes the ability to add Two-Factor Authentication to your account. To enable, you must first have Google Authenticator on your smart phone [Android][iOS]. You can then setup 2FA by navigating to your Account Settings Once the Account Settings page has loaded, select "Account Security" and enter your forum password. You will then follow on-screen instructions to setup 2FA. If you have 2FA enabled on your forum account, you will need to authenticate when attempting to perform any of the following activities: Changing email address (also need to re-enter password) Changing password (also need to re-enter current password) Updating two-factor authentication setup (also need to re-enter password) Logging into the front-end (This does not apply if the user is logged in automatically because they have used the Remember Me checkbox) Managing PayPal billing agreements Editing personal billing information Managing addresses Managing alternative contacts Managing stored cards Viewing, withdrawing or topping up account credit After 3 failed attempts, the account will be locked for 60 minutes. A number of staff are already using Google Authenticator for their Github account, and now for their rAthena Forum account to keep them secure. If you begin to use this and encounter problems, please let me know as soon as possible.

Build incorporates the changes not yet compiled, rebuild does a complete recompile of the code.

You don't loose /conf/ edits by recompiling under pre-re mode. You -should- be using the import folders, though. Cleaning before building just removes old makefiles and pointer scripts created by the build process. ./configure && make clean && make server

Your server consoles generally tell you why. Look at the error.

Short answer: there is. Long answer: Yes, but you need to alter the theme to conform to the new theme loading structure. You can look at the default "bootstrap" theme to see how this is achieved. In most cases, all you need is a manifest.php file and then the js, css, img, main/, header and footer.php files.

Hey guys! I've been receiving many PMs over the last two months from disgruntled members claiming that staff are being unfair or giving out Warning Points on a whim, so I thought it might be time to explain how this system works. The Warnings available to staff are all preset in order to have a standardised rule set. All staff are unable to make up their own warnings to prevent bias. These warning reasons are taken directly from the Rules page, which all members agree to adhere to. Each warning has a +# value in front of it denoting how many warning points it gives. When your account has reached a certain number of points in any 28 day period, your account will suffer under some restrictions. These restrictions are also preset. For example, for breaking the rules for topic bumping 5 times within any 28 day period will restrict you from posting on our forums for 7 days. The rules predate my existence on this project and i'm sure many members who have been a part of this project can agree that over the last few years we have become ignorant of punishing rule-breakers. I believed our laid-back lax approach needed a gentle push, so this system was overhauled on 7th December 2016 and is so far doing it's job very well. December Warnings: 40 January Warnings: 69 The staff are not out to get you and only issue warnings if the warning conditions are met. Members who don't follow the forum rules get warned, it's as simple as that. If for some reason you believe you shouldn't have been given warning points in a particular instance, please feel free to contact me.

Correct, though the dev team are very close to pushing it into a public PR for testing from what i understand.

The error tells you exactly what you need to do. Change your packet_db_ver to 55. If you scroll down in db/packet_db.txt you'll see packet_ver: 55 and client 2015-11-04 there.