In this update1
Full notes
Full Gloria Victis: Medieval MMORPG update
Read the full published notes in a cleaner layout. The original post stays linked below.
Repeated intro
Greetings, Warriors!
What changed
- Gameplay
- Performance
- Maps
- Balance
Gloria Victis: Medieval MMORPG changes
This week, we are happy to introduce a significant change in one of the core PVP systems in the game. Sieges and battles for locations are the meat and potatoes of Gloria Victis and we all know how much fun and adrenaline they can bring. We are removing some negative aspects of certain possibilities related to Sieges in today's patch based on your feedback from an ingame questionnaire, so we hope you will be delighted to read the details of the new system below.
Additionally, we managed to continue our work on players' proxy optimization and from now on, servers' performance should be much better, especially in bigger fights. This is not the end of this task, and our programmers are constantly finding space for improvements on that matter, so you can expect further iterations of optimization changes in the following weeks.
Last but not least and as always, we are addressing some of your reports and feedback, introducing some Quality of Life improvements and fixes.
Check the details below!
The screenshot’s authors have been awarded. SHVAGIER, SODANK, Hawk, and Salty – check your Ambers!
Changelog v.0.9.9.3.5 Beta
Nation locations sieges changes
In order to improve the overall sieging experience, we are introducing a new mechanic for nation castles. We observed players' behavior regarding map movement, sieges tactics, and outcomes of performed actions. It became obvious that there are some aspects of the old system that could bring negative emotions, drag players from the actual gameplay, and be abused to bully other nations by, for example, keeping the location under constant siege status.
After asking you directly about possible solutions via ingame questionnaire, we received very positive feedback, where 79.7% of you voted "Rather Agree" or "Definitely Agree" to the question “Should capturing at least one small flag be required to begin a siege?”
This new system should make it impossible to mislead the defenders by keeping the location in a constant siege state, which was making it impossible to rebuild walls and other defenses, and in the long run, was quite overwhelming to deal with.
Our designers were searching for solutions to mentioned problems for quite some time, as it was crucial for us to deliver the least impactful and at the same time well-targeted change to limit only the actions that were causing trouble. The change aims to filter out enemies driving around the flags, with no intention of attacking, from those who actually want to attack. The entire iteration in general is designed to protect against trolls pulling the entire army out of the castle and escaping without the possibility of PvP.
From now on, to start a siege on the main location flag, it is required to capture at least one of the minor flags of this location.
Additionally, to counter lone raiders capturing the flags and running away to avoid combat, from now on, we'll dismount the horse to the stables while entering the bastion. Thus, it will be possible to protect yourself much more efficiently, and it will be easier to catch the player who is occupying the minor flag because he will have to recall his horse again to escape. Additionally, for further balance improvements, when the possibility to call the mount directly on spawn is being turned off, players who will decide to defend the flag and spawn on it, will receive a one minute buff allowing them to call out their mount outside of Bastion in 5 seconds, instead of 15 like before.
Source
Changelog.gg summarizes and formats this update. How we read updates.
