m (Text replacement - "git://" to "https://") |
|||
(8 intermediate revisions by 3 users not shown) | |||
Line 13: | Line 13: | ||
* Open a terminal. | * Open a terminal. | ||
sudo yum install gcc-c++ make git | sudo yum install gcc-c++ make git | ||
''' TMW-Herc addtions ''' | |||
* Open Terminal. | |||
sudo apt-get install mysqlclient-dev package or mariadbclient-dev libtool libpcre-dev automake autoconf | |||
sudo yum install mysqlclient-dev package or mariadbclient-dev libtool libpcre-dev automake autoconf | |||
Note that you must have gcc 4.6 or later. Any modern distro will have this version, but "stable" distros with very long release cycles, such as Red Hat Enterprise Linux, might not. | Note that you must have gcc 4.6 or later. Any modern distro will have this version, but "stable" distros with very long release cycles, such as Red Hat Enterprise Linux, might not. | ||
Line 21: | Line 26: | ||
mkdir ~/tmwAthena | mkdir ~/tmwAthena | ||
cd ~/tmwAthena/ | cd ~/tmwAthena/ | ||
git clone --recursive | git clone --recursive https://github.com/themanaworld/tmwa.git | ||
git clone --recursive | git clone --recursive https://github.com/themanaworld/tmwa-server-data.git | ||
cd tmwa/ | cd tmwa/ | ||
echo "export PATH=$PATH:~/bin" >> ~/.bashrc | echo "export PATH=$PATH:~/bin" >> ~/.bashrc | ||
Line 29: | Line 34: | ||
make | make | ||
make install | make install | ||
git config --global url.git@github.com:.pushInsteadOf | git config --global url.git@github.com:.pushInsteadOf https://github.com ''{{ref|push}} {{ref|once}}'' | ||
cd ../tmwa-server-data | cd ../tmwa-server-data | ||
make conf | make conf | ||
Line 51: | Line 56: | ||
git clone https://gitorious.org/evol/evol-hercules.git ./evol | git clone https://gitorious.org/evol/evol-hercules.git ./evol | ||
cd ~/tmwAthena/ | cd ~/tmwAthena/ | ||
git clone --recursive https://github.com/wushin/tmwa-server-data | git clone -b tmw-herc --recursive https://github.com/wushin/tmwa-server-data ./server-data | ||
ln -s ./server-data | ln -s ./server-data/client-data ./client-data | ||
git clone https://gitorious.org/evol/evol-tools.git | git clone https://gitorious.org/evol/evol-tools.git | ||
ln -s ./evol-tools/hercules/templates ./templates | |||
git clone https://github.com/HerculesWS/Hercules.git ./serverdata | |||
cd hercules/ | cd hercules/ | ||
./build.sh | ./build.sh | ||
make install | make install | ||
cd ../server-data | cp -f ./athena-start ../server-data/ | ||
./athena-start | cd ../evol-tools/localserver | ||
./initdb.sh | |||
cd ../../server-data | |||
./athena-start start | |||
* Migrate TMWA to Herc | * Migrate TMWA to Herc | ||
Line 71: | Line 80: | ||
cd ~/tmwAthena/ | cd ~/tmwAthena/ | ||
mv tmwa-server-data server-data | mv tmwa-server-data server-data | ||
ln -s ./server-data/client-data ./client-data | |||
ln -s ./server-data ./oldserverdata | ln -s ./server-data ./oldserverdata | ||
ln -s ./server-data ./newserverdata | ln -s ./server-data ./newserverdata | ||
git clone https://gitorious.org/evol/evol-tools.git | git clone https://gitorious.org/evol/evol-tools.git | ||
ln -s ./evol-tools/hercules/templates ./templates | |||
git clone https://github.com/HerculesWS/Hercules.git ./serverdata | |||
cd hercules/ | cd hercules/ | ||
./build.sh | ./build.sh | ||
make install | make install | ||
cp -f ./athena-start ../server-data/ | |||
cd ../serverdata | |||
cp -r npc/ db/ conf/ ../server-data/ | |||
cd .. | |||
./evol-tools/hercules/convert_server.py | ./evol-tools/hercules/convert_server.py | ||
cd ../server-data | cd ./evol-tools/localserver | ||
./athena-start | ./initdb.sh | ||
cd ../../server-data | |||
./athena-start start | |||
==Hosting Updates== | ==Hosting Updates== | ||
Line 148: | Line 166: | ||
git format-patch -M -C origin/master | git format-patch -M -C origin/master | ||
* pastebin the patch(es) and post for review at irc. | * pastebin the patch(es) and post for review at irc.libera.chat channel: #themanaworld-dev or on our [http://forums.themanaworld.org/viewforum.php?f=18 development forums]. '''Extensive patches must be posted on the forum as a series of well-formed patches with descriptive commit messages.''' In particular, later patches should not fix errors introduced in earlier patches, and each patch should form a logically independent part. | ||
<span style="color:#FF0000"> '''Note :''' This is kind of outdated; with github it's often easier to do patches on branches there. see: '''[[Working With Git]]''' page</span> | <span style="color:#FF0000"> '''Note :''' This is kind of outdated; with github it's often easier to do patches on branches there. see: '''[[Working With Git]]''' page</span> |
Latest revision as of 01:07, 13 June 2022
We're using Git as version control system for our source files and content. Have a look at our Tutorial about how to use Git.
Set Up
This is a how to help content development for official server (tmwAthena) using Ubuntu and the Mana+ client. Other OS and clients may differ. Following this guide, you should be able to get development testing versions of the client data (tmwa-client-data), server-data (tmwa-server-data) and participate in development by using a localhost server. After getting these, you can both test current development and begin development in the direction you find most fitting.
Install Dependencies
Debian derivates (including Ubuntu)
- Open a terminal.
sudo apt-get install g++ python make realpath git
Fedora derivates
- Open a terminal.
sudo yum install gcc-c++ make git
TMW-Herc addtions
- Open Terminal.
sudo apt-get install mysqlclient-dev package or mariadbclient-dev libtool libpcre-dev automake autoconf sudo yum install mysqlclient-dev package or mariadbclient-dev libtool libpcre-dev automake autoconf
Note that you must have gcc 4.6 or later. Any modern distro will have this version, but "stable" distros with very long release cycles, such as Red Hat Enterprise Linux, might not.
Set Up TMWA Server
Here are the steps to use when creating a new local testing server.
- Open a terminal.
mkdir ~/tmwAthena cd ~/tmwAthena/ git clone --recursive https://github.com/themanaworld/tmwa.git git clone --recursive https://github.com/themanaworld/tmwa-server-data.git cd tmwa/ echo "export PATH=$PATH:~/bin" >> ~/.bashrc source ~/.bashrc ./configure --user make make install git config --global url.git@github.com:.pushInsteadOf https://github.com [1] [2] cd ../tmwa-server-data make conf
- Preferably, add the update hooks.
ln -s ../../git/hooks/post-merge .git/hooks/ ln -s ../../../../git/hooks/post-merge .git/modules/client-data/hooks/ # (git 1.7.8 or newer) ln -s ../../../git/hooks/post-merge client-data/.git/hooks/ # (git 1.7.7 or older) cd client-data git checkout master cd music git checkout master
Set Up Herc Server [WIP]
- Create New Server:
mkdir ~/tmwAthena cd ~/tmwAthena/ git clone https://gitorious.org/evol/hercules.git cd hercules/src/ git clone https://gitorious.org/evol/evol-hercules.git ./evol cd ~/tmwAthena/ git clone -b tmw-herc --recursive https://github.com/wushin/tmwa-server-data ./server-data ln -s ./server-data/client-data ./client-data git clone https://gitorious.org/evol/evol-tools.git ln -s ./evol-tools/hercules/templates ./templates git clone https://github.com/HerculesWS/Hercules.git ./serverdata cd hercules/ ./build.sh make install cp -f ./athena-start ../server-data/ cd ../evol-tools/localserver ./initdb.sh cd ../../server-data ./athena-start start
- Migrate TMWA to Herc
Assumes TMWA is Installed as per this page.
cd ~/tmwAthena/ git clone https://gitorious.org/evol/hercules.git cd hercules/src/ git clone https://gitorious.org/evol/evol-hercules.git ./evol cd ~/tmwAthena/ mv tmwa-server-data server-data ln -s ./server-data/client-data ./client-data ln -s ./server-data ./oldserverdata ln -s ./server-data ./newserverdata git clone https://gitorious.org/evol/evol-tools.git ln -s ./evol-tools/hercules/templates ./templates git clone https://github.com/HerculesWS/Hercules.git ./serverdata cd hercules/ ./build.sh make install cp -f ./athena-start ../server-data/ cd ../serverdata cp -r npc/ db/ conf/ ../server-data/ cd .. ./evol-tools/hercules/convert_server.py cd ./evol-tools/localserver ./initdb.sh cd ../../server-data ./athena-start start
Hosting Updates
TMW makes it easy to generate delta zips out of a repository, once it is initially set up.
It will put them in ~/www/updates/, which may be a symlink to wherever your web server is really serving. Setting up a webserver is not covered here.
Once everything is set up, just run 'make updates' from the server-data dir every time client-data changes. It will do nothing if appropriate, generate complete zips the first time, and incremental zips afterwards.
Some notes:
- You must put news.txt and skeleton resources.xml file (and maybe an empty resources2.txt) in ~/www/updates/ first.
- Music updates are never added; they should be in the skeleton and updated manually if needed.
- You definitely want to run one of the analyzer scripts frequently, and remove the old updates.
Updating the Server
Running and Administrating the Server
The TMWAthena is in fact 3 servers:
- tmwa-login which manages accounts and connection to char server.
- tmwa-char which manages characters and connects them to the map server.
- tmwa-map which manages game content (maps, monsters, items, scripts...) and their interaction with characters
- Start the servers: Open a terminal and run all the local servers. To stop them, either close the terminal or type control-C.
cd ~/tmwAthena/tmwa-server-data/ ./run-all
- In a new terminal, Launch tmwa-admin the administration tool, add yourself as an user and make yourself a GM:
cd ~/tmwAthena/tmwa-server-data/login tmwa-admin add <username> M <password> gm <username> 99
Note : Be sure that you are running tmwa-admin from within the "login/" directory. Check that the config files are correct: the connection port should be 6901 for tmwa's configuration, not 6900, which is the hard-coded default.
See also: GM Commands
Connecting
- Open a command line terminal and run your client pointing to your client data and your local server :
manaplus --server localhost --port 6901 -u -d ~/tmwAthena/tmwa-server-data/client-data
If all went well, you are now ready to test new content and participate with development.
develop new content
You are now free to do some changes, first close the client and your servers.
Notes for client data changes: 1) commit and push them in the client-data repo 2) commit and push "client-data" when it shows "(new commits)" in your server-data 3) commit and push other server data changes.
- Make your modifications (e.g. Change a map) and save them.
- Open a terminal.
cd ~/tmwAthena/tmwa-server-data/client-data git status git add [modified files] git commit
git push
cd .. make maps (if you changed a map) git status git add [modified files] git add client-data (if git status shows (new commits). Don't do this if you don't have push access to client-data!) git commit
git push
- Close the terminal.
: a step for those with commit access to the remote repositories. For others, you don't need to reconfigure your clone and please make a patch on steps where git push is suggested.
: you only need to do this once, no matter how many times you independently clone the repositories.
git format-patch -M -C origin/master
- pastebin the patch(es) and post for review at irc.libera.chat channel: #themanaworld-dev or on our development forums. Extensive patches must be posted on the forum as a series of well-formed patches with descriptive commit messages. In particular, later patches should not fix errors introduced in earlier patches, and each patch should form a logically independent part.
Note : This is kind of outdated; with github it's often easier to do patches on branches there. see: Working With Git page
You can also pull the data which has been modified.
- Open a terminal.
cd ~/tmwAthena/tmwa-server-data git pull
- If you haven't installed the hook,
git submodule update --merge at toplevel (for client-data) and in client-data (for music)
- Close the terminal.
See Also: README.mv.txt - Documentation on using git submodules, like client-data and tmw-music.
Making Content
Making Map Content
See Mapping Tutorial.
Python Converter Tool
After editing maps for the client, you need to generate the walkmaps and imports for the server. yhis can be done either by the Tiled application or by running the python script tmx_converter.py which is located in the tools folder of the Server Data folder. (see Mapping Tutorial#Creating the WLK files) After that, commit and push the files that the converter edited. Note that, if you do not have push access to the main repository, you should let someone else update the submodule itself.
Getting Art Content Into The Game
- Post [CPT] or [WIP] art on the graphics development forum.
- Work with the Art Director and collaborators on getting the art consistent.
- When finished, edit topic as [FND].
- Art Director approves [FND] art and marks it [RC]. Should the art need animation or special effect, the Art Director requests xml for it. If not, the Art Director commits it and marks as [GIT].
- XML Team reviews or drafts xml related to the art, then commits the .png and .xml. Topic can be marked as [GIT].
- Art content affected: client-data/graphics/sprites then related directory for .png and .xml animation addition.
- Project developer requests database entry reservations from a General Content Team developer.
- Map entry server data affected: resnametable.txt and .wlk files in the data directory, map content files in the npc directory.
- Map entry client data affected: .tmx files in the maps directory.
- Map entry requires the running of the .tmx converter (aka java converter) before commits can be made.
- Art content server data affected: entry made in the item_db.txt, mob_db.txt or mob_skills_db.txt in the db directory.
- Art content client data affected: entry added in items.xml, monsters.xml or other identification file.
Handling General Content Team [REQ]s
- General Content Team member adds a [REQ] topic to the graphics development forum.
- General Content Team member adds the [REQ] topic as a hyperlink under "Required Art" on the Art in Development page.
- Art Director attempts to network with other artists to assign the art to an artist.
Bit Masking
Bit Masking helps us reduce our variable count while offering a dynamic method of script writing that is versatile and flexible to both linear and non-linear script writing.
Generating client updates
- Shutdown all your servers.
- First we are going to check the config files to be sure the paths are correct.
cd ~/tmwAthena/tmwa-server-data/client-data/tools/ ls
Output: add-git-attributes edit-all-to-export-tilesets.sh formatXML.sh list-tileset-order map-db.py minimap-render.py adler32 edit-map-tileset-names.sh indent.xsl make-updates map-diff.py End of output
- The easiest solution is to create a symbolic link to that directory
ln -s /var/www/tmwupdates ~/www/updates (your public www folder is /tmwupdates)
- You can Edit the make-updates file with gedit or nano or vi.
Search for the folowing lines: output=~/www/updates And change them to: output=/var/www/tmwupdates (your public www folder is /tmwupdates)
- Save the file and get back in the terminal.
cd ~/tmwAthena/tmwa-server-data/login/conf ls
Output: ladmin_athena.conf lan_support.conf login_local.conf.example ladmin_local.conf login_athena.conf ladmin_local.conf.example login_local.conf End of output
- Edit the login_local.conf with an editor and look for the following line:
update_host: http://updates.themanaworld.org/
- Change that line to:
update_host: http://127.0.0.1/tmwupdates/ (or use your external ip)
- Save the file and get back in the terminal.
- Open a terminal.
First we compile the adler32 tool to generate a hash.
cd ~/tmwAthena/tmwa-server-data/client-data/tools/adler32/ make
Output must be: gcc -lz -o adler32 adler32.c
make install
- Now that we compiled the adler tool we can make us a update.
cd ~/tmwAthena/tmwa-server-data/ make updates
- Each time you want to make new updates
make sure you have a new commit then cd ~/tmwAthena/tmwa-server-data/ make updates