swubu

What about making 2 Github trinity repo's 1 Public ( Public share ) = ( trinity) core & data ( auth /characters/world ) sync ... so users/ testers/... would not have the problems like , core is up to date wile data is not or visa versa. 1 Devo private (shared under the Devo's ) = ( trinity) core & data ( auth /characters/world ) is the same way its now "Feq update's that only dev can inject ( slight updates ). spams like , " hey i have a problem i followed the wiki but it seems my core is not sync" or errors like unknow colum permission " and lots of other problems because core data Non sync . save's some time and explanation btw Thnx for the WIKI's , 3.3.5 go's flawless..... 4.3.4 non sync situations i think i need to fix it with hash <--- grts