Jump to content
TrinityCore

Shauren

Developers
  • Content Count

    422
  • Joined

  • Last visited

  • Days Won

    74

Shauren last won the day on March 20

Shauren had the most liked content!

Community Reputation

168 Excellent

About Shauren

  • Rank
    Better than everyone else
  • Birthday 10/01/1991

Profile Information

  • Gender
    Male
  • Location
    EIP

Recent Profile Visitors

10658 profile views
  1. No, you cannot. Master branch is on latest 8.3.0 version
  2. Just download the client from battle.net app, even a trial (or "starter" as they call it now) is enough
  3. This table exists only to send sniffed hotfixes for db2 files that are not loaded by TC. You should never try to manually insert data into it. If you really must know - blob is simply the entire db2 row written as binary
  4. No, I don't really care about mac clients, the current 8.2.5.32750 build being allowed for mac clients on TC is actually an exception, not a norm, it is the first one since 7.3.5
  5. If you don't have a launcher then no, you need to use windows client
  6. It sounds like you connect both worldservers into the same character database, you need to separate them and share only auth (and world if you dont want to customize anything for only one realm)
  7. You need to use folder name (case sensitive) and version from .toc, timestamp is for cache, just set it to current time
  8. Install MySQL 5.7, thats all you must do
  9. You don't need the client at all after extraction (but you will need it again if there are fixes/changes done to extractors, to extract again), you can also delete Buildings
  10. Ignore startup errors Allied races are not implemented
  11. Repacks are not supported. Currently supported version is 8.2.0.31478 and you need to download new version of arctium launcher
  12. You should either use SOAP from your website to connect to running worldserver and send .accont set password comand (preferred) or just clear s and v fields from auth.account (this method might go away in undetermined future)
  13. This isnt a supported scenario, bnetserver has three separate build ranges that are incompatible with each other due to changes in client 6.0 to 6.2.3 6.2.4 to 7.2.5 7.3 to now
×
×
  • Create New...