Jump to content
TrinityCore

Thulium

Members
  • Content count

    31
  • Joined

  • Last visited

  • Days Won

    3

Thulium last won the day on January 12

Thulium had the most liked content!

Community Reputation

12 Good

About Thulium

  • Rank
    Advanced Member
  1. How to install using pre-compiled packages

    Hello folks! Today I finished upgrading my buildserver to Debian 9 'Stretch', and the packages will now be compiled to that version of Debian. Please note that older versions of Debian -will- break- as they no longer satisfy the requirements. You should be able to upgrade your system from Debian 8 to 9 and the new version of the packages will automatically work :-) Cheers!
  2. How to install using pre-compiled packages

    Hi blackcat, The software itself will run on Ubuntu just fine, as long as you are providing it with enough resources. However, the packages are made for Debian 8 (will upgrade to 9 soon). You are free to try and install the packages on your Ubuntu server, however, some package names for the dependencies might not match. And then the package manager (dpkg) will be unable to install the software. You could do one of 2 things: - Run a debian based server - Manually unpack the deb files and move the files to the correct folder (and script that) Regarding the 7.2.5 server, I do make packages for the 'master' branch for trinitycore, but I don't run a master branch server and those packages might contain incomplete configuration. However, feel free to try them and let me know what to include :-) Cheers
  3. I might be late to the party, but when you are running the extractor tools, can you open 'top' in a different terminal window? It sounds like you either have severe I/O Wait times, or your system is busy with other stuff. I've ran the extractors on a virtual machine (on a server that's hosting 20 other VMs on a single i5 cpu) and it took a few hours, but nothing exciting.
  4. How to install using pre-compiled packages

    Hi moonwhaler, Thanks for the feedback! :-) As for bots, I fear that there isn't a viable project at the moment that implements player bots. I have tried merging a few codebases a few years ago, if I got it working, it was very laggy and heavily taxing my server. And sadly, most of the projects that implement a form of bots in TrinityCore are dead, or almost dead. As the code is no longer compatible with the server. What -could- be an option, but I don't know how well they are developed, take a spare PC, run some copies of WoW on it in low graphics mode and use an actual bot to co ntrol them. But I don't know if they are any bots that can do anything more then 'just farming'. You might also need to disable Warden if you use modified WoW clients. Cheers!
  5. Location of Databases (Character DB)

    My guess would be that it's all gone or corrupted, you could give yourself a 'safeguard' by giving the databases a version in the name, e.g.: - characters-335 - characters-master etc.. That's what I did with the packages I've made :-)
  6. Location of Databases (Character DB)

    If you check your DB server, there should be 3 databases that contain TC data: - auth: useraccounts and server connection profiles (realms) - characters: what it says on the tin - world: what it says on the tin The first 2 databases contain 'unique' information in the sense that it's unique to your server, it contains everything people did on your server. The world database is the only one that you can ignore for backup purposes, as it can be reconstructed.
  7. Server runs only @localhost

    This looks like a repost of the topic below with a different repack.. Same advice as before, compile it yourself if you want support on these forums. Or check the appveyor links in this topic:
  8. Strange parse error

    Hi Pallam, It's better to report this to the issue tracker on Github: https://github.com/TrinityCore/TrinityCore/issues That's where most of the dev's are :-)
  9. I beg to differ, the reason the libraries tend to run out of sync is because the OS keeps itself updated and (as much as possible) security hole free. A better practice would be to have a 'staging/test' server which you run with the SAME version of the codebase as you have on your 'live' server. On that server you run the following 3 steps on a daily basis: - Stop MySQL/TC servers - Update OS packages - Restart MySQL/TC servers If you then run into this issue do the following: - Recompile TC on your 'test/staging' server - Test it - Update OS packages on 'live' server - Update TC on 'live server' And if you can't/don't want to do that, you can install the packages I've mentioned in my previous post, as they are compiled on a kept-current installation of Debian 8 Jessie.
  10. How to install using pre-compiled packages

    Hi all! I've created a script that will generate a data package for your server and added the instructions on how to use it in the post. I've just added it to my build environment, so it will be ready for use tomorrow! Cheers!
  11. Hi ruben381, First of all, make sure that you have your distribution fully updated. Normally the distribution maintainer keeps development packages (you'll need for building software) in sync with the binary packages containing the software. E.g. on Debian: apt-get update apt-get dist-upgrade apt-get autoremove apt-get clean This will update/upgrade all packages in your installation to the latest version available. After you've done that, make sure you install all the development packages required to compile TC. All of them are named in the Wiki, you can recognize them by the '-dev' suffix. Then follow the instructions to compile the server, perform all other setup tasks and you should be good to go. Shameless plug: Alternatively, install the packages I've built for Debian, they work with the current stable version of Debian:
  12. @Lorac: I can comment on the RAM usage on Linux systems. I'm currently testing a script to generate the maps and package them in a nice little zip file for me. I'm running the extraction tools on a LXC container with 2 GBs of RAM and 2 cores. Works like a charm! :-) @Flavia: If you really have difficulties compiling the server, you can always try reading: The main topic is Debian packaged versions, but Nay linked pre-built Windows binaries.
  13. How to install using pre-compiled packages

    That was my bad, I changed the text to reflect the correct name, but the actual link was pointing at the internal hostname. I fixed the link, try again :-)
  14. How to install using pre-compiled packages

    Hmm... Weird, check http://repo.element-networks.nl/trinitycore-recipes.tgz
  15. How to install using pre-compiled packages

    I took a look, but I take it you would like to have the original uncompiled git source in those packages? My current setup doesn't really allow for this. It does the following: - Maintain a local copy of the repo (the 'meta' script that builds trinitycore runs 'git pull' before compiling) - Build the software according to the build recipe I defined - Package the software according to the package recipe - Push the resulting package to the repo This allows me to save a lot of disk space (I only have 1 copy of the source per branch), and it *should* be possible to redo any older builds by checking out that version in git. I'm using a script a colleague made, I will link it in the post once he posted in on Github (it's on his todo-list). So that part of this setup I cannot share, as it is not my work. However, I'm cool with sharing the recipes I made for the build script (see attachment). But I do ask that if you make improvements/changes to let me know. So I can incorporate them in the scripts I use. I also just updated the build script to look for the correct version of the TDB when the source files mention it ;-) trinitycore-recipes.tgz
×