Best Practice - Changing existing Edges?

[TCArknight]

Team,

I wanted to touch base and see how others handle this situation when working on settings.

If you have a setting where core edges/hindrances/etc. are identical except for some prerequisites, what’s the best way to code for that.

For example, one setting I’m looking at has:

 Mr. Fix-It
Requirements: Novice, Smarts d10+, Repair d10+, Knowledge (technology) at d8+
This Edge has different requirements, but otherwise functions as described in the Savage Worlds Rulebook.

If I just preclude the core Mr. Fix-It, then anything looking for it will not find the new, Setting-specific version.

Is this a situation where “replaces” is best? Or is there another better way to handle it?

Thanks!
TC

[CapedCrusader]

DO NOT EVER USE REPLACES.

That is for something else used by the core system. It is NOT intended for this use. Please do not ever use it.

[TCArknight]

Originally Posted by CapedCrusader

DO NOT EVER USE REPLACES.

That is for something else used by the core system. It is NOT intended for this use. Please do not ever use it.

I completely agree! I can’t think of when I might have used it previously too but wanted to put it out there.

If the core edge has Edge.MyName and the New one is Edge.MyNewEdge, have you seen an issue if the new Edge has both?

[TCArknight]

Did a bit of testing.

If an edge, MyNewEdge, is specifically given Edge.MyName, then when it is taken the hero will receive both tags.

The only thing I see an issue with is if you did something like hero.tagcount[Edge.?]. In that case, each time the count would be 1 greater because the one edge is providing two tags.

Maybe we need a CountsAs tag for edges and hindrances?

[CapedCrusader]

This is an ongoing issue, even within a Setting at times. What we (Setting Authors) have always done is replace any Edges affected with replacement versions for the Setting. Anything that has Edge.MyName as part of it's prerequisite would also have to be precluded and recreated. Yes, this can have a nasty domino effect. Not really a lot to do about it, part of the cost of flexibility. We try to structure things to avoid this, but it's not always possible. Oh, also, now that I think of it having the tag would not solve something like a pickreq, it would only work if the prereq used a tag test.