Jump to content

Mangos 0.14, Milestone Completed


Guest VladimirMangos
 Share

Recommended Posts

MaNGOS is an object-oriented Massively Multiplayer Online Role-Playing Game Server (MMORPGS). It's an educational project, to help developers get familar with large scale C++ development projects.

The 0.14 release based on GIT commit [8587] is the fourteenth release on the MaNGOS roadmap. As a source-only release, it is intended only for developers and advanced users who understand they will probably experience bugs and/or rough edges.

The following list only gives you a higher level overview, for further details see the ChangeLog file included in the source releases.

==== Game Features ====

* Added: Support for 'on demand' regeneration of power instead fixed tick mode.

* Added: Allow NPCs to apply taunt.

* Added: Update killing quest objectives base at creature_template KillCredit fields.

* Added: Implement support `spell_proc_item_enchant` table for ppm item enchantments triggering at hit.

* Added: Implement new arena rating-system for season 6.

* Added: Allow save and restore at login forms/stances.

* Added: Implement far sight like spells work for long distance.

* Added: Implement proper storage and use of character specific account data.

* Added: Implement battleground bonusweekends call to arms.

* Added: Implement DB-based store battleground/arena gameobjects/creatures and related event spawn/despawn requirement.

* Improved: Fixes and optimizations in spell cooldown code.

* Improved: Fixes and improvements in EventAI code let better EventAI creature scripting.

* Improved: Fixes in combat log packets let show more correct info.

* Improved: More achievements types support implemented.

* Improved: Fixed well known walk-after-taxi bug.

* Improved: More improvements in mind control code.

* Improved: More improvements in gameobjects spawn/despawn work dependent from gameobject template data.

* Improved: Changed formula used for calculation creature damage base at attackpower.

* Improved: Propertly storing/restoring BG entry point including mount/taxi state

* Improved: More correct work timed quests, other quest code improvements.

* Improved: Implement more strict checks for fake messages in chat.

* plus lots of fixes for auras, effects, spells, talents, and more.

==== Server Features ====

* Added: Implement support spell casting precasts and aura boost casts for simplify and support related spell cast dependencies.

* Added: Implement possibility to reset client cache data from server side.

* Added: Implement --enable-builtin-ace option for explicit select builtin/system ACE in Unix/Linux build.

* Added: Implement check DBs versions (required_* fields) at mangosd/realmd loading.

* Improved: More checks at server startup for DB content.

* Improved: Some fields moved from `data` field of characters table to own fields. More planned move to final get rid from `data` field.

* Improved: Finish switch to uint32 spell ids use in code.

* Improved: Optimizations in map loading and broadcasting. New cell search algorithm implemented.

* Improved: Fixed memory leaks (mostly at server shutdown) and code cleanups.

* Improved: Use exceptions instead of explicit size checking for each packet, added checks for full read received packets.

* Improved: Optimizations for different guild data loading and use.

* Improved: Fixed redundant calculation of v and s on every login.

* Improved: Fixed race conditions in LockedQueue.

* Improved: Fixed long existed bug with vmaps unloading.

==== Statistics ====

* Fixed Bugs: 60 tickets and many bugs reported at forum resolved

* Total number of changes: 600 revisions (635 commits)

MaNGOS team not plan create special branch for 0.14 release. Tag will created release commit from other side.

We plan continue provide limited support for existed mangos-0.12 branch with appropriate patches backporting from master.

Link to comment
Share on other sites

Congrats :) So if i got it right, the 0.14 release will be rev 8587 so someone who wants to use that, should get that revision and not checkout master.

In the future, when additional fixes get in the 0.14 release, how will we check it out then?

Link to comment
Share on other sites

Congrats :) So if i got it right, the 0.14 release will be rev 8587 so someone who wants to use that, should get that revision and not checkout master.

In the future, when additional fixes get in the 0.14 release, how will we check it out then?

there won't be additional fixes 'getting into 0.14'.

the only thing what i'm wondering: will you create a tag for it, as you did it for 0.13 too?

Link to comment
Share on other sites

MaNGOS team not plan create special branch for 0.14 release. Tag will created release commit from other side.

Here I am.

As usual, annotated tag object d7237e4 called v0.14 created, pointing to commit object f5025e3 ([8587] MaNGOS 0.14 release.).

$ git tag -ln
v0.12           MaNGOS 0.12
v0.13           MaNGOS 0.13 -- moving from client 3.0.9
v0.13-dev1      MaNGOS 0.13 dev1 -- moving from client 3.0.3
v0.13-dev2      MaNGOS 0.13 dev2 -- moving from client 3.0.8a
v0.14           MaNGOS 0.14 -- moving from client 3.1.3

Link to comment
Share on other sites

 Share

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use