Famine

not sure why, maybe I am missing something, but it is only grabbing the avi files. no mpq's are parsed from the links.

Did this ever come to fruition? Looking to start playing around with the zero branch and if it hasn't may be able to help out with that.

The way I always understood it though was the DBC info is backup data, the primary scale is set first by the server (in the database), if it doesn't find it, then it looks in the DBC files.

This is typically stored in Database not dbc files. see mangos.creature_template tables under "Scale" column. must restart server to see diff... maybe even delete cache.

What you don't seem to understand is that "I can has server now?!?" and I meanz RITE NAO!!!... Just sayin. This stuff all works magically and needs to just see client version on the server side and everything automagically works!!! (I really feel I should put sarcasm tags around that for clarity... but I think it went understood.) The mod of the client is (at least here) a NO NO! So if it's a no no here, then you can't develop based on the mod of the client. It's what's referred to as a catch 22. You need the client modded to make it easier to develop, but legally you can't do it without bringing heat down on the project (loose translation). Honestly I have no idea how the dev's walk the thin line to begin with. It truly is impressive.

Yea, no I appreciate the power of the tool, and I am attempting to learn all the ins and outs of it. I really am not trying to avoid it, just attempting to understand the logic. Right, you may have said it a little better than I did, but this is exactly where I started as well. See... now that is how I understood the commits when I was browsing through the code. (btw I am using git reset as opposed to creating a new local branch... This may be part of my problem.) This is the problem right here... In an attempt to avoid having any part of the DB ahead of the core I am trying to fit 10#'s of crap in a 5# bag. Pushing the core to anything [10550] or above forces me to update the db. I realize that doesn't sound like a big deal, but in 4 months when I finally get around to updating my db I have the feeling im going to forget that a portion of the db is ahead. It avoids headaches. Just so I can say I partially understand, Long story short, If I want to create a version of MaNGOS with this or any other project, find their commits ahead of the revision I am interested in. If I want to start combining projects, if there isn't a commit that is on the same version across the board I am going to come into issues. And lesson is to stay up to date on the commits because it's easier to create a patch against the head revision than it is with something earlier. Thanks for your time and effort blueboy, that took a while to get out i'm sure.

Alright, I am really sorry but I have to resort to asking. This may not be all that complex, and it may just boil down to me not understanding git and the way it works. I am far more familiar with svn and cvs. I haven't been around for a while, and things have changed in the overall project but info should translate I'm sure. What I am used to being able to do is this: 1: go to DB forum and find the most recent release. This gives me a MaNGOS version to work towards building. side note: I have been able to successfully reset my local version to match this version and build it successfully with SD2 2: download mangos source and build 3: go home, be happy. the problem I am running into is when I try to add in support for playerbot... no other core mod tried, so I assume I would have difficulty with any of them. Am I right in understanding that when looking at the git commits in the blueboy branch I am seeing clean mangos commits AND commits of playerbot code? for example: on 2010-09-26 there is commit in history 750c4f7. This is build number 10545 which matches my db version. This commit does not include (from what I can tell, correct me if i'm wrong) support for playerbot. I need to create a patch to get this commit to support the bots. The patch is where I am running into issues. What I have been trying to do is create a patch from 5c1fe508 to the 10545 revision. I am able to build fine after applying what I think is the patch I created using gitk, but I am getting errors on server start after building that I have the wrong version of DB. Any help is appreciated.

I'm not entirely sure what all the complaints are about to be completely honest. The system isn't that hard. I think most of the issues are going to arise in the attempts to organize all the different pieces to the puzzle since there is no such thing as a revision number now... It appears we are going with a date/counter system. Consider me voting for the rest... someone make a GUI that would show a log of revisions and allow someone to update or download the full package just by clicking on that revision. The problem is that unless it is explicitly stated in the information about the revision, it is tough to look through the website to look for SQL updates. Many users wait for official DB support before they update their cores.