Agenda

• Database migration and webIg server change
• Feedbacks on the Patch: Kitinlair occupations, Boss refactoring, Marauder gameplay
• Recrutement: Event team, Support Team, Translation team

Je vais refaire un point sur la migration et le patch qu'il y a eu.
Nous avions prévu de migrer le très vieux serveur web qui contenait le webig et des outils de nevrax vers un nouveau serveur tout frais.
Afin de minimiser les problèmes, il était convenu de ne migrer que la base de données (étape 1), mettre à jour le serveur vers une version ubuntu encore en LTS (16.04) au minimum (etape 2).
Puis sur le serveur me.ryzom.com y faire une copie des apps et les tests en php 7 (etape 3).
Enfin quand tout serait ok, on basculerait app.ryzom.com sur me.ryzom.com (etape 4).
Puis finalement un nouveau serveur viendrai ajouter la réplication au cas où il soit nécessaire de basculer des services (etape 5).
Bon ... Tout ça c'était sans prévoir que le serveur web allait nous lâcher.
Ce qui nous a obligé à finalement faire les étapes 1 à 5 en 24h.
Donc, compte rendu des opérations :
Tous nos serveurs sont actuellement en Ubuntu 20.04.
Le vieux serveur web va nous quitter (mais personne ne va le pleurer ...).
Nous avons les principales applications qui fonctionnent sans erreurs majeures (pas mal de warning que nous corrigerons au fur et a mesure).
Mais globalement, c'est une très bonne chose de faite et il n'est plus prévu de grosses migrations.
Les prochaines mise à jour se feront pendant un redémarrage sur le serveur Atys afin de ne plus bloquer le jeu.
Donc pour la migration, nous sommes pas mal.
S'il y a des questions à ce sujet, n'hésitez pas.

Si pas d'autres questions on peut passer au patch.
Il reste pour le moment un souci à corriger concernant les métiers de la kinitière qui sont buggés.
Ce sera fait prochainement, mais nous ne savons pas s'il est necessaire de faire un patch + reboot du serveur ou pas.
On vous tiendra au courant.
Boss refactoring a été corrigé lors de son lancement et pour le moment tourne normalement.
Si tout se passe bien, au prochain redémarrage/patch nous appliquerons le système à tout Atys.

