araxiaonline/TrinityCore
3
0
Fork 0
mirror of https://github.com/araxiaonline/TrinityCore.git synced 2026-06-13 03:32:28 -04:00
Code Issues Packages Projects Releases Wiki Activity

* Updated some text files.

Browse Source 
* Removed unused text files.

--HG--
branch : trunk
This commit is contained in:
XTZGZoReX
2009-03-20 17:07:29 +01:00
parent cd898858a6
commit a416f0526c
8 changed files with 29 additions and 324 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
AUTHORS
View File

@@ -1,20 +0,0 @@
The AUTHORS file:
This file should collect a trace of all the legal paperwork that you have
exchanged with contributors for your particular package. This information is
very useful for registering the copyright of your package. The file might
have an introductory blurb similar to this one:
Authors of Trinity Core
The following contributions warranted legal paper exchanges
with [the Free Software Foundation | Your Name].
Also see files ChangeLog and THANKS
Then, list who the contributors are and what files they have worked on.
Indicate whether they created the file, or whether they modified it. For
example:
Random J. Hacker:
entire files -> foo1.c , foo2.c , foo3.c
modifications -> foo4.c , foo5.c

5
ChangeLog
View File

@@ -1,5 +0,0 @@
= Trinity Core -- General information =
Copyright (C) Trinity Core (http://www.trinitycore.org)
A complete changelog can be found at : https://www.bitbucket.org/KingPin/trinitycore/changesets/

2
INSTALL.linux
View File

@@ -1,4 +1,4 @@
= Trinity Core -- Linux installation instructions =
= TrinityCore -- Linux installation =
Copyright (C) Trinity Core (http://www.trinitycore.org)

120
NEWS
View File

@@ -1,120 +0,0 @@
= Trinity Core -- History of visible changes =
Copyright (C) Trinity Core (http://www.trinitycore.org)
See the COPYING file for copying conditions.
<<<<<<< HEAD:NEWS
Please visit the Trinity Core website for bug reports, patch
submissions, suggestions, and support:
http://www.trinitycore.org/
=======
Visit our project website for documentation, and more:
http://getmangos.com/
Visit our forums for support:
http://getmangos.com/community/
Please submit bug reports at:
http://mangos.lighthouseapp.com/
Version 0.13
* Under discussion.
* Upgrade to client version 3.0.9 (build 9551).
Version 0.12
* Migrate from SVN to GIT.
* Implemented arena system.
* Start using Adaptive Communication Environment (ACE) framework v.5.6.6 in server network code.
* Update Visual Leak Detector lib to Version 1.9g (beta).
* Upgrade to client version 2.4.3 (build 8606).
Version 0.11
* Lots of improvements in the spell system.
* Now use Mersenne Twister random number generator.
* MySQL client libs updated to 5.0.56.
* Upgrade to client version 2.4.2 (build 8278).
Version 0.10
* master looter lot mode,
* FFA PvP zones and FFA PvP server type support,
* Guild Banks,
* unique equipped items support, including gems,
* talent inspecting,
* PostgreSql support,
* sockets library updated to v.2.2.9 version,
* 64-bit binaries building at Windows,
* Upgrade to client version 2.3.0 (build 7561).
Version 0.9
* recipes discovery system support,
* more auras, effects, spells, and talents working,
* players queue at login support,
* mangosd/realmd as Windows services support,
* autogeneration mangosd/realmd crash reports (Windows only),
* Visual Studio 2008 Express and Pro support,
* division Mangos DataBase to MangosDB(WorldDB) and CharactersDB.
* Upgrade to client version 2.2.3 (build 7359).
Version 0.8
* battleground support,
* gender specific creatures,
* game objects triggering more scripts,
* more auras, effects, spells, and talents working,
* dungeon specific data,
* localization support for data,
* vmaps for line of sight handling,
* build support for OpenBSD and FreeBSD,
* Upgrade to client version 2.1.3 (build 6898).
Version 0.7, Codename "Eye of the Storm"
* Full rewrite of the GNU autotools based build system, in order to
smooth and clean up the build process.
* Full rewrite of the Windows build system, allowing MaNGOS to be built
from Visual C++ 2003 Toolkit, Visual C++ 2003, Visual C++ 2005.
* Upgrade to client version 2.0.12 (build 6546).
Version 0.6, Codename "Black Dragonflight"
* MaNGOS development moved to http://sourceforge.net/projects/mangos/
* A lots of speed improvements to data handling and data transfer have been
completed.
* Mail, auction house, profession, creature, and game object systems have seen
a lot of improvements and can be considered feature complete. Some minor bugs
still are left.
* Rest system has been finished.
* Initial pet stable support has been added.
* PvP and duel system have seen lots of improvements
* Guilds are not just a myth anymore. Coming closer to full guild support.
* Taxi and transport system is close to a fully working system.
* A lot more has been added.
Version 0.5, Codename "Stable Master"
* Core stability improvements, lots of threading and memory usage related
bugs have been resolved.
* MySQL Database backend has been cleaned up.
* Proper support for game clients of version 1.10.2 has been added.
* Support for auras, pets, spells, talents, totems, etc. has been added
or improved.
* Cross-platform issues have been resolved, MaNGOS should now build on
more platforms, including FreeBSD.
Version 0.1, Codename "Lightbringer"
* AI system
* Grid system
* Lots a game features working.
* Lovely optimizations for the beloved server.
Version 0.0.3, Codename "Mango Carpet"
* Interim release, not gone public.
Version 0.0.2, Codename "Library"
* Most data conversions working.
* Database cleanup.
* More features working.
* Many bugs fixed.
Version 0.0.1, Codename "Endeavour"
* Data converter added.
* Build system improvements.
* Bug fixing and code cleaning.
>>>>>>> f516ed7e9487666e5ef9eaf85660191f9e50db95:NEWS

10
README
View File

@@ -1,6 +1,6 @@
= Trinity Core -- General information =
= TrinityCore -- General information =
Copyright (C) Trinity Core (http://www.trinitycore.org)
Copyright (C) TrinityCore (http://www.trinitycore.org)
Trinity Core is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
@@ -26,11 +26,11 @@ Copyright (C) Trinity Core (http://www.trinitycore.org)
file, but you are not obligated to do so. If you do not wish to do
so, delete this exception statement from your version.
Trinity Core is a World of Warcraft game server emulator. It is derived
TrinityCore is a World of Warcraft game server emulator. It is derived
from MaNGOS, the Massive Network Game Object Server, and is based on the
code of that project.
For further information on the Trinity Core project, please visit our
For further information on the TrinityCore project, please visit our
project website at http://www.trinitycore.org.
API documentation can be obtained by running the "make doc" command inside
@@ -40,4 +40,4 @@ SQL files to create the database can be found in the sql directory. Files
to update your database from an older revision/version can be found in the
sql/updates directory.
See the INSTALL.Linux file for installation instructions under Linux.
See the INSTALL.linux file for installation instructions on Linux.

51
THANKS
View File

@@ -1,37 +1,24 @@
The THANKS file:
= TrinityCore -- Thanks/credits file =
All distributions should contain a `THANKS' file containing a two column list
of the contributors, one per line, alphabetically sorted. The left column gives
the contributor's name, while the right column gives the last known good email
address for this contributor. This list should be introduced with a wording
similar to this one:
TrinityCore is a derivation/rewrite of MaNGOS, which was originally written
by Team Python and the WoW Daemon Team. Many people further helped Trinity Core
by submitting bug reports, code patches, and suggestions. Thanks to the
community!
Trinity Core THANKS file
Special thanks should go out to the WowwoW team. We have gained help from
them many times in the creation of this project. Keep up the good work guys.
Trinity Core is a derivation/rewrite of MaNGOS, which was originally written
by Team Python and the WoW Daemon Team. Many people further helped Trinity Core
by submitting bug reports, code patches, and suggestions. Thanks to the
community!
Thanks to the ScriptDev2 team (http://www.scriptdev2.com) for scripts.
Special thanks should go out to the WowwoW team. We have gained help from
them many times in the creation of this project. Keep up the good work guys.
Thanks to the WCell team (especially Ralek) for research on realm reconnect
sequence, item scaling stats algorithm, gameobject rotation issues.
Thanks to the ImpConfig developer (dythzer) for the custom configuration patch.
Thanks to the ScriptDev2 team (http://www.scriptdev2.com) for scripts.
Thanks to WCell team (especially Ralek) for reseach on realm reconnect sequence,
item scaling stats algorithm, gameobject rotation issues.
The easiest policy with this file is to thank everyone who contributes to the
project, without judging the value of the contribution.
Unlike `AUTHORS', the `THANKS' file is not maintained for legal reasons. It is
maintained to thank all the contributors that helped you out in your project.
The `AUTHORS' file can not be used for this purpose because certain
contributions, like bug reports or ideas and suggestions do not require legal
paper exchanges.
You can also decide to send some kind of special greeting when you initially
add a name to your `THANKS' file. The mere presense of a name in `THANKS' is
then a flag to you that the initial greeting has been sent.
Thanks go out to the following people for various patches/code (listed in the
order they were added): w12x, dythzer, XEQT, death420, balrok, TOM_RUS,
runningnak3d, Seline, KingPin, raczman, bogie, Neo2003, NoFantasy, Derex,
freghar, toilet1, megamage, MadJack, WarHead, gvcoman, Ntsc, arrai, jrkpote,
Seraphim, vagoth, KerchumA222, Rognar, Blaymoira, DragonHunter, Molius, apoc,
SeT, hunuza, Wyk3d, VladimirMangos, rj686, Arthorius, QAston, Muhaha, dereka,
Kaldorei, NuRRi, Biglad, Machiavelli, Nivelo, Paradox, Aokromes, EleGoS,
Visagalis, reno, Cybrax, GriffonHeart, fgenesis, rilex, XTElite1, Anubisss, eL,
Iskander, arclite, Bladex, EIFEL, Klaimmore.

109
bcpp.cfg
View File

@@ -1,109 +0,0 @@
; This file contains configuration parameters that are used
; within the bcpp program.
; There are two types of parameter types : Boolean, and Integer.
; Boolean types can have only two valid values [On, Yes, or Off, No].
; Integer types can have a valid range of 0 - 5000.
;------------------------------------------------------------------------
; This parameter specifies how many lines separate between two
; functions.
;------------------------------------------------------------------------
function_spacing = 1 ; Integer
;------------------------------------------------------------------------
; Specifies whether to use tabs in indenting code.
;------------------------------------------------------------------------
use_tabs = no ; Boolean
;------------------------------------------------------------------------
; Specifies how many spaces to indent. This parameter is also used
; for tab indenting, as 1 tab may be worth 8 spaces if so desired.
; This parameter is used to position comments in TAB mode, and expanding
; of tabs within code!
;------------------------------------------------------------------------
indent_spacing = 4 ; Integer
;------------------------------------------------------------------------
; Specifies whether to indent preprocessor controls to match the code
;------------------------------------------------------------------------
indent_preprocessor = yes ; Boolean
;------------------------------------------------------------------------
; Specifies whether to indent embedded SQL statements
;------------------------------------------------------------------------
indent_exec_sql = yes ; Boolean
;------------------------------------------------------------------------
; Defines at what start position comments that have code on the
; same line to be placed.
;------------------------------------------------------------------------
comments_with_code = 60 ; Integer
;------------------------------------------------------------------------
; Defines at what start position comments with no code start.
;------------------------------------------------------------------------
comments_with_nocode = 0 ; Integer
;------------------------------------------------------------------------
; Set this option to ON turns off setting indentation position of parameter
; "comments_with_nocode". Indentation is then set according to code
; position.
;------------------------------------------------------------------------
leave_comments_nocode = On ; Boolean
;------------------------------------------------------------------------
; Use this option is used to change non-ascii (non-printable) chars to
; octal notation if they lie within quotes. Either
; Ascii_Chars_Only, XOR Leave_Graphic_Chars parameters need to be set
; as a True value for this parameter to take effect.
;------------------------------------------------------------------------
NonAscii_Quotes_to_Octal = yes ; Boolean
;------------------------------------------------------------------------
; Setting this parameter to yes will strip non-printable characters
; from the source files, but leave any character that are IBM
; graphics alone. Any non-printable characters that lie within
; quotes will be transformed into octal/character notation, if
; NonAscii_Quotes_To_Octal parameter is set to True.
;------------------------------------------------------------------------
; leave_graphic_chars = yes ; Boolean
;------------------------------------------------------------------------
; Setting this parameter to yes will strip any non-printable,
; non-ascii characters from the input file. Any non-printable
; octal/character notation if NonAscii_Quotes_To_Octal is set to
; True. Comment out this parameter if you are using
; Leave_Graphic_Chars parameter, as this parameter will override
; it.
;------------------------------------------------------------------------
ascii_chars_only = no ; Boolean
;------------------------------------------------------------------------
; This parameter will place open braces on a new line after it's
; associated code if set on/yes. Else the brace will be place on
; next above line if possible, with it's code.
;------------------------------------------------------------------------
place_brace_on_new_line = yes ; Boolean
;------------------------------------------------------------------------
; This parameter will stop output from the program corrupting output
; that may exit from the program via the standard output.
; If this parameter is set to off/no then no output is generated from
; the program, unless an error is encountered
;------------------------------------------------------------------------
program_output = yes ; Boolean
;------------------------------------------------------------------------
; Specifies what the internal memory requirements will be in size of the
; line processing buffer. This essentially is used only for open brace
; relocation in kernighan/ritchie style.
;------------------------------------------------------------------------
Queue_Buffer = 100 ; Integer
;------------------------------------------------------------------------
; If this option is set to true then the input file will be backup into a
; another file with a ".bac" extension added to the end of the file
; name.
;------------------------------------------------------------------------
Backup_File = yes ; Boolean

36
win/VC90/mangosd.vcproj
View File

@@ -116,10 +116,7 @@
/>
<Tool
Name="VCPostBuildEventTool"
CommandLine="copy ..\..\dep\lib\$(PlatformName)_$(ConfigurationName)\*.dll ..\..\bin\$(PlatformName)_$(ConfigurationName)&#x0D;
&#x0A;
copy ..\..\src\mangosd\mangosd.conf.dist.in ..\..\bin\$(PlatformName)_$(ConfigurationName)\TrinityCore.conf&#x0D;
&#x0A;"
CommandLine="copy ..\..\dep\lib\$(PlatformName)_$(ConfigurationName)\*.dll ..\..\bin\$(PlatformName)_$(ConfigurationName)&#x0D;&#x0A;copy ..\..\src\mangosd\mangosd.conf.dist.in ..\..\bin\$(PlatformName)_$(ConfigurationName)\TrinityCore.conf&#x0D;&#x0A;"
/>
</Configuration>
<Configuration
@@ -219,10 +216,7 @@
/>
<Tool
Name="VCPostBuildEventTool"
CommandLine="copy ..\..\dep\lib\$(PlatformName)_$(ConfigurationName)\*.dll ..\..\bin\$(PlatformName)_$(ConfigurationName)&#x0D;
&#x0A;
copy ..\..\src\mangosd\mangosd.conf.dist.in ..\..\bin\$(PlatformName)_$(ConfigurationName)\TrinityCore.conf&#x0D;
&#x0A;"
CommandLine="copy ..\..\dep\lib\$(PlatformName)_$(ConfigurationName)\*.dll ..\..\bin\$(PlatformName)_$(ConfigurationName)&#x0D;&#x0A;copy ..\..\src\mangosd\mangosd.conf.dist.in ..\..\bin\$(PlatformName)_$(ConfigurationName)\TrinityCore.conf&#x0D;&#x0A;"
/>
</Configuration>
<Configuration
@@ -323,10 +317,7 @@
/>
<Tool
Name="VCPostBuildEventTool"
CommandLine="copy ..\..\dep\lib\$(PlatformName)_$(ConfigurationName)\*.dll ..\..\bin\$(PlatformName)_$(ConfigurationName)&#x0D;
&#x0A;
copy ..\..\src\mangosd\mangosd.conf.dist.in ..\..\bin\$(PlatformName)_$(ConfigurationName)\TrinityCore.conf&#x0D;
&#x0A;"
CommandLine="copy ..\..\dep\lib\$(PlatformName)_$(ConfigurationName)\*.dll ..\..\bin\$(PlatformName)_$(ConfigurationName)&#x0D;&#x0A;copy ..\..\src\mangosd\mangosd.conf.dist.in ..\..\bin\$(PlatformName)_$(ConfigurationName)\TrinityCore.conf&#x0D;&#x0A;"
/>
</Configuration>
<Configuration
@@ -427,10 +418,7 @@
/>
<Tool
Name="VCPostBuildEventTool"
CommandLine="copy ..\..\dep\lib\$(PlatformName)_$(ConfigurationName)\*.dll ..\..\bin\$(PlatformName)_$(ConfigurationName)&#x0D;
&#x0A;
copy ..\..\src\mangosd\mangosd.conf.dist.in ..\..\bin\$(PlatformName)_$(ConfigurationName)\TrinityCore.conf&#x0D;
&#x0A;"
CommandLine="copy ..\..\dep\lib\$(PlatformName)_$(ConfigurationName)\*.dll ..\..\bin\$(PlatformName)_$(ConfigurationName)&#x0D;&#x0A;copy ..\..\src\mangosd\mangosd.conf.dist.in ..\..\bin\$(PlatformName)_$(ConfigurationName)\TrinityCore.conf&#x0D;&#x0A;"
/>
</Configuration>
</Configurations>
@@ -440,26 +428,10 @@
<Filter
Name="doc"
>
<File
RelativePath="..\..\Authors"
>
</File>
<File
RelativePath="..\..\ChangeLog"
>
</File>
<File
RelativePath="..\..\Copying"
>
</File>
<File
RelativePath="..\..\Install"
>
</File>
<File
RelativePath="..\..\News"
>
</File>
<File
RelativePath="..\..\Readme"
>