Reply to thread

Message

<blockquote data-quote="Dalamar" data-source="post: 7279277" data-attributes="member: 358">A bubblegum fix would be the ability to set a skill to desired rank in the character edit menu. Not perfect (especially if you would have taken ranks after getting the exploit), but it gets the skill to the character view. &nbsp;Oh, definitely if you're going to work on a GUI, this is less important of an issue. Currently it is mostly an issue because the only way to see an exploit's description in the program itself is to pick the exploit and then accept or decline it. I would suggest using an exploit's internal name (IIRC, your code did not have that be the same as the exploit's display name), though that does mean you need to at some point have the program check that there are no duplicate internal names for multiple exploits. Which is quite possible with some career exploits duplicating universal exploits with different requirements. I'm going to disagree a bit with Morrus here. Hiding all normally unavailable choices means the program is now unable&nbsp; to handle house rules like having free choice of your trait. Then again, a GUI will probably handle this issue as well.</blockquote>

[QUOTE="Dalamar, post: 7279277, member: 358"] A bubblegum fix would be the ability to set a skill to desired rank in the character edit menu. Not perfect (especially if you would have taken ranks after getting the exploit), but it gets the skill to the character view. Oh, definitely if you're going to work on a GUI, this is less important of an issue. Currently it is mostly an issue because the only way to see an exploit's description in the program itself is to pick the exploit and then accept or decline it. I would suggest using an exploit's internal name (IIRC, your code did not have that be the same as the exploit's display name), though that does mean you need to at some point have the program check that there are no duplicate internal names for multiple exploits. Which is quite possible with some career exploits duplicating universal exploits with different requirements. I'm going to disagree a bit with Morrus here. Hiding all normally unavailable choices means the program is now unable to handle house rules like having free choice of your trait. Then again, a GUI will probably handle this issue as well. [/QUOTE]

Verification