Senior Member
Join Date: Aug 2013
Posts: 123
|
for giggles, remove this:
Code:
<eval phase="Setup" priority="5000">#resmax[resHinder] += 1</eval> |
#21 |
Senior Member
Join Date: Nov 2009
Posts: 891
|
I have a thought on the ability to buy it off. Do you buy it off with an Advance or Edge? Maybe inside the racial property or racial ability you could have it turn itself off, by making it not print. Then, the things that need to look at its existence look at the print value and if it is printing it is in effect, but if it is not printing it is turned off.
The print/noprint code is (I usually put it in pre-traits or traits 5000, but it has a broader range, but it depends on when things need to look at it, I am pretty sure that Setup might even work). Code:
if (hero.tagis[Edge.edgMeLiterate] = 1) then perform this.assign[Print.NoPrint] endif Personally I think that value should be able to be part of everything. Then we could have Derived Traits that only show up when not the default value and have other things turn themselves off or be turned off by mechanic scripts. Evil wins because good rolls poorly .... or the players are not paying enough attention to the game. |
#22 |
Senior Member
Join Date: Feb 2010
Posts: 874
|
And yes, somewhere along the way in process I made the additional version of Illiterate irrelevant, since I deactivate the Hindrance by turning off the Racial Ability itself. Apparently I forgot about it and never got rid of it.
Is there any reason using the regular Hindrance (the way I obviously have it set up now) would make any difference in regard to the Reward thing, though, since its still on the character by being bootstrapped? Last edited by Paragon; April 5th, 2017 at 04:24 PM. |
#23 |
Senior Member
Join Date: Feb 2010
Posts: 874
|
Won't the former reduce the number of Hindrances the character can take? That's why I put it in in the first place as I recall.
|
#24 |
Senior Member
Join Date: Feb 2010
Posts: 874
|
Quote:
|
|
#25 |
Senior Member
Join Date: Aug 2013
Posts: 123
|
Quote:
I suspect that removing that line and testing will NOT give the reward(and by side effect will reduce your available max hindrance points). |
|
#26 |
Senior Member
Join Date: Feb 2010
Posts: 874
|
Well, I went in and fixed a couple things with the Racial Power, just because I was there, but this still seems to be producing the extra Reward point:
Code:
<thing id="rpLessEdu" name="Less Educated" description="Simian communities are superstitious of “modern†or “futuristic†technology, and traditionally don’t teach technology to their young. Simians begin with the Illiterate Hindrance, and cannot take the following skills at the time of character creation: Driving, Lockpicking, Knowledge (Computers, Electronics, Science, and the like), Piloting, Repair. Simians, can buy this off with two character creation points, or as an Advance." compset="RacialProp" summary="Technology averse"> <fieldval field="raceCstVal" value="-2"/> <usesource source="BrEarth"/> <tag group="DomainTerm" tag="Race" name="Race" abbrev="Race"/> <tag group="User" tag="LessEdu" name="LessEdu" abbrev="LessEdu"/> <bootstrap thing="hinBESIll"> <containerreq phase="Initialize" priority="8000">hero#User.LessEdu</containerreq> </bootstrap> <eval phase="Setup" priority="5000"><![CDATA[ if (field[abilActive].value <> 0) then hero.child[resHinder].field[resMax].value += 1 herofield[acMaxMinor].value += 1 herofield[acMaxHindP].value += 1 endif]]></eval> </thing> |
#27 |
Senior Member
Join Date: Feb 2010
Posts: 874
|
Quote:
|
|
#28 |
Senior Member
Join Date: Feb 2010
Posts: 874
|
Just as an interesting side issue, bootstrapping it does not actually prevent you from taking it normally. I'll have to get in and replace that one and set it up so the bootstrapped one blocks access to the regular one.
Edit: This was apparently an artifact of not closing and reopening the program; now that I've done that there's no duplication possible. Last edited by Paragon; April 6th, 2017 at 08:37 AM. |
#29 |
Senior Member
Join Date: Aug 2013
Posts: 123
|
heh... before I was a developer, I spent 8 years on technical support for a few application help desks. One of the things I learned really early on is to remove things ONE BY ONE, testing between each to minimize and eliminate causes. This has helped me immensely when I became a developer(it also helped me realize the kind of stupid stuff clients might attempt so I could test those when I am coding!)
|
#30 |
|
|