Jump to content


Popular Content

Showing content with the highest reputation since 12/27/10 in all areas

  1. 53 points
    Two new full world database has been upload to Github Releases. TDB 735.00 (2018/02/19) was released for the master branch (previous release TDB 720.00 from 2017/04/18). TDB 335.64 (2018/02/19) was released for the 3.3.5 branch (previous release TDB 335.63 from 2017/04/18). Notes: If you are installing a new DB you only need the 2 full SQLs plus any file at /sql/updates/world/ and sql/updates/hotfixes/ on Trinitycore repository. On 3.3.5: single full SQL file plus any file at /sql/updates/world/
  2. 25 points
    I guess I can speak for all TrinityCore team about this. We, and surely you people, noticed that there are people always asking the same questions... They are either too lazy to search the forum, don't know how to use it, or lastly... they don't want to search. So, before you ask a question, search on the forum for an answer. If you don't find it, search again. If you still can't find it... search again! (i know... I'm repeating myself!) And then if you don't find it, open a new thread. So, when you open a thread, remember... post a proper topic title (I will start to close all threads with topic titles like "help me" or "server help", etc...), if you are too lazy to use a proper topic title, I will be too lazy to answer to your questions. After that, in the problem description, explain what is happening, and how it should happen. Give us the most info you can... You can even copy/paste those question's and answer them on your topic: - What is your O.S. version? - What is your core version? (There is no "last version", on somedays we can do more than 1 commit, so post your correct core version) - Where did you grab it? - Did you compiled yourself? - Do you have all dependency's correctly installed? - What are their versions? (Same as the core, each linux flavour (by example) has his owns versions. So even if you are on windows, tell us the versions) - Did you Follow our wiki? - Did you correctly updated the databases? - What is your MySQL Server version? (There is no "latest version") - What is your MySQL Client Version? (There is no "latest version", and i mean the library's) - Is your MySQL correctly configured and running? - What is your MySQL client? (SQLyog? MySQL command line? etc.. NOTE: please, don't use navicat) - Did you opened the necessary ports? - Do you have any custom patches in the core? Which ones? Did you try without them? - What is your wow client version? Did you extracted the necessary files from it? And lastly... Post your conf files and realmd table in necessary cases. Note: If many of you start answering those questions when you find a problem, in most of cases, you'll find the answer by yourselves and spare us wasting time answering the same questions. And also, you won't find us to critics or narcizists. Note2: I will start to change the Warning level acording to the number of rules you guy's break. Seem that way you'll think twice!
  3. 20 points
    Since TrinityCore moved to git, I think this commands will be useful for all users. If you have some interesting commands, tricks or solutions for non-standard tasks - please, share. Download sources: git clone git://github.com/TrinityCore/TrinityCore.gitDownload sources in custom folder: git clone git://github.com/TrinityCore/TrinityCore.git <folder_name>Update sources for up-to-date version: git pull origin masterShow all branches (local + remote): git branch -aDownload sources from specific branch: git clone git://github.com/TrinityCore/TrinityCore.git git checkout -b <branch> origin/<remote_branch>Create new branch: git branch <branch>Show current branch: git branchSwitch branch: git checkout <branch>Show modifications - usually used when you commit something to your repo: git statusShow differences between two branches: git diff <branch_1>..<branch_2> git diff master..<branch> git diff <branch> (diff with master)Create patch from modified sources: git diff > <patch_name>.patchCreate patch from different branches: git diff master <branch> -p > <patch_name>.patch git diff master <branch> > <patch_name>.patchCreate patch from different commits: git diff <commit_hash_1> <commit_hash_2> > <patch_name>.patch git diff 719ffeb414c97e09469b 52cd2cbd7eb62648ae13 > <patch_name>.patchApply patch to sources: git apply < <patch_name>.patchApply patch to sources with creating of new files: patch -p1 < <patch_name>.patchRevert applied patch: patch -p1 -R < <patch_name>.patchAdd all modifications to sources: git add *Add single modifications to sources: git add <file_name>Create commit: git commit -a -m "<description>"Create commit with author: git commit --author="name <[email protected]>" -m "<description>"Show log changes: git log git log --format=onelineAdvanced log view: git log --oneline --author/commiter=<author> git log --since/after/before/until=<date> git log --pretty=format:<string> git log --summary git log --stat git log --helpRevert all changes in source code: git reset --hardRemove all except original source files: git clean -f -x -dSwitch to master branch: git checkout masterDelete specific branch: git branch <branch> -DDownload specific revision of sources (for example 10 revisions below): git clone git://github.com/TrinityCore/TrinityCore.git cd ./TrinityCore git checkout master git reset HEAD~10Switch to specific revision 1. Find commit's hash for specific revision: git log --grep=Core/DBLayer2. Find needed commit's hash. Like this one: ... commit 70a45be1594c43e09f7103c910f11a0476f88b52 ...3. Revert to specific revision with creation of new branch "DBLayer": git checkout -b DBLayer 70a45be1594c43e09f7103c910f11a0476f88b52Undo last push to your remote repository: git push -f origin HEAD^:masteror git rebase -i origin/<branch>~1 git rebase --abort git push origin +<branch> vim -> delete everything and type: noopGet all commits from specific one like patch files: git format-patch --full-index 52499b03ea8c86ab536c2025c3629b8883f591f2Get cherry-pick patch from remote repository: git log --reverse --pretty=tformat:'git cherry-pick %h # %s' | grep "\[patch"Merge remote branch to your repository: git clone [email protected]:<username>/TrinityCore.git <folder_name> cd ./<folder_name> git remote add -f -t master -m master upstream <remote_repository> git merge upstream/masterDownload remote fork to local repository: git remote add upstream git://github.com/<username>/TrinityCore.git git fetch upstream git checkout -b <branch> upstream/<remote_branch> git pull upstream <remote_branch> Credits goes to ru-mangos community, google and github help topics =]
  4. 13 points
    Requirements: Msysgit can either by acquired directly from git for windows or using the "SetupComplete" package from GitExtensions. Msysgit version required: 1.7+ Minimum required TC rev: b2404c1a26d9 (10997) Setup options: During the setup wizard you will encounter the following screen: Make sure your git executable is added to the PATH variable by choosing one of the green marked options. Fixes "Missing or outdated git - did you forget to install a recent version?"
  5. 9 points
    Core : Source Repo : https://github.com/T...ore/TrinityCore Git Pull : https://github.com/T...TrinityCore.git Database : Full DBs : https://github.com/TrinityCore/TrinityCore/releases Source Repo: same as core Issue Tracker : https://github.com/TrinityCore/TrinityCore/issues Wiki / How-tos : http://www.trinitycore.info IRC: Network : irc.rizon.net General/Support channel : #trinity IRC Clients: Windows users: http://www.mirc.com IceChat http://www.icechat.net/ *nix users: (use one of the following) emerge irssi apt-get install irssi yum install irssi pacman -S irssi pkg_add -r irssi Any operating system: webchat (online IRC client) Twitter : http://twitter.com/TrinityMMo
  6. 7 points
    I see that the number of pinned posts in the 'Help and Support' section is getting large. My original thought was to try to move some of the "How To" posts to the wiki but I can't create new pages. So I figured I'd suggest instead that all posts that are guides or "How To" posts be moved to a subsection of "Help and Support" called "Guides". I know it may seem like more micromanagement for your mods but having a separate guides forum would: Allow the "How To" posts to be easily browsed (especially when they become "unpinned") Free up the pinned list for its original intended purpose: important notices Prevent the first page of "Help and Support" from being nothing but pinned posts Encourage more people to write guides (maybe) Anyway, just a thought after the success of the "solved" section which seems to have cut down on duplicate questions. Edit: I see you could actually free up pinned slots in several forums that have guides in them. In fact some guides I didn't even know whe had
  7. 6 points
    How to Setup Debugging & Enable 'edit And Continue' in Visual Studio aka: How to Setup Debugging & Enable 'edit And Continue' in Visual Studio 2008 Update 2014-9-27: Updated the guide to remove ace.dll requirement due to BOOST support added in rev 3ba49277d NOTICE: For now you need to disable linker option /SAFESEH or it will ignore the /EDITANDCONTINUE option that gets set when you change the PDB type. To do this: Make sure you are on DEBUG configuration Right click on a project (eg: authserver) and select Properties Expand the Linker category Click on Advanced Scroll down to Image Has Safe Exception Handlers Set it to NO Click Apply Repeat for all other projects in the solution. If a project doesn't have a Linker category, skip it Update History: Some people have reported that this does not work for 64 bit applications. I struggled with this for a bit and now that I figured it out, I thought I'd pass it along The Guide: Before you start, compile the solution in Debug mode at least once to get 'ace.dll' and then copy all the following (required) DLLs to any folder, you will point Visual Studio to this later: ace.dll - Not required for sources after rev 3ba49277d due to BOOST support libeay32.dll libmysql.dll ssleay32.dll * Note: 32-bit names listed, 64-bit names will most likely be different (you should know what to look for) Step 1: Seting up the projects Step 2: Setting up the debug executable info Step 3: Enable 'edit and continue' (and other 'Debugging' menu settings) That's it. Now when you choose 'Debug -> Start Debugging (F5)', Visual Studio will launch both the authserver and worldserver and when you break execution and make changes, the 'apply code changes' will be available allowing you to 'edit and continue' instead of having to stop and recompile. Note: There are some cases you can't use 'edit and continue' Supported Code Changes Precompiled Header Limitations For more information, see here Edit and Continue (Visual C++) Some people have reported that this does not work for 64 bit applications.
  8. 5 points
    This tutorial aims to simplify the compilation of TrinityCore on Mac OS X by using Homebrew, the missing package manager for OS X, to install TrinityCore dependencies, in order to keep things simple. 1) Install Homebrew For those who don't have Homebrew installed, you can easily install it typing: ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" 2) Install Xcode and Command Line Tools Install XCode using the App Store, then type: xcodeselect --install 3) Install dependencies brew update brew install mysql openssl readline cmake boost zlib brew link zlib --force 4) Getting sources Move to the folder where you want to place the TrinityCore sources, then type: git clone https://github.com/TrinityCore/TrinityCore.git cd TrinityCore If ( and ONLY if ) you want to compile 3.3.5 type: git checkout 3.3.5 Create build folder: mkdir build cd build 5) Generate the XCode project files IMPORTANT: replace /Users/username/tc-server of the following command with the path where you want to install the TrinityCore server. then type: cmake ../ -GXcode \ -DMYSQL_ADD_INCLUDE_PATH=/usr/local/include \ -DMYSQL_LIBRARY=/usr/local/mysql/lib/libmysqlclient_r.dylib \ -DREADLINE_INCLUDE_DIR=/usr/local/opt/readline/include \ -DREADLINE_LIBRARY=/usr/local/opt/readline/lib/libreadline.dylib \ -DBOOST_INCLUDEDIR=/usr/local/include \ -DBOOST_LIBRARYDIR=/usr/local/lib \ -DOPENSSL_INCLUDE_DIR=/usr/local/opt/openssl/include \ -DOPENSSL_SSL_LIBRARIES=/usr/local/opt/openssl/lib/libssl.dylib \ -DOPENSSL_CRYPTO_LIBRARIES=/usr/local/opt/openssl/lib/libcrypto.dylib \ -DZMQ_LIBRARY=/usr/local/opt/zeromq/lib/libzmq.dylib \ -DZMQ_INCLUDE_DIR=/usr/local/opt/zeromq/include \ -DZLIB_ROOT=/usr/local/Cellar/zlib/1.2.8 \ -DCMAKE_INSTALL_PREFIX=/Users/username/tc-server \ -DWITH_WARNINGS=1 6) Building the binaries Type the following to build the binaries: xcodebuild -target install -config Release I have tested this tutorial both for branch 3.3.5 and 6.x using a MacBook Pro Retina 15" running: - a fresh Mac OS X 10.9.5 (Mavericks) - a fresh Mac OS X 10.10.3 (Yosemite) - Mac OS X 10.11.3 (El Capitan) and it worked fine, give me your feedback.
  9. 5 points
    Hey all, I wanted to write down a guide about preparing your linux server to be able to work as a gdb log tracer + restarter I have been using it for around 2 years with no problem what-so-ever (other than the performance if having a compiled server with full debug flags on) What is GDB? GDB, the GNU Project debugger, allows you to see what is going on `inside' another program while it executes -- or what another program was doing at the moment it crashed. What is Restater? Restarter allows your core to crash, fall, get stuck and come back every time without anyone touching or doing anything manualy. For this guide you acknowledge that you have basic knowledge in operating linux systems and using ssh as a cli 1. First, lets make sure your Freeze Detector is set up corretly by editing the worldserver.conf file in `etc` Find MaxCoreStuckTime and set it to 120 ( MaxCoreStuckTime = 120 ) This will tell the server that if this demon is stuck for 2 minutes the core will crash automaticly leaving the restarter at work.. 2. Make sure you have sendmail installed sendmail is a cli program that allows sending emails without any pre-setup etc Try: /usr/sbin/sendmail -f [email protected] [email protected] or sendmail -f [email protected] [email protected] If you get an email from [email protected] this means it works, if you dont -> Follow the sendmail installation guide which i found very helpful 3. Go to your `bin` folder (where the worldserver bins are installed at) create a new file - for the perpuse of the test call it `commands` (nano commands) put the following code in the file: run -c ../etc/worldserver.conf bt bt full info thread thread apply all backtrace full quit Make sure that if you are using another path or other server config name, you have to alter it in the file. The rest, leave as is, its for the backtrace report to work. 4. Create crashes folder under bin mkdir Crashes the C is capsulated 5. creatre a new file, this file will be used as our restarter, mine is called gdbres.sh (nano gdbres.sh) In the file, put the following code: while : do gdb -x=commands -batch ./worldserver > temp tail -c 60000 temp | sed 1i"Subject: Crash Log" | /usr/sbin/sendmail -f [email protected] [email protected] tail -c 60000 temp | sed 1i"Subject: Crash Log" | /usr/sbin/sendmail -f [email protected] [email protected] mv temp Crashes/log$(date +\%Y-\%m-\%d-\%H-\%M-\%S).log done tail takes the last part of your `temp` file and sends it via mail, the -c 60000 chooses to take 60kb worth of text (which is the aprox gdb crash log filesize) and just send it trough sed li = the subject of that email the last command mv temp /Crashes/blabla moves the temp file to your crash log folder, if you dont have a crash folder it wont move the file and you wont have any log keepting so make sure you created the folder.. 6. Alter the files to be able to execute: chmod +x commands chmod +x gdbres.sh 7. Starting the restarter is an easy job, personaly i use screen if you are using screen do the following: screen -A -dmS world ./gdbres.sh This will start it in a new demon screen and you can forget about starting the core on your own for a while if you are using simple cli commands you can use ./gdbres.sh && to make it start and forget about it Notes: Turning the restarter off gave me lots of problems when i wanted to close it, I started using webmin to be able to close it via their "Running programs" Positive: To update core to tip etc, you can make install then just crash it. you dont have to fully shutdown the core only ctrl+c in the screen folder or shut it down via ingame and it will come back online using the restarter Sometimes the gdb log comes back bigger than 60k, you can always go back to the Crashes folder and take the full crash.. Its usualy not bigger trough To be able to debug your core with full debug flags you will have to use -DCMAKE_BUILD_TYPE=Debug to include additional debug-code in core in the cmake proccess as stated in the linux compile guide
  10. 5 points
    2014-01-24 Clarify the "before you start" section to account for clients copied to new machines Clarify how to check the Launcher version Clarify when to run backgrounddownloader.exe Fixed some typos, missed some typos and probably even made more typos Update history: I've put the guide in the spoiler below since it involves a LOT of downloading (approx. 20 to 25 GB), I thought I'd caution you first so you can decide if you want to find alternate means. Step 3: Install the patches IMPORTANT: I can't stress this enough NEVER run Launcher.exe IMPORTANT: I guess I have to remind people to block Blizzard's servers in their WTF too This set of instructions should work for all the patches you've downloaded regardless of what instructions they came with. Take a minute to read them before you start and keep them handy for reference. Patches uploaded by other people might be a bit confusing. Take a look at the "_instructions.txt" file in one of my patch archives for help. Before you start: If you have more than one installation make sure you run WoW.exe once to get the proper installation path in the registry or the patch might try to modify the wrong installation. If you've copied your wow client to a new computer, make sure you run WoW.exe once to get the proper installation path in the registry or the patch won't be able to find your installation Pre-Patching Make a backup of your 3.3.5a client Copy "base-Win" to the "Data" folder Edit realmlist.wtf change "realmlist" and "patchlist" to point anywhere but the official servers ( is a good choice for now) Edit or create launcher.wtf in the "WTF" folder Make sure the contents are the following: Note: Check this file after each patch, some patches may delete or change it. Replace it if they do Apply the patches in order * Note: If you have a Cata DVD then use that and skip wow-3.3.x-to- Extract the patch archive to a temporary folder Copy the patch contents to the appropriate folders in your WoW installation If the patch contains an EXE, copy everything to the "Updates" folder These (and only these) types of patches can be deleted when finished If the patch contains a "wow-patch.MPQ" and a bunch of MPQ files, copy "wow-patch.MPQ" to the WoW root (overwriting) and copy the other MPQs to their appropriate folders (usually same folder structure as the archive) If the patch contains a bunch of MPQ files without a "wow-patch.MPQ", put them in the appropriate folders (usually same folder structure as the archive) Important: If this type of patch does not contan a "wow-0-xxxxx-Win-final.MPQ" (where xxxxx matches the patch revision) then you will need to download the collection at the top of the guide and extract it. Place this in the "Updates" folder. Apply the patch See Notes section below if you get errors trying to apply the patch If the patch contained an EXE, run the EXE If the patch contained an update script (my uploads), run the script If you have the "wow-patch.MPQ", just run "Blizzard Updater.exe" If you have a file such as "wow-0-xxxxx-Win-final.MPQ" (where xxxxx matches the patch revision), run this from your WoW root: Run "BackgroundDownloader.exe" to see if there is additional patch info only after the following patches: wow- wow- wow- Make sure your tools are updated by checking "Launcher.exe" (right-click -> properties), the version should be Run the tools updater if it isn't (don't run the launcher) Copy the MFIL / TFIL from the collection you downloaded to the WoW root Overwrite any that came with the patches Run "backgrounddownloader.exe" The first two will download approx. 7 GB, the last approx. 4 GB When finished, run WoW.exe (not Launcher.exe) Follow the guide for setting up a server (make sure to compile the tools) Edit "realmlist.wtf" and point "realmlist" and "patchlist" to your server's IP Patch WoW.exe This is required or you won't be able to log out, every NPC will be "Unknown" plus a host of other problems Run WoW.exe (not Launcher.exe) Allow it to connect to Blizzard's servers to check for additional data Log in, create a character and enter the world If it is downloading, there will be an arrow over the system menu button. This uses a slow UDP pulse so it may take several days. Just leave the client running. The final client size after patching and optimizations performed when WoW.exe is first run is approx. 15.7 GB (confirmed by +CDawg who collaborated on the process) Notes: If at any time you have trouble installing a patch, you may need to do one or more of the following Copy "base-Win" to the "Data" folder (this file sometimes gets corrupt) and try repatching Update the tools (BackgroundDownloader, Blizzard Updater) Oh, did I mention: IMPORTANT: I can't stress this enough NEVER run Launcher.exe Oh, did I mention: IMPORTANT: I guess I have to remind people to block Blizzard's servers in their WTF too ---------------------------------- End of Guide ---------------------------------- Forum Mods: You can close the following threads since they will be obsolete http://www.trinityco...tion-available/ http://www.trinityco...2-10-23-334-pm/ http://www.trinityco...patches-where/
  11. 5 points
    TortoiseGIT guide moved back into its own topic for easier seaching / discussion until I can put it on the wiki. It shouldn't have been merged into the middle of a discussion about the commandline.
  12. 4 points
    Please read and understand the following : What we require when you file an issue : VERY IMPORTANT, WHY THERE IS NO LATEST: on github after 1 month we can't known the date the issue was posted, and because that we can't known the revision Never ever test things with GM accounts - Update your core before reporting a bug, the bug of ancient cores can be fixed on newer cores. - Add which revision of Trinitycore you're running on (this is the CORE revision, not your client version) - Add which database, and what revision, you run on. Remember, you can get the most updated TDB from Downloads · TrinityCore/TrinityCore · GitHub - Add a list of which modifications that has been done to the core (if any) if those modifications aren't public available you must share the code if you/we see that they can be reason of bug, if you don't use a clean core and you don't share the code if it afects the bug or the files of the bug (crash) the ticket will be closed. - Supply links, spell ids, full spell names, npc ids, npc guids, npc names, gameobject ids, gameobject names detailed, we don't must guess what mob/instance/spell you are talking about. addon to help you with ids: http://www.curse.com/addons/wow/spellid#t1:other-downloads get 3.3.5a version. Example CORE revision number : b1e2cdb905d6a92edeb505eff968d26c453b252b (LAST is not a valid number), there are 40 Time Zones from UTC−12 to UTC+14, we don't known on what Time Zone you live, for me Today is 31 of July, for someone on Honolulu it's 30 of July. Read Howto properly install git on Windows. - Help and Support - TrinityCore if you can't get something like TrinityCore Hash: c4818f189216+ (Win32, Release (little-endian)) (worldserver-daemon) when you use server info on console. Example DB revision number : TDB 335.51 The above is VERY important, so add this when reporting! Any ticket without this info will be closed without notice.
  13. 4 points
    Database install errors Please note that the software called Navicat is NOT supported due to issues with how it handles SQL-files with "/* */"-style comments. We advise all users to stay well clear of this program unless they really are looking for issues. TCE00001 My core don't starts i get: [1146] Table 'world.updates_include' doesn't exist Your database structure is not up to date. Please make sure you've executed all queries in the sql/updates folders. Maybe you are updating one very ancient core and missed some sql, easy way is drop all your trinitycore databases (auth, character, hotfixes, world) and leave core to import the databases if you don't care about data. Another way can be create temporally the needed databases and allow core to import the sql files, then export the updates and updates_include tables from those databases and import them to your production core (be sure you have updated your databases to max before import the updates tables to your production core). REMEMBER: core needs one user with create table/alter table/drop table permisions. TCE00002 My core don't starts i get: 2012-07-11 16:47:10 ERROR: DatabasePool world NOT opened. There were errors opening the MySQL connections. Check your SQLDriverLogFile for specific errors. 2012-07-11 16:47:10 ERROR: Cannot connect to world database;3306;trinity;trinity;world Unknown column 'level' in 'field list' 2012-07-03 23:01:12 ERROR: E:TrinitysrcserversharedDatabaseMySQLConnection.cpp:531 in MySQLConnection::_HandleMySQLErrno FATAL ERROR: Your database structure is not up to date. Please make sure you've executed all queries in the sql/updates folders. This means DB structure was changed, you need to apply the sql files found at sql/updates (this also can mean you have updated your db structure but you forgot to install the updated core) If you use the most updated master branch and you don't have custom things DROP your world database and get the most updated TDB from GET TDB then apply the sql files found at sql/updates. If you can't or you don't want to drop your world database or droping world database don't fixes your problem enable SQLDriverLogFile on your worldserver.conf file. If you get those errors whatever you are trying on world database, use http://www.trinitycore.org/f/topic/43-windowslinux-combine-sql-updates/ to create a 2 files instalation system to be sure you don't miss any sql file. Under Linux you can use rgrep <insert here the missing column name> sql/updates/*.sql to see what file you miss. Under Windows you can use notepad++ or ultraedit 32 to search the file you miss. Anyway if you have world db structure problems, we sugest you to DROP world db and leave core to import the files, because maybe you have missed some. TCE00003 My server don't starts, i get: >> Loaded 0 trinity strings. DB table `trinity_string` is empty. This is because you forgot to import world database or you have enabled autoupdater but missed to put world database on the worldserver directory or imported travis world database instead proper database. If you get "unknown column" or "unknown table" error it can be because 10 reasons: 1) You have cloned master repository (3.3.5a) and installed TDB, but you forgot to apply the files present on sql/updates/world you need to run those to properly start core. 2) You have updated your database, but you forgot to update your binary files, you usually can't run older cores with newer databases. 3) You have updated your core, but you forgot to update your database, you usually can't run older databases with newer cores. MOST COMMON CASE 4) You have download 4.3.4/6.x databases, but you cloned 3.3.5a repository you can't use 6.x/4.3.4 databases with 3.3.5a core. NOTICE use one very high range to avoid to get your spawns/scripts deleted when a new TDB is released unless you drop the full DB when updating. NOTICE2: if you don't drop your world database you will end with double spawns. 8) You are trying to use a custom patch and you forgot to apply the sql files for it or they don't exist. 9) You are trying to use one sql for another project or deprecated sql files. 10) You are trying to apply the same update 2 times.
  14. 3 points
    Very interesting video I've been looking at for the last 10 minutes, still a lot more to watch. Thx dfighter for sharing it "How to Protect Your Open Source Project From Poisonous People"
  15. 3 points
    I would like to request an archive of the Wiki for the tables related to 335 for those who wish to continue using / developing that branch. Once table structures change for 6.x, it will be difficult to maintain a 335 repo if the reference material is updated to the new structure without archiving the old structure. Thanks!
  16. 3 points
    as you might be able to see above there is a new custom search box on the forums, if you cant see it its because of your adblock, please consider removing our site from adblock as I promise we have no ads on the site, none, zero, zilch so you wont be bombarded by ads if you whitelist TC . this search box is a combination box that parses all of the TC sites / sections and gives a singular search location for everything at once. You get: the wiki the forums the sourcecode on github the issues on github pull requests on github doxygen docs irc logs from #trinity on rizon you can refine your search to specific sections using tabs at top of the results : the results are labeled and show full URL. search away and let me know how it goes for you it is being improved over time so there might be changes.
  17. 3 points
    Let's stick to the facts here. OP is oblivious on how to proceed in order to get his server working because he either a) doesn't understand a word of English and could not understand the error message in the console even if his life depended on it, or b.) is too ignorant or uninitiating to consult MySQL package instructions or google for upgrade directions. These possible causes may have deeper rooted issues such as clinical retardism, lazy parenting or, indeed, sir was an avid repack user in the past. Please convince me why the fuck we should judge and not deal with the facts at face value - ignorance is bliss. This is a learning project after all, and we should not deprive one of the chance of learning because of his alledged past. If you feel the need to bash someone, fine. But base your conclusions on facts for which you have probable cause, and keep your witchhunt theories to yourself. You know what's been here even before that? Cancer. I guess we should defend and worship cancer too. Paradox, you need to stop getting your panties up in a bunch. They're soaking wet from menstrual blood and they're leaving a rotten stench within the community.
  18. 3 points
    Pinned. I, for one, didn't like the merge, I think each guide must be in a separate topic as long as they cover separate aspects of a problem.
  19. 3 points
    should be fixed, confluence was going mental.
  20. 3 points
    Well there was the post where I directed some idiot running a public server to Paradox for information pn TC's dev support plan. np though. I'll catch the next idiot
  21. 3 points
    For a second there, I thought you were talking about rbac, and I got this hilarious picture in my head of a player that can move any direction but forward, because each direction has its own rbac permission, and his forward moving permission was revoked
  22. 3 points
    +delro +rkm +MrSmite testing testing a simple +username[/CODE] Caps DONT matter.
  23. 3 points
    A crash a day keeps the mem leak away. ™
  24. 3 points
    Ok, I expect you will be able to provide the build farm capable of fully testing TC on all supported host OSes, then? Windows, various Linux builds, and OSX would be great. Just post up here where the devs can remote into to test every build change first. Thanks for being such a supporter!
  25. 3 points
    Who ever this gregarious person is, I don't know what it is you think I have done to you, since you are too cowardly to confront me directly, but, stop negative repping me for no reason.
  • Newsletter

    Want to keep up to date with all our latest news and information?

    Sign Up