killradio_1337

Hey guys. ACHIEVEMENT_CRITERIA_DATA_TYPE_S_AREA (type = 6) was removed from 4.x and 6.x branches long time ago, but still there are some data with this type in DB. Is this entries can be safely removed from DB, or ACHIEVEMENT_CRITERIA_DATA_TYPE_S_AREA waiting for implementation? Same question for ACHIEVEMENT_CRITERIA_DATA_TYPE_MAP_DIFFICULTY (type = 12) in 4.x branch - this criteria type already implemented and working as intended? Asking, cuz can't find proper commits with some more explanation.

Already found solution, forgot to override EnterEvadeMode (thought I did it) >_< Btw, ainame replaced by scriptedai, since Im already used npc_escortAI to handle this actions.

Hi everyone. Trying to make some custom quests and faced weird problem: I need to make creature attackable for other NPCs, but still pacified (not aggroing/attacking other mobs). Already tried many cases with unit_flags and react states, but creature keeps going into attack<->evade mode during moving. Can some one provide simple example or mb NPC which has waypoint + moving + can be target for attack + doesnt attack anyone in combat state?

Problem: Could not find a proper repository signature (hash) - you may need to pull tags with git fetch -t Continuing anyway - note that the versionstring will be set to "unknown 1970-01-01 00:00:00 (Archived)" How to repeat: Make TC's repo clone, push some commits to your new repo and merge with TC's one. Solution: Go to https://github.com/TrinityCore/TrinityCore/releases/tag/init Find "init" named tag and its hash (9b1c0e006f20091f28f3f468cfcab1feb51286bd) Go with git into your cloned repo and type: git tag -a init 9b1c0e006f20091f28f3f468cfcab1feb51286bd git push --tagsYou can also check if everything ok with this command: git describe --match init --dirty=+ --abbrev=12Output should be like init-<counter>-<short-hash> For ex.: init-22656-g15a9c6729ee2

ulimit + sysctl + google = profit.. But these ones handle only most common bottlenecks of highload systems. If u dont know how to manage linux servers and asking such questions - its better to hire someone with enough skill.

For those who want to have quick start with GIT: GitHub Cheat Sheet All the hidden and not hidden features of Git and GitHub. This cheat sheet was inspired by Zach Holman's Git and GitHub Secrets talk at Aloha Ruby Conference 2012 (slides) and his More Git and GitHub Secrets talk at WDCNZ 2013 (slides). Link: https://github.com/tiimgreen/github-cheat-sheet

Rly interesting thing from Peter Cottle for those who wants to know more about GIT branchin: http://pcottle.github.com/learnGitBranching/ Supported commands: commit branch checkout cherry-pick reset revert rebase merge

Learn git in 15 minutes rly simple and easy way to learn git, just try out yourself! A bit more online guides and how-tos: http://rogerdudler.github.com/git-guide/ http://githowto.com/making_changes

git revert <hash> example: git revert ca9918e

Use patch command under linux/win and find blocks in ur code (with npp or other editor): <<<<<<< HEAD uiDeathArmyCheckTimer = 0; bDeathArmyDone = true; ======= if (uiDeathArmyCheckTimer <= uiDiff) { me->ClearUnitState(UNIT_STATE_ROOT | UNIT_STATE_STUNNED); uiDeathArmyCheckTimer = 0; bDeathArmyDone = true; } else uiDeathArmyCheckTimer -= uiDiff; >>>>>>> 84268be882e79ee7633323502ce83f2e4bfcf3a9 all between <<<<<<< HEAD and ======= - is what u have now in code, between ======= and >>>>>>> [hash] - what u want to have, after apply patch or smth. Check logic, functions, variables, etc and try to fix ur code. There is no step-by-step guide "how to fix conflicts after applyin patch".

http://support.microsoft.com/kb/867466/en -> try method 1/2.

OMG u cant just drop this table - all items will disappear from ur characters inventory. -- Add new column to item_instance table ALTER TABLE `item_instance` ADD COLUMN `itemEntry` mediumint(8) unsigned NOT NULL DEFAULT '0' AFTER `guid`; -- Set values for new column from corresponding columns in other tables UPDATE item_instance ii, auctionhouse ah SET ii.itemEntry = ah.item_template WHERE ii.guid = ah.itemguid; UPDATE item_instance ii, character_inventory ci SET ii.itemEntry = ci.item_template WHERE ii.guid = ci.item; UPDATE item_instance ii, guild_bank_item gbi SET ii.itemEntry = gbi.item_entry WHERE ii.guid = gbi.item_guid; UPDATE item_instance ii, mail_items mi SET ii.itemEntry = mi.item_template WHERE ii.guid = mi.item_guid; U missed 10654_characters_item_instance.sql update.

Try to install MySQL 5.1.x (Win64) and recompile with it. Btw what openssl arch u using? win64?

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 =]