POT
POT
POT
Main menu

Download

Forum

SVN

Prev Next

AAC scripts

This small article describes general info about OTServ AAC scripts.

Table of Contents

Basics

Welcome! On this website you will find info about OTServ accmakers. This website is dedicated both for people who dont know anything about that and authors of such scripts. Beginners will find here basics and clues about how to use such scripts, as well as ready solutions for their's AAC. AAC creators should follow instructions on this site in order to make those scripts well.

Many people want to start using AAC scripts without knowledge. They spam forums, IRC channels and people IMs. If you dont know anything about AAC scripts, then this site is perfect for you. Before you will ask any question, read this website. If you will still dont know the answer, think before ask.

Mainly last times there went out planty new AAC scripts. Too bad they are very poor and people who make them don't know anything about their's job. People started to think that if they made "own AAC" (which usualy means to copy other script and sign with own nickname) they are cool - sorry guys - you only show how stupid your codes are. This website provides information about how to make good scripts and promotes ready solutions for safe and stable websites. We hope this website will change the situation and people who are creating accmakers will correct their's works or leave publishing bad scripts.

What is AAC?

AAC stands for Automatic Account Creator also called accmaker. Most generaly it is a program (application, or script) that autmates account creation process. However for a long time already simple accmakers aren't enought - nowadays avarage AAC should have additional options like account management, statistics and character lookup.


Types of AAC

Basicly there two types of accmakers: websites and in-game. In-game AACs are NPCs that ask user for account and character information. To use such AAC person must log into special account (usualy 1/1). Website AACs provides much more features - you can browse web from every place and from many devices. You can access it globaly. Also those accmakers aren't restricted by Tibia client and can be extended in many ways. Usualy website accmakers are PHP scripts and works on various HTTP servers.


Why not ingame

First when people of OTS world weren't familiar with PHP, HTTP servers they were just addeding some code to server and account used to be craeted after logging in on special password where was NPC to complete the process. As OTS community were extending and new ideas came out, there appeared first website scripts - they provided at least so much functionality as NPC accmaker. With time website AACs was extending and now they usualy contains many features that NPC would never have. Website AAC is accessable from every device where you have the Internet and browser so it means nearly every computer all over the world in this days. But those are all advantages of website AAC - there is one more reason which simply disqualifies in-game AACs: they are in fact impossible. Why? It is possible to create such AAC only if you add your server to many lists and links. To use in-game AAC people need to know your IP to connect and have Tibia client to use AAC. Normaly they wouldn't know that and Tibia client is not a stadard application that is installed in every computer. The only way to provide accessibility for users is a website.


Website AAC HOWTO

Website AAC is most commonly used type of accmaker. People who want to use it first time find it hard to install and mainternace. In fact it can be - you really need to know what you are doing with it and how does it work. Usualy this type of AAC is a PHP script so we won't discuss other cases. To run PHP script you need a HTTP server - program which will provide website for people from outside, with installed PHP - interpreter of PHP scripts that executes them. It is quite easy to install Apache and PHP manualy, but it is described all over the net, so we won't descire it here.


Main features

Of course basic AAC script feature, as the name says, must be account creation. But from the time when the first website accmaker was made (about 2004) scripts of that kind were extended and now "just AAC" is never enought. Empty site with only form for account creation shows that server is poor, that administrator doesn't care about it (and users) and he is probably a noob that just wanted to have "my own masta OTS". Currently even simple accmaker must provide some basic features.

Account creation is of course the most basic AAC feature. But this is also the point which is made wrong in nearly every scirpt. Account number has to be random and generated during account creation, not during entering website by user. That's most important critertium which we used fro our recommended scripts. This is for safety reasons, but not only. It is simply only possible way of correct implementation - people who make it other way simply don't know what they are doing as this is very unstable realisation.

On the beginning first accmaker was just a website form for creating account and character. But someone who made script was just lazy and finished work in that point. First more extended script was OTSCMS which was first that introduced login mechanism and allowed users to manage account form website. It means that they could create many characters on one account, or for example change password. Currently accmakers with only account creation form are not even worth to downloading (except PVP servers) and account managers are now standard.

Other important features of website AAC scripts are ideas based on oryginal Tibia website. Many script contains statistics page where are listed players with highest scores, character view page where it is possible to check information about given player. Also lastly guilds system is very popular. Very important is, to merge website with OTServ world and create some kind of community, it means that on wbesite player should be affected, or at least connected with character in game.

Also very important is, to provide easy way of changing website behaviors and/or layout without editing script engine. Some scripts contains template engines, multilanguge support and modular structure. All those things give user ability to make website to look just like he wants. Everyone wants to have oryginal website which will impress visitor.

Don't touch!

Before using, every AAC needs to be installed. It requires to put information about OTServ as it needs to work on it's database. Many dumb people create scripts and just put configuration file there so people will edit it. Too bad they don't even know about how to distribute PHP scripts, so how avarge user should know it? Script is a code - user mustn't touch the code. Code is a hermetic enviroment - when user will edit it and type something wrong it will crush. Every PHP script that needs to be edited in any way, includes installer, or just configuration editor. With such script user fills settings on website and installer checks and validates them and then creates configuration file with saved settings.


Important notes

This website presents some ways of AAC script developement that should be followed. It is not just our wish, but we presents clever and considered ideas. Those are just real points of view.


Scripts with POT

If you plan to use AAC script it is good to check if the one you use is POT-based or at least provides POT enviroment. POT is standard way for PHP scripts to access database and other resources so if you will find any code that bases on POT it will surely work with your AAC if only it provides POT enviroment.

Here are some examples of POT in use:

We want to promote "good scripts" and usage of POT. If you have a script that fits our requirements you can contact us - we will add it to list.

Link

If you want to help us you can put following image on your website:

You can use following code for that:

  1. <a href="http://otserv-aac.info/">
  2.     <img alt="OTServ AAC" src="http://otserv-aac.info/aac.png"/>
  3. </a>
Prev Up Next
Creating framework Additional info Troubleshooting