Originally Posted by razorace
I'm starting up this thread to get some feedback on how we can improve the OJP documentation to make it more user-friendly.
We're already in the process of converting everything to html, but beyond that I'm not sure what we should do.
One idea is to dramatically reducing the amount of information that is in the changelog. Should we condense the changelog so it only discusses mentions major new features and major fixes? What about the nitty gritty change details? Do people care about that stuff or should only coders know when I've changed the FP cost of kicks from 2 to 3?
What do you guys think?
following are my opinion.
In high priority,
For novice users, our OJP document should include more clear difference from "original JKA" to "latest OJP".
(A present document has only latest changelog)
following proposal of elements,
- OJP concept
- Saber combat manual
- Experience system
- Source build manual
- ToDo(target in the future)
And of course, latest changelog is needed for veteran user.
I welcome web-based document.
It is necessary to always contain the latest specification in an online
In low priority,
we should correspond to multi languages ??
Yes, I will prepare a Japanese document.
These are trifling opinion from me.