VladimirMangos

it already exist.

Ntsc, i agree. This not done only by single reason: when i add original patch then prefer not change existed functionality not explcitly related to localization code work. Just good rule: chnage one thing by step. This also affect scripting code and then also batter do independnet. But i agree that need do at some time.

Patch added in to [6810]. Thank you.

I think this is not support thread. Ppl, do you understand what meaning unsupported Closed.

I only want say: make pull for selection development way is nonsense

Instead store realm level info in common for all realms realmd DB better add new table in characters DB and access similar character_tutorial that also per account per realm data. Possible in like case common GM level in realmd set _max_ possible gm level for account and per-realm setting set real gm level in specific realm. In like case will be possible check second data only if first (global GM level > 0) and then avoid slowdown for normal player login. In anycase this seldom used feature and then for including to mangos it don't must slowdown server work if not used for most oftent cases. At this moment i not comment is this part good for

You can do anything but i think UDB team will recreate forum and continue work.

And Brian isn't all UDB team, and in fact not UDB team member last time.

New genrevison output required data (date+time+git_hash) for compare. For DB project you in fact not require know revison, you need know last mangos sql update intergated to DB. For this DB creators must only write this sql update name in version. SD2 use same genrevison generator and you can compare date+time for example.

It's not support. Period.

DB/scriptlib version strings output added in 113f4f2f9f15e5d4679f9215e1dc306f71688e99 old versions script library will not load until implement this feature support.

I just point to simple thing: if some feature exist not meaning that it must used in strange ways.

Tag each commit? You free do it by self

DB version possible output. For script DLL need some changes...

Mangos development fully dependent from client changes in fact. So most stable point is just before client switch, and most unstable after client switch. This set single proper time for any release. Any new features strongly connected to new client and can''t be backported to like stable release branch. Can be backposted only very local typos fixes. So we have current way to development.

Maybe you use wrong address (need git://github.com/mangos/mangos.git ) maybe some other.I not have any problems with conection to github.com This is just not true. And you _know_ that this not true.

Not sure. And best for waiting part of community attempt understand work with git instead waiting...

In 4144246d8c8a267020bb5a248f63bb0c8a9c9cf2 git support added for revison (date+hash in git case) Svn revison generation also still work if you download sources from svn.

http://github.com/mangos/mangos/commits/master

09:08:27 MaNGOS/0.12.0-SVN (2008-10-22 23:08:34 Revision 9d1ac13) (Win32,little-endian) m-daemon) As you see forum soft stop make from short hash link to commit page. So better use full hash and this let have nice link after paste logs to forum post. For find commit can be used data+time in 99.999% case infact. Only very small time ranged commits need hash start for find proper. Also i plan as suggest Wik3d make shift-link in chat ".server info" output from hash. Then it can be shift-copy to open chat line and then selected and copy to clipboard from it. And used for search commit or paste in forum thread/etc.

I currently test gensvnrevision modification that undersatand git case. I don't known what version better 1) with added repo URL svn git 2) more near to old format svn git generator use git for version creation if have .git directory and use svn case if have .svn. [added] as i see forum understand git hash and make from it URL. So maybe (2) better and more short

It not used currently.

Yes, must be fixed in http://github.com/mangos/mangos/commit/679a1a921de472158851b70684932ced20dca19c

In http://github.com/mangos/mangos/commit/95612a0e0593d3ee51e8bd6f1d44daf8a7091980 Thank you

I am sceptic In fact we will have 2 choice as i think a) private development: Why mangos not support X, when mangos will support X, mangos die it still not support X, b) public: mangos crash it 10 sec, mangos crash client, i lost all characters at server, mangos is garbage nothing work, "you use unfinished version" why i use non finished version??? I use lastest! And my client auto-upgraded itself to X and work only with it version. I think (a) harm public project view less