PlaneShift
Gameplay => General Discussion => Topic started by: Tontow on November 21, 2008, 01:00:46 am
-
First off, no spoilers. The knowledge of weather a feature is active on the PS server isn't considered a spoiler so long as who/what/where is not mentioned.
I know of the Dev log http://planeshift.cvs.sourceforge.net/planeshift/planeshift/docs/history.txt?view=log , but that isn't quite what I'm looking for.
What I would like is a list of implemented items (things that are active and can be used on the PS server).
The working skills list comes close to what I would like; however, things like lock picking wouldn't make the list because, even though its working, you can't use it yet to pick any locks.
And the skill list is lacking things like:
Revision 1.4640 - (view) (download) - [select for diffs]
Fri Oct 5 09:14:24 2007 UTC (13 months, 1 week ago) by kennygraunke
Branch: MAIN
Changes since 1.4639: +4 -0 lines
Diff to previous 1.4639
- Added <activemagic> quest prerequisite op, so quests can be given only when
a particular spell category is active.
- Added "Flying a Kite" quest to MaleEnki to test the above. You should only
be able to get the quest after casting Defensive Wind on yourself.
Which wasn't active/implemented when last I checked.
I know the devs are busy little bee-slaves and I understand if such a list isn't possible because of time constraints.
-
the correct link is http://planeshift.svn.sourceforge.net/viewvc/planeshift/trunk/docs/history.txt and there is no way to know when a feature that has been added to svn has been implemented on laanx, some features take a lot of time before they are at a useable state and when things have been updated to support such a feature on laanx.
-
Also, when the history mentions that something is added, it does not mean it works correctly or did not introduce a bunch of new bugs :) It may just mean that something is in development. It does give some idea of what people are working on though.
-
Something that can be done, is tagging. When you cut a release for Laanx, tag it in svn so that we could run a report based on that tag, or get a test env set up using only the code that is currently on laanx. Is this likely to happen any time soon? I can see this having major benefits to potential testers... especially if the version used as the "tag" shows up on the client window when loading psclient, per my recommendation from FS#1818.
-
Is this likely to happen any time soon?
And who is going to program that? :o
-
when a release is done laanx _is_ updated to what is in svn with NO changes other then the database info and the info in the db its self, there is no use tagging things as you need all files for your build and if you mix things up too much it will not build at all. It is a matter of it the features that in the works have been debugged enough to be used and the devs have done their work to make sure it is usable on laanx.
-
you can just download the stable folder which always contains what's on laanx (engine side not db) and the currently compatible client with it