Development

14th of december 2015 

1 Security improvements
Now thanks to vl, https://secure.ryzom.com doesn't accept SSLv3 and TLSv1.0 anymore, it got a A+ grade on https://www.ssllabs.com/ssltest/analyze.html?d=secure.ryzom.com&a mp;hideResults=on

Ulukyn updated SSL certificate on RSYNC so Linux players are again able to create accounts.

Forums notifications shouldn't go in Spam folder anymore since VL fixed SPF records for ryzom.com.

2 Ryzom on Steam
Since there still remains lot of work to do on every aspect to improve the game before it goes on Steam, Tamarea has asked for a delay in the date of addition on Steam, and it has been accepted. New deadline is so end of March 2016, and not end of December 2016 anymore.

Kervala: For Steam, I'm currently adding a link "Game setup", which starts the totally new "configurator" (?) for all platforms. It's a RyzomCore member who did it. It works with Windows, OSX and Linux.

For now, I'm working on the patch system. I succeeded in generated the .packed_sheets and have the patch system work under Linux. I still have to test it. For now, there are only Windows 32 bits executables, but we plan to create a specific BNP file for the clients of each platform (win32, win64, linux32, linux64 and OSX).

Here is what I've done from the old TODO list:
- Compiling the Windows clients under Linux (automation process);
- Ending Ryzom Configuration/Set-tup (MFC and Qt5 versions);
- Regenerating .packed_sheets.

The patch system can't be used with the AppStore client because Apple forbids changes in the applications without their validation. There will be, instead, an OS X package to download to install the client without going through the AppStore and this one will have the patch system activated.

3 A launcher for Ryzom
Kervala: I thought about different patch problems under OS X, Linux and Windows, and I wonder if we shouldn't need a small launcher with buttons to launch Ryzom, launch Ryzom Configuration, etc... It could also setup alternative Ryzom clients like Yubo or if you want to launch several clients.

It will fix current problems that are :

- Ryzom must be run as an Admin under Windows, that's not a good thing for security. Applications like Chrome don't need that and they are patching themselves. They choose to install files in AppData so they don't need Admin permissions. The launcher will be installed in C:\Program Files and run as a normal user, it'll be able to download needed data and copy them in a writable directory.

- Under OS X, that's the same problem. Ryzom couldn't patch data if installed in /Applications because it needs root permissions. So the "launcher" could put data somewhere in "Application Support".

- Under Linux, again the same case. Packages are installed with root user and we can't overwrite these data. With a launcher, client will be able to update itself using IG patch system. RSYNC could be abandonned since all clients (excepted AppStore one) will be using IG patch system.

- Under Ubuntu, we'll only have to update Debian packages if the launcher must be updated and since it'll be compiled in static, it'll be the same under all Ubuntu versions.

Launcher will be able to create links in Start menus or on Desktop for all clients. You'll still be able to start Ryzom directly without launching the launcher. Launcher will be mainly used to download initial data at the first launch.

There will be a small package (less than 50 MB) for each launcher to download on SF (or other sites). The related executables will be bundled in the package, but all data will be downloaded from a common file.

To summarize, launcher goal is to :

