This is an iVerse Change Log; a summary of issues raised and/or dealt with through official game designer meetings and efforts.
Content Layout Approach: No true templates – let’s agree that this makes things more work, but it makes the site more portable and less tied to technology except wordpress and html. Post snippets are the exception that’s not negotiable. Some older pages (like some characters) need to be migrated from templates. We should try and consolidate as much content that’s part of common formats into post snippets.
> COMPLETE 11-13
Web Page Editing: A primer is needed for basic HTML for Arabus and WordPress for Arabus and Duncan to edit pages.
>
Specific Content Attribution: Attribution (author, editors, etc.) and inspiration – encourage people/fan to create content? Not now, leave as HTML comment as in-page content at the bottom of pages. Copy as needed from old web site migration effort.
> COMPLETE 11-13
Solicited Feedback: Create a reusable post snippet with a link to a google form to collect data. This is for only specific instances and as a GM for world materials, not to be advertised or used across collections of pages. Do NOT publish this functionality to anyone but existing play groups.
> WORKING
Pages with marker as “Incomplete Materials” – Remove This. Replace with a general note on home page.
> WORKING
More Frequent Site Backups: Weekly – archived to arabus’s google drive
> WORKING
Enable Duncan to edit web pages for iCore materials.
> WORKING
“Not Applicable” text: If a feature has nothing more to add for i20 or Icore, have a standard set of text that says “The details for this are completely covered under the shared/common explanations.” If there are no extra details for either, do NOT insert the tabbed detail display – this should only be used if one or neither of the options is covered completely under the general explanation.
> WORKING
OBSIDIAN PORTAL CONTENT: Migrating content? – schedule this; 5 characters and/or items per 2 weeks – google calendar for Arabus and Kelly.
> First calendar event created.
Feature Versioning: Spreadsheet for major version icore, not minor (grammar, etc.) – use the web site for full iterative; go full iterative progress. Have an archive spreadsheet in google docs. Ultimately, its not work icore going 1 way and i20 another. Since each feature has its own page now, that versioning should be the backup mechanism. Copying data to the web site from skills and traits – There is a column marked as “copied to web site” in the Incarna skill and trait google spreadsheets; There is no current means of tracking i20 changes other than the page edit history.
Feature Treatment between i20 and iCore: Treat d20 “skills” as essentially base lores with focus/specialties? No. will every iCore feature have a d20 skill corollary? Create a spreadsheet – Spreadsheet with d20 to icore correlate – skills, kits, etc. Features – All features should be tagged as i20 and icore? Will everyone of them have an expression for both? If so, then only “trait” or “skill” tag is necessary, not “i20” and “icore”…
> WORKING (spreadsheet for designers)
Poll: Do we need a i20 skill/tool mapping?
YES +4
> WORKING
here is a start to the mapping of d20 proficiencies to iCore equivalents… https://incarna.net/characters/d20/prof/
Advisory Materials: These need to be flagged and put in a collapsing panel for any page. If its not 1) universal explanation, or system (i20/iCore) specific details, move any suggestion of how to incorporate or use to a “Advice” or “GM” panel that has a visual clue to expand it.
Design/Why it Work Approach: Move to Design – why something works the way it does = outside of search, linked from materials.
d20/DnD and Incarna label overlap: Where the label overlaps = ok or change for icore? Change the name = policy. Example: Danger Sense is a iCore feature, and a feature of the Barbarian Class. They work completely differently. The outcome would be to change the incarna label from Danger Sense to something else.
Should character “beauty” be represented as a feature (trait ? assume average)?
Harmony, senses, beauty = 5 levels/2 pos/2neg/no mod
> COMPLETE
Label and Scale unification – the web site uses a dozen or more scales and nothing ties them together except number coincidentally used. DO analysis of all measures and labels used for them.
> DONE
Character Points:
We will try and unify the feature cost between i20 and icore.
i20 will NOT use CP to buy races.
We dont know how races are going to turn out under OneDnD – lets not overthink.
lores under i20 use the 5 scale = skills under icore using full standard progression.
CP in iCore buys archetypes (would you call this a class equiv? Unify somehow?) = NO
CP in iCore buys backgrounds/upbringings (cultural experience equiv? Unify somehow?) = YES
Features:
UNIFY MOMENT LIMITERS? = YES (moment is the moment in time in which a feature can be acquired)
“Any” – Any time in the character’s development, including Character Inception.
“Inception” – Only at the TIME OF Character Inception.
“Experience” – Only AFTER Character Inception.
HOW TO HANDLE i20? (ASI = ability score increase); Mark each feature as eligible as an ASI Feat (Character Inception or dev)?
Symmetric: Only on the common character ASI (i20) that all classes share or __ (iCore)?
Asymmetric: Only on the non-symmetric moments.
> FUCK IT, leave it to WOTC.
Q: Accumulated Character Points has no formal label and the concept and collection are just referred to as CP.
Call the accumulated CP of a character their “CP Pool”.
5
Leave it! Who cares!? We get it!
> COMPLETE
as part of the label reconciliation project and the poll that clearly indicated character points should be referenced as a “pool”, the Basin Scale has been added – used in whole or part specifically for anima energy (synergy, etc. – both wells and pools), character points, and essence. https://incarna.net/ver/design/stand/scale/basin/
Q: Character Points should be used as XP in i20, to buy levels in addition to features.
No, its too dangerous to get PCs out of sync on that level. Policy should continue to be milestone (not XP).
4
Neither should be policy, GMs alone need to contend with game balance of PC levels and game balance.
2
Sounds good, the peril of PCs not being on the same level is outweighed by the options gained. Change the rules/policy.
Q: How shall references to d20 source material (SRD; system reference doc) be handled going forward?
Use the Online SRD – it may be lo-fi, but it likely will never go away as it is just a web output of the SRD pdf source .
= all
A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | AA | AB | AC | AD | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1
|
updated on the site?
|
done | ||||||||||||||||||||||||||||
2
|
Level | knowledge |
grasp/exposure
|
lores | language | education (formal) | experience | availability (items) | ease of use | familiarity | icore rank | skill | harmony | senses | trepidation |
reasonableness
|
litany (faith) | effects | codes | aptitude | conviction | anima well | weaves | essence | CP | learning cost | actions | |||
3
|
"discovery" | feeble | disability? | |||||||||||||||||||||||||||
4
|
weak | |||||||||||||||||||||||||||||
5
|
neg | secret/hidden |
misapprehension
|
uneducated (remote/culture only)
|
alien | -x to -1 | dull | anxiety | anxiety | ex: healing |
unlimited measure/level as skill
|
d20 max = prof bns
|
||||||||||||||||||
6
|
zero | unfamiliar | 0 | latent | 0 | 0 | anyone | accumulated | pool | CP | flat | Disastrous | ||||||||||||||||||
7
|
1 | rudimentary | common | common | basic | basic (primary) | familiar | pervasive | ease +1 | familiar | beginner | 1 | opposed | sharp | disorienting | unconfident | general | trivial | trivial | 1 | 1 | 1 | apt 1 start |
currently assigned
|
pledged | easy cost | Dire | |||
8
|
2 | foundational | common | common | conversation | advanced (secondary) | competent | common | ease +2 | experienced | 2 | incompatible | strong | exacting | confident | shared | minor | minor | 2 | 2 | 2 | apt 2 start |
currently unassigned
|
free | CP | standard cost | Failure | |||
9
|
3 | accomplished | common | common | fluent | BA or BS | practiced | uncommon | accomplished | 3 | different | myopic | overconfident | abiding | major | major | 3 | 3 | 3 | apt 3 start | expected | (future) | CP | high cost | Simple | |||||
10
|
4 | expert | uncommon | uncommon | fluent | PHD | scarce | expert | 4 | compatible | acute | 4 | 4 | 4 | apt 4 start | spent | spent | spent | Major | |||||||||||
11
|
5 | master | rare | obscure | fluent | MD, etc. | rare | master | 5 | aligned | natural | 5 | 5 | apt 4 start | Extraordinary | |||||||||||||||
12
|
plus | unique | "Acuteness Scale" | 6+ | 6+ | |||||||||||||||||||||||||
13
|
EX: This feature uses the 5 standard level "Significance Ranking System"; 0 to 4 in this case.
|
property: ease | feeble | |||||||||||||||||||||||||||
14
|
NEW/PROPOSED | "Access Scale" | "Practice Scale" | "Harmony Scale" | weak |
within a given set of adopters
|
||||||||||||||||||||||||
15
|
neg | alien | ill-educated (misapprehension) | alien | dull | disorienting | unconfident |
can use 1+ level at once; limit by aptitude, cost scales w/aptitude to increase measure and volume
|
disability | |||||||||||||||||||||
16
|
0 | hidden (GM only) | unfamiliar | uneducated | unfamiliar | latent | latent | character rank | Disastrous | |||||||||||||||||||||
17
|
1 | pervasive | pervasive | familiar | familiar | pervasive | familiar | pervasive | minor (+1) | beginner | familiar | opposed | minor (+1) | myopic | overconfident | general | minor | pervasive | pervasive | pervasive | pervasive | apt 1-4 start | minor (1 CP) | pool | pool | flat | Dire | |||
18
|
2 | common | common | competent | competent | common | competent | common | major (+2) | competent | competent | incompatible | major (+2) | shared | major | common | common | common | common | natural apt start | major (2 cp) | pledged | pledged | minor | Failure | |||||
19
|
"significant/fluent" 3 | uncommon | common | accomplished | accomplished | uncommon | accomplished | uncommon | significant (+4) | accomplished | accomplished | different | significant (+4) | abiding | significant | uncommon | uncommon | uncommon | uncommon |
significant (up to 4 CP)
|
free | free | major | Simple | ||||||
20
|
4 | scare | uncommon | expert | expert | scarce | expert | scarce | expert | expert | compatible | scarce | scarce | scarce | future | future | significant | Major | ||||||||||||
21
|
5 | rare | uncommon | master | master | rare | master | rare | master | master | aligned | rare (natural) | rare | rare | spent | spent | Extraordinary | |||||||||||||
22
|
singular | unique | singular | singular | unique | |||||||||||||||||||||||||
23
|
where does forbidden fit? any can be forbidden
|
|||||||||||||||||||||||||||||
24
|
proscribed? by who?
|
|||||||||||||||||||||||||||||
25
|
forbidden is by perspective – Gret danger in its outcome to user, place, and living creatures in the area.
|
The “Latent” label is now going to be just having anima energy (synergy, etc.) only – no associated aptitude. Latent will NO LONGER affect psychic alone the way it did. In order to get psychic powers, you must buy psychic aptitude. Meditation is universal and can be used perhaps as a fulcrum to “buying” simple powers temporarily for an anima cost (focus in the case of psychic). Aptitude Saturation can be used to make psychic easier to acquire or manipulate with anima. This is not a poll, but you can reply with any issues. Issues will be resolved within this new framework though – standardization will have less issues no matter how you slice it.