-
Notifications
You must be signed in to change notification settings - Fork 202
How to install
Infact you can directly use their installation instructions - they also cover ScriptDev2’s installation
Clone ScriptDev2 git clone git://github.com/scriptdev2/scriptdev2.git ScriptDev2 - execute from within src/bindings directory
MS Windows:
Compile ScriptDev2 using the scriptVC80, scriptVC90 or scriptVC100 Solution within the ScriptDev2 folder (this will overwrite the Mangoscript dll in the output directory)
GNU/Linux or CMake:
When running CMake on MaNGOS, make sure to set -D INCLUDE_BINDINGS_DIR=ScriptDev2
Compile MaNGOS (ScriptDev2 will automatically be built when compiling Mangos from here on)
- Create ScriptDev2-Database
-
Execute
sql\scriptdev2_create_database.sql, then execute
sql\scriptdev2_create_structure.sqlon that database. - Add content to ScriptDev2-Database
-
Execute
sql\scriptdev2_script_full.sqlon scriptdev2 database - Update ScriptNames
-
Execute
sql\mangos_scriptname_full.sqlon your MaNGOS world Database
Place the included "scriptdev2.conf" file within the directory containing your "mangosd.conf" and "realmd.conf" files.
You may need to change this file to match the database you created and any custom settings you wish to use.
Note this file will be differently created for Unix based systems.
-
Enter src/bindings/ScriptDev2 directory (with git-bash)
-
Update ScriptDev2 with
git pull -
Compile ScriptDev2
On windows you must still compile MaNGOS before ScriptDev2 -
Update your Database with new Scriptdev2 SQL changes. For this you can either:
-
apply only the changes that were made during that revision by looking in the sql\update folder or (files named rXXX_scriptdev2.sql should be executed on the scriptdev2 db while rXXX_mangos.sql should be executed on your mangos db)
-
reapply "mangos_scriptname_full.sql" to your MaNGOS database. - WARNING this will NOT include removed script names!
-
You can view the ScriptDev2 change log on the ScriptDev2 Github Repository.
Or of course locally with your Git GUI tools or with git log (Note that it should be up to date before looking into your local log)