- download initial data (several GB)
- install the right executables (client + configuration)
- create links to executables
- copy all files in a writable location- make copies of client with different configurations (different server, different account, etc...)
- launch configurator
- it'll used for Windows, Linux and OS X, but won't be used for Steam (Steam manages itself patching and is acting like a launcher) or AppStore (Apple doesn't authorize to patch files)

For the case where critical data are corrupted, we'll use the ryzom_client_patcher utility that is a command-line tool very similar to the old ryzom_recover but that uses the same files as IG patch. It doesn't require any external files unlike client.

4 Fix of pipeline to create a new zone
Kervala: I have a good news: Kaetemi just told me that it'll be easy to create new 3D zones (lands) or modify existing ones. He fixed all build pipeline. The huge problem was we couldn't change existing files/create new ones. Everything has been tested now and is working fine. At least Kaetemi tested them.

Q: It's in the context of the tools made by Kaetemi? Or it's just some preliminary change? We still need 3DSMax for now?
A: You'll have to ask Kaetemi when he comes back.

5 Addition ingame of the tryker cities banners
Cities banners are ready to be added ingame but we have to wait until we can patch big files. This will be possible soon, when we will have the new client (the one that will be used for Steam, also available without using Steam) and patch progress. 

6 Documentation on datasheets
YannK:  I'd just want to say that I've put the sbricks study on stand-by to concentrate on the .creature, since it will probably be used earlier with the tools which Kaetemi is creating. But there is an awful amount of options (as you can guess from the complexity of Ryzom AI). So if ever you need a specific creature type, don't hesitate to let me know for me to concentrate on these points.

Same, I'm considering creating datasheets types, without legacy, but which have all the needed elements for a .creature kind, but only when I've documented everything. So if you have needs before that, once again, don't hesitate to ask.

A precision, for the ones who don't know much about the engine, the .creature concern all the elements which are displayed and managed dynamically by the server, be them a pole, a decorative banner, a mob or a NPC, it's managed with a datasheet of .creature type (even some buildings sometime).

Well, for the ones who'd like to have a general view of the system, I've written this text on our site: https://khaganat.net/wikhan/fr:tag:informatique:ryzom_core:start. At the end, there's a link towards the datasheets area, but there are only .sitem for now. I'm publishing in blocks, when I've made a coherent whole from my notes. Next one will be about .creature.

Q: But there's no one who found Nevrax documentation on this?
A: Doesn't seem to.

Q: Where's the page about .sitem?A: [i]https://khaganat.net/wikhan/fr:rcdssitem

[/i]

11h of january 2016 

1 Latest fixes and improvements 
Here is the list of the last fixes and improvements sent by Kervala:
- Complete removal of the Yubo chat.
- Use of optimmised models for the boots when wearing a mage dress.
- Fix of the bug of the red underwears at launch.
- Checking the video memory and using the adequate textures cache.
- Compiling the crash-report, ryzom_configuration_qt and the ryzom_client_patcher for all clients.
- Fixing several textures and generating the textures with the new tools.
- Fixing the dead keys on Linux. 
- Synchronous/Assynchronous launch of an application on all platforms.
- Using whole screan instead of windows mode when launching Ryzom if the screen is already in 1024x768.
- Upading the LZMA/7z code.
- Adding the textures_optimizer tool to detect the textures which can be optimised and optimsing them if needed (useless alpha channel, grey shaded images recorded in colors, etc).
- In the occupations, fixing the bug on the degree icons.

Reminder: the whole list for fixing and improvements can be found there:  https://bitbucket.org/ryzom/ryzomcore/commits/all and the simplified one is here: http://ryzom.kervala.net/clients/ryzom_changelog.txt.

25h of january 2016

1 Steam: Latest fixes and improvements
- fixed crash when launching Ryzom Configuration under OS X
- fixed all bugs related to Lua 5.3 and its numbers conversion
- fixed paths in .bank
- added functions to be able to use environment variables in paths defined in .cfg
- Ryzom looks for data in several locations depending on platform
- deleted hardcoded Windows paths in C++ code
- implemented a TODO of Guillaume PUZIN related to sheets to visual stot ID conversion speed optimization
- improvement of NLMISC::CCmdArgs tp manage command
-line arguments (display help, version, arguments checks, etc...)
- display native language name in IG configuration
- fixes for VC++ 2015
- added panoply_preview tool to have a preview of colors changes
- dynamic link to X11 to reduce dependencies and since API is stable
- fixed compilation without PCH- support for <base> tag in HTML
- fixed Windows icon for crash_report
- fixed a crash in ryzom_backup_service
- added methods to pack/unpack BNP files directly in NeL CBigFile
- adapted tga2dds, bnp_make and Ryzom client with CCmdArgs to manage command-lines parameters
- fixed "eszett" conversion to "s" using toLower (shouldn't be changed)
- display an error if a filename exists more than once in a BNP file while creating with bnp_make- keeps original translations characters case for emotes names
- replaced spaces by underscores in emote commands

2 RyzomCore
Someone converted some RyzomCore assets to blender: https://plus.google.com/102259963096294243979/posts/ZpoGJqhHeKV
This could be of help for artists who want to use it as a base for new things.

01st of february 2016

The Dev group is still concentrated on Steam. To see the daily improvements: http://ryzom.kervala.net/clients/ryzom_changelog.txt

Q: Someone want to say something for this group?
A: Give a great bravo to the dev and their availability. Thanks.
Kervala: Thanks and you're welcome.

29th of february 2016

Kervala: I'm glad to announce that patch system is working on all platforms now. I enabled it by default for all my static clients (with "static" in their filename) so please try them and report any problem you could notice during patch.

21st of march 2016 

Kervala submitted today the Steam version for validation, now we just have to wait.

18th of april 2016

1 Bug: account creation with Mac OSX client
It was impossible to create an account with OS X client. In fact, certificate was already under OS X, this leads to OpenSSL returning an error saying that we were trying to add it twice. It's fixed.

2 Ryzom forge testing server
Ryzon Forge really needs is own testing server, this will give him more possibilities that with only Yubo. This is a call for dev group, both internal and Ryzom Forge side.
Having an accessible Ryzom shard could allow us to go deeply in our work, more test, more fix (like unimplemented weapon) etc.

3 "Blender Exporting" tool

Q: I didn't follow for real those last few weeks : what is the situation of the new graphic tools?
A: Tamarea: I need to contact Kaetemi to know how it is going. Steam took a lot of my time. Kaetemi still needs designer or 3D artist to try his tool to see what needs to be improved. The first feedback i got is, we should add to this tool an user manual. The tool has been created, its manual is still missing (should be written by Kaetemi) and a maximum of testers to allow him to improve this tool.

Q: Which tool? 
A: Creation of the free (cc-by-SA) tool "Blender Exporting"
This tool, usable on all platforms, aims at allowing computer graphics designers to do without 3DsMax (paid software) by exporting directly their graphic productions from Blender and other software to NeL, Ryzom's free engine.
Blender Exporting development was funded by Winch Gate, the company that owns Ryzom.

The first phase, under trial, is the exporting tool itself. It converts Blender models to the NeL format without needed too much interaction with the artists.

The second phase, in progress, consists in creating a properties and mesh editor, to allow the artists to specify advanced effects for the mesh (like reflections on models, the wind on trees, etc).

The third phase will consist in creating the Zone editor.
While awaiting for the end of the tests, it can be compiled there: https://bitbucket.org/ryzom/ryzomcore/commits/all ). It can also be downloaded through ryzom_tools_static_*.zip on this page http://ryzom.kervala.net/clients/.

9th of may 2016

The Dev team has spent the last three days working with these unavoidable bug fixes following all the changes made in the client, in addition to the usual monitoring:

- No slowdown of the game server has been noticed
- Megacorp had to be temporarily closed because it was using too much CPU, causing timeouts when many simultaneous creations of accounts occured.

Bugs:

- Problem with the subscrition system, which bugs and doesn't run. That's why we decided to open free game server to everybody during a week, the time for the Dev team fix the issue.
So, for a week, the unsubscribed accounts can connect without having to resubscribe and accounts already subscribed have their subscription extended for 7 days.
- Error 62 (AVG antivirus blocking Ryzom). Kervala (Dev) fixed the error and has just updated the Steam client. A patch notes is being written, as other patches have been incorporated into this update.

Improvements and fixes:

- Improvement of the tool restoring the characters in order to shorten the working time facing the influx of restoration requests.
- Fix of Error 62 when connecting to the server (AVG antivirus blocking Ryzom). The Steam client update has just been made.
- Fix of missing textures when some boots were worn with a mage robe
- Other small fixes, added to this update of the Steam client.

23 mai

1 Recrutement
- Recherche d'un dev PHP : Ulukyn recherche un dev PHP bénévole pour travailler avec lui sur Ark. Si vous êtes intéressé(e), veuillez postuler à volunteer@ryzom.com svp.
- Nous avons 2 candidats dev C++ pour aider sur Ryzom Core.

2 Lags de 00:00 UTC et 00:40 UTC
- Correction des lags à 00:00 UTC et 00:40 UTC effectuée il y a quelques jours. Le correctif devrait très fortement atténuer (presque annuler) ces lags. Une annonce officielle sera faite s'il se confirme que le correctif fonctionne (nous n'avons encore eu aucun retour de joueur disant que c'était mieux.)

3 Ryzom Core
- A voir pour la prochaine fois : est-ce que Ryzom Core pourrait améliorer le paramétrage de l'interface pour la rendre réglable en taille ?
- Ryzom Core avait commencé à travailler à un debuggage et à une amélioration de Ryzom Ring pour le rendre de nouveau utilisable. Ce projet est-il encore en cours ?

Q : De ce que je sais, un outil appelé Pocket World devrait remplacer Ryzom Ring ?
R : Oui et c'est toujours prévu. Mais il faut d'abord ouvrir Ark aux joueurs.

4 Gold spammers
Les Gold Spammers sont arrivés sur Atys depuis que Ryzom est sur Steam. L'équipe dev a installé un nouvel outil nous permettant d'être beaucoup plus réactifs pour les chasser du serveur de jeu. 

5 Étude : joueurs désabonnés et free to play
Une réflexion est en cours pour voir s'il serait possible de permettre aux joueurs désabonnés de continuer à pouvoir jouer, mais avec les limitations temporaires du free trial (blocage des niveaux et briques à 125, etc). Les personnages retrouveraient leur niveau d'origine au réabonnement.

6 Ark
L'ouverture d'Ark aux joueurs est presque prête à passer en mode bêta. C'est Ryzom Forge qui sera testeur avant l'ouverture totale aux joueurs. L'interface d'Ark sera améliorée au fil de la bêta.

3oth of may 2016

1 Recruitment:

Looking for a PHP dev: Ulukyn searches a PHP dev volunteer to work with him on Ark. If you are interested, please apply to volunteer@ryzom.com please.

2 Cross-platform live Ryzom chat translator:

Siela: I have started working on a cross-platform live Ryzom chat translator, using the chatlog... it's only in pre-alpha state, but for those wanting to take a look: https://gitlab.com/SIELA1915/rift-translation/tree/master or https://gitlab.com/SIELA1915/rift-translation/