Jump to content

rAthena feature tracking


Antares

Recommended Posts


  • Group:  Members
  • Topic Count:  74
  • Topics Per Day:  0.02
  • Content Count:  420
  • Reputation:   89
  • Joined:  01/30/12
  • Last Seen:  

Hi!

 

I originally posted this @ Hercules boards, but I think this would be nice to implement here as well:

http://hercules.ws/board/topic/937-hercules-feature-tracking/

 

Xgear advised me to start this suggestion, based on this post:

http://hercules.ws/board/topic/744-hercules-feature-status/

 

So would it be possible to make some kind of page/document/txt/anything in which everyone can keep track of the implemented kRo features of rAthena? It would be good, because looking thru the trac is not very easy to find something, and gathering data on features would be easier, because we would know what is missing and what is already done. Even a plain txt, updated regularly would suffice, but of course it can be made more sophisticated.

 

The point is that this shouldn't be a timeline thing, but a fix list of features which is updated every time something new appears.

For example:

 

 

-3rd jobs:              Implemented @ 2019.12.12 - r19999
-renewal mechanics:     Partially Implemented
     -renewal aspd:     Implemented @ 2019.11.11 - r18888
     -renewal attack:   To be done
-WOE TE:                To be done
-Episode 13 quests      Implemented @............
-Client support         2012-04-10 Implemented @............
-Episode 19.2 quests    To be done
-LHZ dun 04 & mobs      Implemented @............
etc
etc
etc
etc
 

 

 

 

/edit

Ah yes, and it doesen't need to be very detailed down to every function that appeared. So if we already implemented, let's say episode 12 and below, and episode 13 is to be done, then we can say that

-episode 12 and below: implemented @ ...........

-episode 13: to be done

 

Same for client support dates, and anything that is continously developing. This way the list remains easily readable.

 

 

 

/additional

We can show the revision numbers to only those we implement now and we already know. It's not super neccessary to look it up to the fist thing.

 

 

PS:

Sry for copying from Herc. I didn't have time to rewrite all of this, and since many users are present on both forums it would look strange to post the same thing :)

Edited by Antares
Link to comment
Share on other sites


  • Group:  Members
  • Topic Count:  111
  • Topics Per Day:  0.02
  • Content Count:  573
  • Reputation:   20
  • Joined:  11/19/11
  • Last Seen:  

How about this ? http://rathena.org/board/forum/186-implemented/

 

 

SlashGeeGee

Link to comment
Share on other sites


  • Group:  Members
  • Topic Count:  74
  • Topics Per Day:  0.02
  • Content Count:  420
  • Reputation:   89
  • Joined:  01/30/12
  • Last Seen:  

How about this ? http://rathena.org/board/forum/186-implemented/

 

 

SlashGeeGee

 

Not bad.. But this is more technical than I think of, and it is a mainly forum topic of suggestions, which is not very organized, and many things are missing. I think of something more like a documentation, a plain text doc without the discussions and etc, only with the results.

 

Btw thx for the link! It's a good thing to start with :)

Edited by Antares
Link to comment
Share on other sites

  • 5 months later...

  • Group:  Forum Manager
  • Topic Count:  282
  • Topics Per Day:  0.06
  • Content Count:  3123
  • Reputation:   1617
  • Joined:  03/26/12
  • Last Seen:  

We can do this with IP.Content when it get fully enabled after the next forum upgrade (which shouldn't be far away). The devs can create the page, link to who created the patch, link to the git rev.

 

OR

 

Create a "Features" page on the wiki...

  • Upvote 1
Link to comment
Share on other sites


  • Group:  Members
  • Topic Count:  41
  • Topics Per Day:  0.01
  • Content Count:  237
  • Reputation:   19
  • Joined:  06/05/13
  • Last Seen:  

i suggest on this it will be a document which contains the kRO patch. and much better if there is an instruction how to disable a feature included on the emulator.

  • Upvote 1
Link to comment
Share on other sites

×
×
  • Create New...