Si pas d'autres questions, openssl ?
Je sais que tout le monde attend ce sujet avec impatience.
Donc, pour faire simple, nos clients ne sont plus compatibles avec une modification des certificats de let's encrypt.
Qui reste l'une des autorités majeurs pour ce qui est de fournir des certificats ssl.
À comprendre : c'est grâce à eux qu'on sécurise nos sites en https.
Et du coup, les clients ne sont plus capables d'accéder aux sites https qui ont un certificat let's encrypt (ce qui est le cas pour nos serveurs).
il existe une configuration qui permet de conserver une compatibilité avec les clients utilisant openssl 1.0 (donc la vieille version).
C'est ce que nous avons fait en attendant de mettre à jour les clients.
Actuellement nous testons les clients Windows 64 bits et Linux 64 bitss avec openssl 3.0 et pas de soucis majeurs.
Nous appliquerons la même modification aux versions Steam et a Macos.
Si vous hébergez des appps webig qui ne sont plus accéssible depuis le jeu, vous pouvez venir me voir et je vous aiderai a configurer votre serveur pour activer la compatibilité (c'est une option certbot).
Mais nous pensons pouvoir fournir les nouvelles versions assez rapidement
Enfin, c'est encore en discussion mais nous nous demandons si nous allons continuer à maintenir des versions 32 bits sous linux (et Windows).
Il reste vraiment très très peu de monde sur des configuration 32 bits.

Agenda[list]

• Current projects
  • Pen-and-paper role-playing game in Ryzom universe
  • OP refactoring
• Recrutement: Event team, Support Team, Translation team

For some time we have been working on a role-playing game in the Ryzom universe. The goal is to be able to play outside the New Lands, either on the Old Lands, now or before the Swarmings, or in other more remote places. Places that will never be in the MMO, for example places where resurrection does not exist.
There is a playable first draft, and I need testers, initially one or two teams of four people. People to play and point out what works well and give suggestions for improvement. For the moment, the working version is in French, and my level in other languages means that I can only have people playing in French. But if a game master wants to get involved, we can also set up tests in other languages.

The outpost refactoring project is Dev's current #1 priority.
Now that GvE tests are finished, we are preparing the next tests on Atys, which will involve GvG. Like GvE tests, these ones will be performed on special outposts.
Ulukyn (Dev) will come to present this GvG part in detail during the next Ryzom Forge meeting on Monday, December 6th.

Support Team

The Support team continues its recruitment campaign for volunteers.
We need you, your availability, your technical and gameplay knowledges of the game but also your diplomacy, to expand our ranks and best meet the expectations of players.
To learn more, please consult this post: https://app.ryzom.com/app_forum/index.php?page=topic/view/22047/2 #2 .
To apply, contact Tamarea exclusively at tamarea@ryzom.com, and do not tell anyone about your application!

Event Team
We're looking for volunteers who want to help write event scripts, or who want to become actors by playing a character in the events we play.
Training is provided, and the entry into acting is done very gradually to give the recruit time to get used to it.
Join us to benefit from this unique experience!
To apply, contact Tamarea exclusively at tamarea@ryzom.com and do not tell anyone about your application!

Translation Team
We are looking for volunteers to translate in-game texts and official announcements into English, German, Spanish, Russian, French, as well as to proofread texts in these five languages.
To apply, contact Tamarea exclusively at tamarea@ryzom.com.

That was the last topic for today!
If you'd like to contact Drumel about tabletop roleplaying, you can do so on chat.ryzom, or reply to the meeting minutes on the forum when they're posted.
The next meeting will be held on Monday, December 6th!
The two main topics will be Bugs and testing, and Outpost redesign.

Agenda

• Update on recent crashes
• Feedback on the Client's beta tests
• Feedback on Boss refactoring
• Progress on OP refactoring (GvG)

Let's talk a little about the recent server problems, there have been several.
The first problem, the most critical, was quite particular and could crash any Ryzom service. Indeed, a Ryzom server is composed of many services which manage an aspect of the game: the EGS which manages the entities (NPC, creatures, actions, etc...), the IOS manages texts and chats and other smaller services but whose role is also important. Now, the bug could occur in one of these services and up to 2-3 times a day, which depending on the service that crashed could cause chain reactions (and therefore a server that crashes completely). The reason of the crash is a bit technical (I could give more details if needed) but a fix was applied and since then none of the services crashed because of this bug.
Another bug has finally been fixed. This is one of the oldest known bugs in the game. We suspected that it came from the missions and we had a hunch that it only happened with characters returning to the game after a long absence. We were able to investigate this bug because we unintentionally caused it by moving occupations into Kitins' Lair. This maneuver, in fact, unknowingly caused the aliases (identification numbers saved in the character's file kept by the server) of the missions concerned to change. Now, if a mission changes aliases and a player has kept the old alias in the character's save file on his own machine, the server will crash as soon as the character in question is loaded. This is because aliases were not originally designed to be changeable... no one anticipated that some missions would be moved from one continent to another. Finally, this diagnosis made it easier to find and fix the bug and the unfortunate player who was crashing the server every time he tried to log was finally able to join Atys without a hitch.
A third bug has been identified in the IOS, which occurs quite rarely. We made the hypothesis that it occurred when a message was sent by the server on a dynamic chat channel, at the same time as one of the players disconnected and added several checks to avoid this conjunction. For the moment, no new crashes have been reported. We keep an eye on it though.
Finally, the last bugs (which cause slowdowns and huge delays in sending messages) occur when the SU crashes (SU = Shard Unifier, a service especially useful when several servers are running - like Aniro, Arispotle and Leanon - or when Ring sessions are active). We have already fixed one of them, the fixing of another is in progress. We will strengthen the part of SU code that handles database writing.
That's it for the information about the recent crashes. Are there any questions?

See forum.
We need as much feedback as possible, because the timing of the next patch depends on it: the sooner we validate the beta client, the sooner we will patch the new features.
So, are there people who have been able to play with the beta client regularly?

See forum.
What are your feedbacks, especially about the new algorithm of spawn of Bosses?
We would like, indeed, to know if its activation in all regions of Atys is now possible or if it still needs some adjustments.

The project is pretty well advanced.
We are running the last alpha tests and the tests on the test servers (Yubo & Gingo) should start soon. At the moment they are focusing on new GvG outposts in zones 50 and will allow us to determine if the NPC setting is good (it is at its minimum, but fighting a guild and NPCs simultaneously can be a bit of a challenge).
During this GvG test, we will move forward with the rest of the project. Some of the changes that are already ready, such as reducing the duration of battles to 1 hour and lowering the cost of attacks, could be implemented quickly. The rotation of materials and the taking of outposts by hostile NPC tribes would then come in a later phase of project development.
We agreed to give the project a boost over the next two months.