From: SourceForge.net <no...@so...> - 2007-11-30 20:32:27
|
Data Feature Requests item #1757673, was opened at 2007-07-20 09:45 Message generated for change (Comment added) made by amaitland You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=750092&aid=1757673&group_id=25576 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Implement New Feature >Group: For 6.0 Status: Open Resolution: None Priority: 7 Private: No Submitted By: Frank Kliewe (frank_kliewe) Assigned to: Frank Kliewe (frank_kliewe) Summary: [MSRD] Move Occupations to ABILITY Initial Comment: Occupations need to be moved to their own category. This will allow to select them more freely and is also needed to create an output sheet that displays the standard Modern statblock. -- Frank ---------------------------------------------------------------------- >Comment By: LegacyKing (amaitland) Date: 2007-11-30 12:32 Message: Logged In: YES user_id=1286039 Originator: NO Sounds like the best solution will be CDOM, so pushing this to 6.0 ---------------------------------------------------------------------- Comment By: LegacyKing (amaitland) Date: 2007-08-27 22:37 Message: Logged In: YES user_id=1286039 Originator: NO As I have finished the conversion I think the solution is actually very simple - In all cases of the Class having an occupation use ADD:ABILITY|CATEGORY=Occupation,TYPE.Occupation It kicks in at first level. Depending on how you want to work it, we can either allow it to be modified, or not. Anyways, I've sent you the two emails with the modifications to the entire MSRD line. We will need a separate tracker to locate any .MODs that deal with Occupations as they won't be considered a 'Feat'. -AM ---------------------------------------------------------------------- Comment By: Frank Kliewe (frank_kliewe) Date: 2007-08-23 10:28 Message: Logged In: YES user_id=1241568 Originator: YES I first need to think this through fully. One of the problems is that occupations need to be taken at first level. While we can enforce that with use of PRExxx, some users will want to override that. I don't think the FEATPRE rule will affect non-Feat Abilities, so we may have to put in rule for that. But there will be other side effects that happen to be incorrect when an occupation is taken after 1st level, especially class skills are problematic here. If you wish you can start to create the basic abilities already. You'll have to create 2 different ability categories, Occupation and Internal. CATEGORY:Internal will later find a lot more use, as it is meant as a general non-visible category for workarounds and other stuff, that don't need to be displayed on their own. The skill choices are stuff like that, so it won't be necessary to create an extra Occupation_skills category for them, just let them use Internal. Once you have finished those, please send the files to me first. I will then see from the practical testing if a rule in the prefs makes sense or not. Feel free to mail me about any problems you run into. -- Frank ---------------------------------------------------------------------- Comment By: LegacyKing (amaitland) Date: 2007-08-22 18:56 Message: Logged In: YES user_id=1286039 Originator: NO (Assigning to Frank to catch his eye) FRANK: I can take a crack at this (I just finished writing about abilities). I'll need some assistance, but I think I can manage to get the bulk finished. Let me know. -AM ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=750092&aid=1757673&group_id=25576 |