PlaneShift
Support => Server Status => Topic started by: Xordan on August 28, 2008, 03:59:58 pm
-
There has been an update today. Please run your updater to get it.
-
Updated. Thanks for the heads up here on the forums!!
-
Ooh, thanks, Xordan!
What kinds of things have been put in the update, and what bugs should be gone? Or will it be listed somewhere in the update?
-
Most of the changes were server side, we removed a fairly big dependency there.
I can't remember everything, but I know there's a few bug fixes related to the server event code - hopefully fixing a combat issue. Also I recall something related to glyphs disappearing during purify being fixed.
Client side.. not much has changed. Some updater improvements.. animation fixes.. focus and mouselook improvements, improved weapon descriptions, some crash fixes.
Ah, also some new items were added.
-
Damn you for making it so I can't tell exactly what's changed within zip files!
Other than that, woo!
-
This may be a topic for discussion in the wishlist or simply the bug tracker as a feature request, but...
When updating, and there is an xml change for a gui element, would it be possible (or does it already exist as a parameter i can pass) for the update to NOT overwrite the existing xml, and just create it as a .xml.psnew or something? I had a couple of custom xml files that Caarrie created, and now I need to go download them and mod them again.
Other than that, I played for a couple of hours last night and didn't have combat stall out once!!!! I finally got to practice the lvl of armor I trained just before the 0.4.01 upgrade!!! THANK YOU!!! \\o// :thumbup: \\o//
-
I think the best solution for that is to make xml's in the userdir override those in the install dir. Should be added as a feature request I suppose.
-
we have http://www.hydlaa.com/flyspray_upgrade/index.php?do=details&task_id=2100 already
-
As always Caarrie, you are on top of things. :)
-
Another thig that changed in the client is the sketch editor. Our contributors worked on it and improved its usability.
-
If anyone cares 341 bugs have been closed and 614 bugs opened on the tracker since the last release.
-
I understand facts are facts... but how do you interpret those numbers? Is it that more players are getting involved with things and filing bug reports, or are things kinda taking one step forward... 2 steps back? Are these only bugs, or feature requests too?
-
that includes feature requests. it is just a number does not mean anything unless we sit down and count how many are duplicates and such.
-
I suspected as much, but wanted to get it clarified so it didn't look quite so bad. I will, however, take it as a good sign that players are trying to give feedback via the tracker.
-
lets look at it another way:
there are currently 6 unconfirmed bugs reported since the last release
there are currently 53 confirmed bugs reported since the last release [that are not fixed]
there are currently 20 assigned bugs to devs/prospects since the last release [that are not fixed]
there is 1 bug that is in progress since the last release
there are 2 bugs "ready to test" since the last release [that have not been tested]
there is one bug ready to review since the last release [a bug fixed by a prospect that has not been reviewed by a dev]
there are 42 feature requests since the last release
so looking at the numbers again there are 111 bugs open since the last release
there are 305 bugs closed since last release
there are 26 open feature requests since the last release [maybe the tracker lied to me last time i ran the numbers :P ]
-
I think Caarrie might have spent too much time answering all those updater problems, and made a counting error somewhere :) The numbers I got from the bug tracker are:
337 new bugs since last release, 304 were closed. There were 69 new feature requests opened, and 57 closed.
The closed bugs (and therefor also the new bugs) include duplicate reports. The same goes for feature requests. Qualitatively, I see that the number of critical bugs is decreasing (and I am sure more will be fixed soon(tm)).
-
I think Caarrie might have spent too much time answering all those updater problems, and made a counting error somewhere :)
since all i did was a search on the tracker and no counting i dont know where the tracker told me the numbers i got :P
The good thing is the numbers are better then what i reported the first time ;)