Reply to thread

Message

<blockquote data-quote="Cergorach" data-source="post: 21334" data-attributes="member: 725">Re: Re:TemplatesRight on target young Skywalker... Erm, Luke ;-)The &quot;problem&quot; with RPM is that it's so darned huge, i only find things missing when i need them and can't find them.My personal preference would be:1.) Everything that is in RPM works properly.2.) Every functionality that the SRD offers should be in RPM.3.) Basic SRD game prep. features, nothing fancy, just functional.4.) Basic SRD ingame features, nothing fancy, just functional.5.) Add bells and whistles, make it more user friendly, etc.Documentation should be an ongoing process, the ideal situation would be that when you add something you document it.Maybe it would be usefull to compile a list of what is in RPM and what is not and how functional it is and should be. That way people can choose what they find important and what not.As a sidenote, no offense intended to those who think the program should be more usersfriendly, currently development of RPM should (IMHO) concentrate on the integrety of the game mechanics. I find it strange (to put it mildly) that people ask for userfriendlyness (and other gadgets)before things like templates and domains (yeah, yeah, i'm guilty as well, my only defense, i thought they were in there, somewhere). I personally would rather have a crappy fully functional program, than an excellent unfinished program...</blockquote>

[QUOTE="Cergorach, post: 21334, member: 725"] [b]Re: Re:Templates[/b] Right on target young Skywalker... Erm, Luke ;-) The "problem" with RPM is that it's so darned huge, i only find things missing when i need them and can't find them. My personal preference would be: 1.) Everything that is in RPM works properly. 2.) Every functionality that the SRD offers should be in RPM. 3.) Basic SRD game prep. features, nothing fancy, just functional. 4.) Basic SRD ingame features, nothing fancy, just functional. 5.) Add bells and whistles, make it more user friendly, etc. Documentation should be an ongoing process, the ideal situation would be that when you add something you document it. Maybe it would be usefull to compile a list of what is in RPM and what is not and how functional it is and should be. That way people can choose what they find important and what not. As a sidenote, no offense intended to those who think the program should be more usersfriendly, currently development of RPM should (IMHO) concentrate on the integrety of the game mechanics. I find it strange (to put it mildly) that people ask for userfriendlyness (and other gadgets)before things like templates and domains (yeah, yeah, i'm guilty as well, my only defense, i thought they were in there, somewhere). I personally would rather have a crappy fully functional program, than an excellent unfinished program... [/QUOTE]

Verification