Note:
In some rare occasions you'll have messages like that:

Hit "Control+F7" to pass that until the server is launched.
When a crash occurs, Codeblocks will trap it and will tell you where it happened:
http://i28.tinypic.com/10n829k.png
Be sure to have the "call stack" window opened:


To have all the interesting informations like line numbers and so on, make a screenshot of it.

See this thread to know what watches are (seeing variables values while debugging).
Press the stop to stop debug mode:

6°) Update the server (SVN):
It's easy. First stop all the servers, else you would have troubles.
Then right click on the folder where is your source code, then select "SVN Update":

And wait...

Now, of course if some code changed in the server, REBUILD them before launching them again.
7°) See the SVN Logs:
For each rev, the devs tell what changed. It's QUITE important you READ them!
To do this, simply right click on the folder where you source code is, then "properties":

---------- Post added at 01:58 PM ---------- Previous post was at 01:57 PM ----------
Then tab "subversion" and "show log".

Wait a bit and you'll have the history.

8°) Dev rev updates:
Sometimes from one rev to another some files are updated, like STB, AIP and QSD files. Those files don't need special handling.
Though sometimes some databases files (.sql) are changed, you NEED to import back those files into your mysql database, with Navicat for example.
The best way is FIRST to delete the according database table BEFORE importing the new one.
For example if you "list_npcs.sql" changed, delete the table "list_npcs" and import after the file "list_npcs.sql".
9°) How to post a bug, how to export data from an avatar:
See this thread in bug forum:
osROSE Forums • View topic - New topic icons for bugs, please use them. (and rules)
10°) how to launch the game?:
Make a batch file (like "rose.bat") near Trose.Exe with this command line:
Code:
TRose.exe @TRIGGER_SOFT@ _server your_server_ip
so for example:
Code:
TRose.exe @TRIGGER_SOFT@ _server 127.0.0.1
11°) GM commands:
Most of the time GM Commands needs at least a 300 level AND the "isgm" flag set to 1 for a player.
You can set the player's "level" into the "account" mysql table, it will apply for ALL his avatars (characters).
You can set the "isgm" to 1 into the "characters" mysql table, for each of his avatar (one can have this, one don't...).
If you want to give your players access to some GM commands, you must set the access level for this command so they can use them. It's in file "commands.ini". By default it's GM (level 300) only, for example /go:
If you want players (who are only level 100) to access it you need to change the value by:
Notes:
-> For your GMs it's better than you give them 300 level AND the isGM set to 1,
-> Some GM commands check that the "isgm" flag is set to 1 for example:
Code:
if(Config.Command_Ban > thisclient->Session->accesslevel || thisclient->CharInfo->isGM == false)
So this command wouldn't be accessible to players, even if you lower its access to "99" in commands.ini.
Once again thanks to lmame of OsRose for this guide and his continued work on the OsRose project.