RuneScape Control Panel (MySQL Servers)

[CodeMonkeyD]

Control Panel Features

• User Login / Change Password (MD5 Encryption)
• Item Database
• Player Equipment Calculator

Introduction
Well i have a little free time on my hands i figured this idea would be helpful for servers with custom items or just help out players in general i will be adding more information about this control panel as it progresses.

Item Database Information
this will load from and item table such as

• img
• desc
• bonuses such as Atk, Def, Other
• Soon to be added Drops by and %

Screenshot


Player Equipment Calculator
Ok the idea here is to gather the information from item table and from the users character equipment data from the current login account used, with an img of a blank equipment inventory it will read what the character has and change each slot to what the correct item is equipped and will add up all the atk, def, and other bonuses are from the item table and process out a total in column such as the item database this is good for any items you may haves changed the stats on.

Another Idea
Well for the Player Equipment i was thinking of allow the player to pick from the database for items to equipped allowing them to calculate the best set of items for there needs.

ScreenShot
*Will be adding once i get working on it.

Thank you for taking the time to read all the features ect please reply with any feed back or features i should add this is going to be released to everyone so lets make it good for all your needs.

Contact Information
- Live Messanger or Email Codemonkeyd@live.com
- you can also pm me on ragezone that works too

[MentaL]

[theabsence]

I wrote something like this back in the day, although it was written in java and implemented mysql server side. I bid you good luck sir, looks like you're doing an excellent job so far.

[ELSD]

:o I luv it very sexi...

[Masius]

Problem is, rsps's so called "coders" are dumbasses. They rather save their information in text files and not actually using MySQL queries. Not only it's better perfomance-wise, but it opens up a new range of possibilities through website/app's means. Gg, tho.

[GhostSnyper]

If you wish to go there, let me put a few things on the table.

1. MySQL doesn't make things faster. Don't even try to justify a HUNDRETH of a second

2. MySQL doesn't scale well with large writes. If you are not batch updating, then there's really no point in replying to me.

3. MySQL is general software. I can put money on the table that I can write something that will make MySQL look like Windows 95

4. PostgreSQL is faster, more robust, and actually CONFORMS TO SQL STANDARDS

[CodeMonkeyD]

Problem is, rsps's so called "coders" are dumbasses. They rather save their information in text files and not actually using MySQL queries. Not only it's better perfomance-wise, but it opens up a new range of possibilities through website/app's means. Gg, tho.

im not sure if you read this right but it loads from a mysql database this control panel is not .txt file format what so ever.

[Mextur]

If you wish to go there, let me put a few things on the table.

1. MySQL doesn't make things faster. Don't even try to justify a HUNDRETH of a second

2. MySQL doesn't scale well with large writes. If you are not batch updating, then there's really no point in replying to me.

3. MySQL is general software. I can put money on the table that I can write something that will make MySQL look like Windows 95

4. PostgreSQL is faster, more robust, and actually CONFORMS TO SQL STANDARDS

MySQL is very slow. Just because you need to initialize an connection between server and the MySQL server.

[GhostSnyper]

MySQL is very slow. Just because you need to initialize an connection between server and the MySQL server.

This is only applicable with bad programming practices. Let me run a few scenarios for you:

1. You have a logging system that starts a database transaction. Since the server runs a per demand database, a new con is made per query. Lots of Overhead.

However, the same thing with text files is just as bad if not worse; The server may waste time connecting and authenticating, but as soon as the data is sent, it's the SQL servers' problem.

With a flat-file system, you waste exponentially more time opening the file, initiating scanners or buffered readers and writers, formatting the data and writing the data. The game server is much more responsible

2. You cache large amounts of data to be offloaded to the Storage system. It works two ways:

Database: You are already using a connection pool or a constant connection to the database. Once the data is ready, you need to make a million queries, or a VERY large prepared statement. Once you send the data, the game server is clear to continue on it's way.

Flat-file: Your server is most likely stable enough to be safe to hold a lot of data. When buffers are full, open the log file using a NIO pipeline. take the memory address already allocated as a byte stream (The data is pre-formatted as the server makes the logs), and the server takes advantage of modern processing power to asynchronously append the data to the log very quickly.

Both these tasks will actually take about the same amount of time, and have little benefit over each other than the fact that it's easier to manipulate data from a SQL storage system from multiple sites rather than a flat-file system. UNLESS YOU ARE SMART


Having multiple ways to access your players' game files is a huge security flaw. We all know how easy it is to rip off someone's database, especially with the flaws in web servers. Using flat-file (or database) systems that require the Game server to issue the data is best. You can guarantee the safety of your data with your protocols, wheras you have no idea the exploits of current game servers


I gotta stop these tired rants

[fade22]

nice :)))