Jump to content
TrinityCore

Rochet2

Members
  • Content Count

    959
  • Joined

  • Last visited

  • Days Won

    81

Rochet2 last won the day on December 2 2020

Rochet2 had the most liked content!

Community Reputation

208 Excellent

2 Followers

About Rochet2

  • Rank
    Snail
  • Birthday 10/26/1993

Contact Methods

  • Website URL
    http://rochet2.github.io/
  • Skype
    Rochet22

Profile Information

  • Gender
    Male
  • Location
    Finland

Recent Profile Visitors

8328 profile views
  1. Reminds me of this one quote from subv I keep seeing at times. : )
  2. Take a look at https://en.wikipedia.org/wiki/Precompiled_header PCH is a way to speed up compiling.
  3. It would be best to avoid SQL queries if you can. However as you asked for an example of how to make this query, here is one: #include "DatabaseEnv.h" int64 count = CharacterDatabase.PQuery("SELECT COUNT(*) FROM characters_spells WHERE guid = %u", player->GetGUID().GetCounter())->Fetch()[0].GetInt64(); if (count >= 30) { } In this code - the include allows you to use CharacterDatabase variable, which is a global variable. - PQuery makes a database query and allows you to use printf like syntax to format variables into the SQL. - GetCounter returns the part of the gu
  4. @Verytas Starting over with the source code that matches your client version (7.x) should fix the most imminent issues you have. (follow what I said before) TrinityCore seems to be in the middle of transitioning to 8.x. Guides have not been updated yet and without external tools you cannot use 8.x client yet with TC, so I would not personally recommend trying to use the latest master branch or 8.x clients yet.
  5. @Verytas Seems you are trying to use latest master branch with 7.x client. However master = 8.0.1.28153. For 7.3.5 you probably want to go back to the commit that supported that version. For example: git checkout -b 7.3.5 7.3.5/26972 See https://github.com/TrinityCore/TrinityCore/tags and https://git-scm.com/book/en/v2/Git-Basics-Tagging
  6. To print information about closest gameobject you can use .gobject target The information should contain the gameobject's guid. Then you can delete the object by its guid with .gobject delete <guid>
  7. At least I cannot see an edit button on the main page. Other pages seem editable. Main page: Any other page:
  8. The database links are also broken. https://trinitycore.atlassian.net/wiki/spaces/tc/overview?mode=global world database characters database auth database
  9. Hmm, on forum main page right side there is the same topics section twice https://community.trinitycore.org/
  10. Links on the main page of the wiki are also broken in same way: https://trinitycore.atlassian.net/wiki/spaces/tc/overview?mode=global "Description of TrinityCore DBC files contents" "How to add a custom script to your solution" "IRC: #Trinity @ irc.rizon.net (Rules)"
  11. mysql 8 not supported yet: https://github.com/TrinityCore/TrinityCore/issues/22188#issuecomment-407205183 https://trinitycore.atlassian.net/wiki/spaces/tc/pages/10977296/Windows+Requirements
  12. Hmm, why did you add that? I don't think I suggested such at least. The commit/changes I referenced had no mention of such code. https://github.com/TrinityCore/TrinityCore/commit/5734643cecbadfffb7ee1b66c9665d57108923f6#diff-82d123ab4d0745ba8103dc4b10c23d9f If you have 0 experience, maybe trying out the latest version of TC is easier. And if you are already are using the latest version, then you have probably mismatching dependencies or you installed only boost source without the precompiled binaries or similar - for that you should post information about your installation lik
  13. No. You should cherry-pick the commit I referenced. It should fix your problem with boost (clear cmake cache and retry configure after you cherry picked). Though I guess also using older versions would get rid of the error since it is caused by newer versions, but .. is using old stuff really the solution?
  14. With the boost you have you should be using win64. There was some problems with the new boost versions and the cmake script a while back. Maybe the 6.x core you have has the old cmake script that cannot handle the .1 in the folder name. For this reason I think I temporarily copied my lib64-msvc-14.1 folder and named it lib64-msvc-14.0. But instead of that maybe its better to check if your core has the needed boost cmake changes: https://github.com/TrinityCore/TrinityCore/commit/5734643cecbadfffb7ee1b66c9665d57108923f6#diff-82d123ab4d0745ba8103dc4b10c23d9f .. and now right
  15. Which compiler did you choose in cmake? Did you choose Win64? or the one without it?
×
×
  • Create New...