Trinity want a really clean & blizzlike code (which is a good thing), there is two consequences of this requirement :
- Trinity Code is cleaner everyday and have more and more 100% blizzlike methods
- It take a long time to implement any new functionality because it often require a lot of modifications to be blizzlike & clean enough for TC
Ashamane, on the other hand, prefer content over blizzlikeness, there is two consequences :
- Ashamane is dirtier than TC code, and some developper may be horrified by some pretty bad code part (Hello @Riztazz :D)
- There is more content on Ashamane (just read the readme) and pull request are often accepted or refused in a matter of days, not weeks or months. (That's what HannibalRoG was speaking about when he said "arrangement")
Does that mean any approach is better than the other ? No. It depend of what you want, and it's up to you to make your choice.
HannibalRoG already showed you the difference between TC and Ashamane when it come to spells (btw Soul Shards are functional @Ibeatdungeon, just check spell_warlock), he also could have talk about world quests, class hall, personal spawns, ...
About the Database, i don't remember where we got Cataclysm spawn, but me and my gigs of sniffs can assure you all spawns since MoP were done by us and us only. Of course over time we took data from other sources, but that's a small part. Again, the database has a lot more errors than TDB due to quickness of sniffs adding and will require a lot if cleaning.
This being said, i repeat that there is no need to confront both projects, Ashamane IS trinity, just with more patches, and as stated before, we will continue to fully support TC with pull requests when we estimate our code respect TC standards, like i already did with AreaTriggers, Scenes, Conversations, Creature Scaling System, QuestScript, PlayerChoice, ...
