Reply to thread

Message

<blockquote data-quote="marli" data-source="post: 5377273" data-attributes="member: 86402">i'd be happy to test, suggest ideas and submit data.however considering the fact that once you start distibuting this to the public you may come into conflict with the BBEWOTC.therefore I'd suggest breaking this project into two.1)the core code that handles most of the processing.you can keep control of this. keeping control of the code.2)data files, powers, feats, classes etc into a external data files.allow these files to be publicly edited and distibuted. If the datasytem fireinakasha suggests i'd go with that.this means you could distribute an official dataset that wont offend WOTC that would produce a character that would be valid but have only power names and feat names.if some commie feels they want to take your work and wotc and release a version they wont need to target you core program and bring wotc wrath down on you.</blockquote>

[QUOTE="marli, post: 5377273, member: 86402"] i'd be happy to test, suggest ideas and submit data. however considering the fact that once you start distibuting this to the public you may come into conflict with the BBEWOTC. therefore I'd suggest breaking this project into two. 1)the core code that handles most of the processing. you can keep control of this. keeping control of the code. 2)data files, powers, feats, classes etc into a external data files. allow these files to be publicly edited and distibuted. If the datasytem fireinakasha suggests i'd go with that. this means you could distribute an official dataset that wont offend WOTC that would produce a character that would be valid but have only power names and feat names. if some commie feels they want to take your work and wotc and release a version they wont need to target you core program and bring wotc wrath down on you. [/QUOTE]

Verification