-
Posts
470 -
Joined
-
Last visited
-
Days Won
84
Posts posted by Shauren
-
-
No? We don't support 1.0 AT ALL, 1.1.1 is the minumum requirement and you can just use 3.0 (it works too)
-
Time is critical? How about no, it is not. Things will be working for 10.0.2 when it hits live realms, not any sooner
-
Our dependency versions are set to whatever ships in current stable debian release, not centos
- 1
-
-
When using openssl 3 you must also copy "legacy.dll" from openssl installation directory in addition to libcrypto-3-x64.dll and libssl-3-x64.dll
-
Thats normal, just ignore them
- 1
-
If you were trying to recreate the database from scratch then you also need to drop views and functions, not just old tables
-
All you had to do was edit the config DBC.Locale from 0 to 4
-
You use the mapextractor that was compiled from master branch obviously
-
It is definitely still there in git history, you just need to find the correct commit or tag - however there is no guarantee that you will be able to compile it with latest compiler/dependency versions
- 1
-
Make sure you are using the arctium launcher to start the game
-
use item id, not name
-
Quests cannot do that. It is world.gossip_menu_option BoxCoded column (and you have to write a script that implements this function https://github.com/TrinityCore/TrinityCore/blob/3.3.5/src/server/game/AI/CreatureAI.h#L207)
- 1
-
You mean the tag? You clearly did not build the extractor from that tag. WDC3 was introduced much later
- 1
-
You cannot use current version extractors with older client version. You must use the version that existed when your desired client version was current
-
To get older versions, you need to checkout one of the tags in repository (we have one, "7.3.5/26972") but I will make no guarantees that you will be able to compile it without issues
-
After you build vmaps by running vmap4assembler, you can delete Buildings directory, everything else is required
-
In that file you only need to allow '1SLC' (or was it 'CLS1'?) where it currently checks for 'WDC3'
But the structures I was talking about was this file https://github.com/TrinityCore/TrinityCore/blob/f759809d9d4364bc1d988e4390d3d5a33d5469e9/src/tools/extractor_common/ExtractorDB2LoadInfo.h
-
master branch extractor will get you closer but it will not work without any modifications to the code (you will need to update db2 reader to support classic format)
-
This is because mysql stores table and column names as lowercase on windows (accountid, securitylevel) but on linux they are case sensitive (AccountID, SecurityLevel)
Make sure that your exported windows database file has correct names in them (use mysqldump, not any other 3rd party export tool)
-
You cannot select it manually, it will happen automatically, depending on dungeon/raid difficulty (only works inside instances)
- 1
-
shared auth db - yes
shared authserver - no
-
This spell is intended to do 200% of targets health in damage, what you need to do is use conditions table to prevent it from being used on anything other than its intended quest target
-
But that builld DOES have a git tag... https://github.com/TrinityCore/TrinityCore/tree/8.3.7/35662
link issue : mariadb need openssl 3.0, trinitycore require openssl 1.0 , how can i separate provide it ?
in Help and Support
Posted
Thats where you are mistaken, RC4 was not deleted even in openssl 3.0