I am making a fansite for a game (Lineage 2) and have found a "Lineage 2 Documentation Project" which has info on everything I wanted to put on the site, templates and all but I am having a problem, here is what the readme says:
"This is the database of Lineage 2 information, where we can all share the
info, and in all 3 languages. In this way we can all run up to date web sites
but share in the hosting duties. This way noone has to have a huge ISP bill.
I have the time and skills to make/maintain the database, but not the time to
run a fan site myself.
Basicly, there is alot of exported data, and then we perform fixes to it at
the correct time during the process. The database constraints then enforce the
rules. For example, after the items are first created, we remove 4 Lineage 1
swords with fix-items.sql. Any further updates or drop rules involving those
4 items just don't update/insert. Order is important, but failed SQL commands
are normal. Comments, Comments, Comments - every fix should have one. So not
modify any of the files in data.tgz. The files are listed in order in
FILES.TXT.
If the data seems a bit... strange... like how shields are weapons
( WHERE hands = 'shield' ) it's that way because of NC, not me :)
As far as updates, dont bother too much until the game is out, things are
still changing far too quickly. But once it stablizes, I'll re-export the
data I can get my hands on, and we simply modify the fix-*.sql files,
and share them. Then everyone has the same data worldwide, but each
webmaster can display/tweak as needed.
You should always be able to rebuild your entire database with the load-db
script (which rebuilds the database from scratch). Your local changes should
be MINIMAL becasue we're sharing data. I'm sharing all this data on the
condition that you all share it as well, but you should add yourself in as a
monster of course ;)
load-db.pgsql is for PostgreSQL, load-db.mysql is for mySQL, use only one.
They unfortunately only work if you have access to the command line tools.
The data files should _always_ be standard SQL. I have have added indexes to
all field that get crossreferenced. But since you're all using static HTML
pages it's not an issue.
items.sql and skills.sql are Chronicle 1 data, if you are using an outdated
version of Lineage2 in your country, then you will want items-prelude.sql and
skills-prelude.sql instead. Just edit your load-db file.
Oh, and yes, it's all UTF-8, it can't work any other way, so you may need
to read
http://www.cl.cam.ac.uk/~mgk25/unicode.html#web
I recommend the web server changes, there is no excuse for anything but UTF-8.
You'll also have to create the lineage2 database in UTF-8
`createdb -E UNICODE lineage2` but you knew that already ;)
Step one is to unzip images.tgz and data.tgz, making data/ and images/.
Then create the lineage2 database (see above).
Run the load-db script or load the files in the order listed in FILES.TXT.
Finish reading this README for what is where.
Look at QUERIES.SQL to get you started."
I think I created the DB correctly, and after that it loses me, I tried different things I thought it was telling me to do, but I was obviously wrong and got errors. So I am asking for info on what exactly I need to go about doing after I have created the DB. Thanks for any help.