sindoring/felwell-core
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

base: DestinyCore upstream @2d631f4e (fork SylvaniaCore ; sql/old retire)

Browse Source
This commit is contained in:
SylvaniaCore deploy
2026-06-17 09:00:37 +00:00
commit f8fcb8ad38
4834 changed files with 2810723 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/COMPILATION_HELP.TXT
+31
View File
@@ -0,0 +1,31 @@
NOTE TO USERS WITH COMPILE-ERRORS :
Before commenting on our issuetracker that "it doesn't compile", we ask you
to do the following :
* Clear the CMake cache
In certain cases we adjust and modify the buildsystem (adding/removing
functions/functionality.
* Remove/delete and recreate your build directory, and recompile
In most cases any linking-errors are related to that the build-
system has not caught up with specific changes.
* Compile on a CLEAN sourcetree
We can not, for obvious reasons, support cores that has been modified.
As you might understand, we're not psychics: we're not aware of what
you have done to your sourcetree, and as such : We can't see what your
additional code is like.
* SUPPLY PROPER LOGS ON COMPILE-ERRORS
This means: Add as MUCH info as possible to the issue, including the
full log from the compile itself (or at least include the 20 lines
above AND under the compile-error itself).
Happy compiling, and have a nice day!
-- The TrinityCore developers
doc/CharacterDBCleanup.txt
+34
View File
@@ -0,0 +1,34 @@
The purpose of the CharacterDB cleanup routines is to remove old, non-
existent and erranous/defunct skills, talents, spells, and achievements
from characters in the database.
To achieve this, add an entry (number) in the worldstate-table
(id:20004), combining the following arguments (bitmasked):
CLEANING_FLAG_ACHIEVEMENT_PROGRESS = 0x1
CLEANING_FLAG_SKILLS = 0x2
CLEANING_FLAG_SPELLS = 0x4
CLEANING_FLAG_TALENTS = 0x8
CLEANING_FLAG_QUESTSTATUS = 0x10
Example:
We want to clean up old talents, spells and skills, but leave
achivements alone - ie. NOT touching those. We'd then need to combine
the numbers from each of the above fields:
CLEANING_FLAG_SKILLS + CLEANING_FLAG_SPELLS + CLEANING_FLAG_TALENTS
This comes out as 2+4+8 => 14, and we now put an entry in for this in
the worldstate table (this is done on the CHARACTERS database) :
UPDATE worldstates SET value=14 WHERE entry=20004;
This will then (when the core is restarting) clean up old and missing
skills, spells and talents.
Please note that we are not responsible for any issues that might come
from this, and that you are (as the owner of the database), responsible
for doing proper backups prior to doing the above in case of anything
going wrong.
-- The TrinityCore developer team
doc/FileHeaders.txt
+58
View File
@@ -0,0 +1,58 @@
To make things look uniform here's the headers we use for sourcefiles.
It makes it "prettier" as it's applied to any of the sourcefiles
(source and headers) , giving us a template licensing-style that we stick to
(or at least keeping in the same style licensewise).
XXXX = startyear
YYYY = active year
Standalone (no previous code from anyone) :
--- SNIP ---
/*
* Copyright (C) 2008-YYYY TrinityCore <https://www.trinitycore.org/>
*
* This program is free software; you can redistribute it and/or modify it
* under the terms of the GNU General Public License as published by the
* Free Software Foundation; either version 2 of the License, or (at your
* option) any later version.
*
* This program is distributed in the hope that it will be useful, but WITHOUT
* ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
* FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
* more details.
*
* You should have received a copy of the GNU General Public License along
* with this program. If not, see <http://www.gnu.org/licenses/>.
*/
--- SNIP ---
With previous code from external developers:
--- SNIP ---
/*
* Copyright (C) 2008-YYYY TrinityCore <https://www.trinitycore.org/>
* Copyright (C) XXXX-YYYY external-teamname <url>
*
* This program is free software; you can redistribute it and/or modify it
* under the terms of the GNU General Public License as published by the
* Free Software Foundation; either version 2 of the License, or (at your
* option) any later version.
*
* This program is distributed in the hope that it will be useful, but WITHOUT
* ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
* FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
* more details.
*
* You should have received a copy of the GNU General Public License along
* with this program. If not, see <http://www.gnu.org/licenses/>.
*/
--- SNIP ---
Please note that if several parties are involved in the creation of a file, you
WILL need to expand the copyright headers accordingly.
Thank you for using these headers when you add new files/modify already existing
files!
- The TrinityCore developers
doc/GPL-2.0.txt
+339
View File
@@ -0,0 +1,339 @@
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Lesser General Public License instead.) You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License along
with this program; if not, write to the Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Lesser General
Public License instead of this License.
doc/HowToScript.txt
+17
View File
@@ -0,0 +1,17 @@
** HOW TO SCRIPT IN C++ **
=========================================================
WARNING: THIS DOCUMENTATION IS NOT ALWAYS UP TO DATE.
FOR MORE UP-TO-DATE INFORMATION, CHECK THE TRINITY WIKI.
=========================================================
1 - create a file myscript.cpp in the scripts/custom folder.
2 - Find the appropriate examples script in the scripts/examples folder and copy its contents.
Don't forget to rename the classes as appropriate!
3 - Rename the AddSC functions as appropriate.
4 - Make sure to change the initializations in the AddSC function to the appropriate script names!
5 - Under ScriptLoader.cpp, add your AddSC function near the top and in AddCustomScripts(), call it.
6 - Add your myscript.cpp file to the scripts CMakeLists.txt: under: set(scripts_STAT_SRCS add: Custom/myscript.cpp
7 - Redefine the virtual functions you want to override in your script.
8 - If the script you are writing is database bound, add the scriptname to the appropriate location in the database.
9 - Recompile and restart the server, and your script should be up and running.
doc/Items.txt
+149
View File
@@ -0,0 +1,149 @@
Syntax:
.add id quantity bonusid
.add id quantity bonusid1;bonusid2 (Don't do like more than 4, you might crash)
1
Heroic
Changes appearance to: 1
2
Pristine Crafting Material
44
Warforged
448
Warforged
449
Heroic
Changes appearance to: 1
450
Mythic
Changes appearance to: 3
451
Raid Finder
Changes appearance to: 4
498
Cooking Ingredient
499
Warforged
524
Heroic
Changes appearance to: 1
525
Stage 1 of 6
Changes appearance to: 6
526
Stage 2 of 6
Changes appearance to: 7
527
Stage 3 of 6
Changes appearance to: 8
546
Warforged
547
Warforged
558
Stage 2 of 6
Changes appearance to: 7
559
Stage 3 of 6
Changes appearance to: 8
560
Warforged
561
Warforged
562
Warforged
566
Heroic
Changes appearance to: 1
567
Mythic
Changes appearance to: 3
569
Mythic
570
Heroic
571
Warforged
593
Stage 4 of 6
Changes appearance to: 8
594
Stage 4 of 6
Changes appearance to: 8
602
Timewalker
615
Timewarped
617
Stage 5 of 6
Changes appearance to: 8
618
Stage 6 of 6
Changes appearance to: 8
619
Stage 5 of 6
Changes appearance to: 8
620
Stage 6 of 6
Changes appearance to: 8
642
Mythic
Changes appearance to: 3
644
Warforged
645
Timewarped Warforged
646
Warforged
648
Empowered
652
Baleful
653
Baleful
656
Warforged
692
Timewarped
doc/LoggingHOWTO.txt
+227
View File
@@ -0,0 +1,227 @@
Logging system "log4j-like"
--- LOGGERS AND APPENDERS ---
Logging system has two components: loggers and appenders. These types of
components enable users to log messages according to message type and level and
control at runtime where they are reported.
LOGGERS
The first and foremost advantage of this system resided in the ability to
disable certain log statements while allowing others to print unhindered.
This capability assumes that the loggers are categorized according to some
developer-chosen criteria.
Loggers are named entitites. Logger names are case-sensitive and they follow
the hierarchical naming rule:
A Logger is said to be an ancestor of another logger if its name followed
by a dot is a prefix of the descendant logger name. A logger is salid to be
a parent of a child logger if there are no ancestors between itself and the
descendant logger.
For example, the logger named "entities.player" is a parent of the logger named
"entities.player.character". Similarly, "entities" is a parent of "entities.player"
and an ancestor of "entities.player.character".
Loggers may be assigned levels. The set of possible levels are TRACE, DEBUG,
INFO, WARN, ERROR AND FATAL, or be disabled using level DISABLED.
By definition the printing method determines the level of a logging request.
For example, TC_LOG_INFO(...) is a logging request of level INFO.
A logging request is said to be enabled if its level is higher than or equal to
the level of its logger. Otherwise, the request is said to be disabled. A logger
without an assigned level will inherit one from the hierarchy
Example
Logger Name Assigned Level Inherited Level
root Proot Proot
server None Proot
As "server" is not defined, it uses the root logger and it's log level.
TRACE < DEBUG < INFO < WARN < ERROR < FATAL.
APPENDERS
The ability to selectively enable of dissable logging request based on their
loggers is only part of the picture. This system allows logging requests to
print to multiple destinations. An output destination is called an appender.
Current system defines appenders for Console, files and Database, but can be
easily extended to remote socket server, NT event loggers, syslog daemons or
any other system.
More than one appender can be attached to one logger. Each enabled logging
request for a given logger will be forwarded to all the appenders in that
logger
CONFIGURATION
System will read all config elements with prefix "Logger." and "Appender."
and configure the logging system. If "root" can not be properly configured the core
will remove all loggers and appenders and create a default set:
- Logger "root" with log level Error
- Logger "server" with log level Info
- Appender "Console" to log to console
Appender config line follows the format:
Type,LogLevel,Flags,optional1,optional2
Its a list of elements separated by comma where each element has its own meaning
Type: Type of the appender
1 - (Console)
2 - (File)
3 - (DB)
LogLevel: Log level
0 - (Disabled)
1 - (Trace)
2 - (Debug)
3 - (Info)
4 - (Warn)
5 - (Error)
6 - (Fatal)
Flags: Define some extra modifications to do to logging message
1 - Prefix Timestamp to the text
2 - Prefix Log Level to the text
4 - Prefix Log Filter type to the text
8 - Append timestamp to the log file name. Format: YYYY-MM-DD_HH-MM-SS
(Only used with Type = 2)
16 - Make a backup of existing file before overwrite
(Only used with Mode = w)
Depending on the type, elements optional1 and optional2 will take different
Colors (read as optional1 if Type = Console)
Format: "fatal error warn info debug trace"
0 - BLACK
1 - RED
2 - GREEN
3 - BROWN
4 - BLUE
5 - MAGENTA
6 - CYAN
7 - GREY
8 - YELLOW
9 - LRED
10 - LGREEN
11 - LBLUE
12 - LMAGENTA
13 - LCYAN
14 - WHITE
Example: "13 11 9 5 3 1"
File: Name of the file (read as optional1 if Type = File)
Allows to use one "%u" to create dynamic files
Mode: Mode to open the file (read as optional2 if Type = File)
a - (Append)
w - (Overwrite)
Example:
Appender.Console1=1,2,6
Creates new appender to log to console any message with log level DEBUG
or higher and prefixes log type and level to the message.
Appender.Console2=1,5,1,13 11 9 5 3 1
Creates new appender to log to console any message with log level ERROR
or higher and prefixes timestamp to the message using colored text.
Appender.File=2,2,7,Auth.log,w
Creates new appender to log to file "Auth.log" any message with log level
DEBUG or higher and prefixes timestamp, type and level to message
In the example, having two different loggers to log to console is perfectly
legal but redundant.
Once we have the list of loggers to read, system will try to configure a new
logger from its config line. Logger config line follows the format:
LogLevel,AppenderList
Its a list of elements separated by comma where each element has its own meaning
LogLevel
0 - (Disabled)
1 - (Trace)
2 - (Debug)
3 - (Info)
4 - (Warn)
5 - (Error)
6 - (Fatal)
AppenderList: List of appenders linked to logger
(Using spaces as separator).
--- EXAMPLES ---
EXAMPLE 1
Log errors to console and a file called server.log that only contain
logs for this server run. File should prefix timestamp, type and log level to
the messages. Console should prefix type and log level.
Appender.Console=1,5,6
Appender.Server=2,5,7,Server.log,w
Logger.root=5,Console Server
Lets trace how system will log two different messages:
1) TC_LOG_ERROR(LOG_FILTER_GUILD, "Guild 1 created");
System will try to find logger of type GUILD, as no logger is configured
for GUILD it will use Root logger. As message Log Level is equal or higher
than the Log level of logger the message is sent to the Appenders
configured in the Logger. "Console" and "Server".
Console will write: "ERROR [GUILD ] Guild 1 created"
Server will write to file "2012-08-15 ERROR [GUILD ] Guild 1 created"
2) TC_LOG_INFO(LOG_FILTER_CHARACTER, "Player Name Logged in");
System will try to find logger of type CHARACTER, as no logger is
configured for CHARACTER it will use Root logger. As message Log Level is
not equal or higher than the Log level of logger the message its discarted.
EXAMPLE 2
Same example that above, but now i want to see all messages of level INFO on
file and server file should add timestamp on creation.
Appender.Console=1,5,6
Appender.Server=2,4,15,Server.log
Logger.root=4,Console Server
Lets trace how system will log two different messages:
1) TC_LOG_ERROR(LOG_FILTER_GUILD, "Guild 1 created");
Performs exactly as example 1.
2) TC_LOG_INFO(LOG_FILTER_CHARACTER, "Player Name Logged in");
System will try to find logger of type CHARACTER, as no logger is
configured for CHARACTER it will use Root logger. As message Log Level is
equal or higher than the Log level of logger the message is sent to the
Appenders configured in the Logger. "Console" and "Server".
Console will discard msg as Log Level is not higher or equal to this
appender
Server will write to file
"2012-08-15 INFO [CHARACTER ] Player Name Logged in"
EXAMPLE 3
As a dev, i may be interested in logging just a particular part of the core
while i'm trying to fix something. So... i want to debug GUILDS to maximum
and also some CHARACTER events to some point. Also im checking some Waypoints
so i want SQLDEV to be logged to file without prefixes. All other messages
should only be logged to console, GUILD to TRACE and CHARACTER to INFO
Appender.Console=1,1
Appender.SQLDev=2,2,0,SQLDev.log
Logger.guild=1,Console
Logger.entities.player.character=3,Console
Logger.sql.dev=3,SQLDev
With this config, any message logger with a Log type different to GUILD,
CHARACTER or SQLDEV will be ignored, as we didn't define a logger Root and
system created a default Root disabled. Appender Console, log level should be
defined to allow all possible messages of its loggers, in this case GUILD uses
TRACE (1), so Appender should allow it. Logger Characters will limit it's own
messages to INFO (3)
doc/UnixInstall.txt
+59
View File
@@ -0,0 +1,59 @@
= TrinityCore -- Linux installation =
Copyright (C) 2008-2018 TrinityCore (https://www.trinitycore.org/)
=========================================================
WARNING: THIS DOCUMENTATION IS NOT ALWAYS UP TO DATE.
FOR MORE UP-TO-DATE INFORMATION, CHECK THE TRINITY WIKI.
=========================================================
CHECK https://www.trinitycore.info/ FOR FURTHER HELP
These are instructions for installation in a Linux environment, if you are
using Windows refer to https://www.trinitycore.info/
Installing TrinityCore is fairly simple on a Linux machine, assuming you
have all required applications
https://www.trinitycore.info/display/tc/Requirements
Most of these are included on common Linux distros, others you may have
to install by your self. Please check your distro's repos.
Make a directory to build in, you can call it anything you want like
build or bin etc, then go into the directory and cmake and make. E.G.
you created a dir named build ad want to have your finalcompiled product
installed in /home/trinity/server, an example sequence of commands can
be :
cmake ../ -DCMAKE_INSTALL_PREFIX=/home/trinity/server -DTOOLS=1 -DWITH_WARNINGS=1
make
make install
Thats just about all thats needed. You can however tweak more settings
than where to install using flags built into our cmake files. Just open
up CMakeLists.txt in the main folder and take a look at some of the
flags like
SERVERS Build worldserver and bnetserver
SCRIPTS Build core with scripts included
TOOLS Build map/mmaps/vmap extraction/assembler tools
USE_SCRIPTPCH Use precompiled headers when compiling scripts
USE_COREPCH Use precompiled headers when compiling servers
WITH_WARNINGS Show all warnings during compile
WITH_COREDEBUG Include additional debug-code in core
CMAKE_INSTALL_PREFIX Set installation directory
NOJEM Do not build with jemalloc (advanced users only)
CONF_DIR Set path as default configuration directory
LIBSDIR Set path as default library directory
CMAKE_C_FLAGS Set C_FLAGS for compile (advanced users only)
CMAKE_CXX_FLAGS Set CXX_FLAGS for compile (advanced users only)
CMAKE_BUILD_TYPE Set buildtype - the supported modes are :
Release, MinSizeRel, RelWithDebInfo, Debug
Of course, replace the paths in CMAKE_INSTALL_PREFIX with the
directory you wish to install TrinityCore to. The datadir is where maps,
DBCs, and SQLs are stored. The sysconfdir is where configuration files are stored.
Once TrinityCore is installed you will need to apply database updates
where necessary. Furthermore, you must configure your installation by
editing the config files in the sysconfdir.