TECHNICAL SUPPORT / WEB APPs BUGS

Well you can always ask one of the Character Shepherding Rascals (I love this one) while in game - they should know the status ;-)

And if you want to be nice you could also add that they can close the ticket because it's solved now...

In some cases it's good that we can't see the status of our tickets.
Just imagine Bitty files a complaint ticket against you, Biroeg, and all the things noted about your defense would be visible to Bitty...
And I don't know how integrated the ticket system really is so it might log additional data depending on the ticket type as well (system config, location, ....) - at least I wouldn't want that publicly visible or even visible to my own account (the later would have been different if the account and game login would use different passwords though - which was the case in the beginning)

Or, a nice person could report on the forum thread covering their report of the problem that it is solved so that the Creeping Servants of Ryzom could close the issue, and even thank them for their diligent effort - See previous post (Really, this should be a contest).

You've taken a specific observation about the status of reported bugs and generalized it to behavior complaint tickets and internal player database information. That's like arguing against holding any opinion because man tends to go to war armed with opinions and weapons. You can't argue apples and grenades and not get covered in applesauce.

A bug and game mechanic issue database would allow us to know if what we encounter has already been reported, what the status is, and if there is anything we can do to work around it for now. It would be, for both developers and us players, very beneficial - but that's just me being reasonable again.

Talking to a Contracted to Serve Residents today, I got an answer to this.

There is an issues database and tracker at the open source ryzom core development website. That is exactly what is needed.

Regarding the OS project site - I think that the bug tracker will change soon (or is already undergoing the move) - not sure about the status right now.

I just mentioned that because I doubt that the in game tickets are running into multiple systems in the backend and I don't think that the issue mentoned here would be solveable by the OS devs as it's related to a part of the gam ethat's still in the progress of being merged into the OS part (at least to my knowledge it's still not fully integrated)

As mentioned above, this issue has already been solved.

Yes, the slow website migration from http://dev.ryzom.com to http://ryzomcore.org is causing huge problems. Cross linked pages that are out-of-date and contradictory in an environment already overly threaded between multiple sites (google, atlassian, etc.) make for an impossible situation for new comers to the Ryzom core.

However, there still seems to only be one issue database, and it shows recent activity so it is still a good place to register very technical issues. I've got two there already. A Chivalrous Sentinel Rover suggested it for a mouse action bug I found.

Ha ha that one reminded me of The Asimov Comic by the Part-Time Scientists.

But yeah - that mouse bug (what ever it is) seems to be technical enough for the folks there :-)