Template:HeroSpecializationDef - Revision history

76561198026315966: obelisk-bot: Pushing translation table rework

2026-05-14T20:48:11Z

obelisk-bot: Pushing translation table rework

← Older revision		Revision as of 20:48, 14 May 2026
Line 8:		Line 8:
	<code>Data:HeroSpecialization/<id></code> carries:		<code>Data:HeroSpecialization/<id></code> carries:

	# <code><nowiki>{{HeroSpecializationDef \| id=… \| ~~name~~=… \| ~~desc~~=… \| ~~icon~~=… \| …}}</nowiki></code>		# <code><nowiki>{{HeroSpecializationDef \| id=… \| icon=… \| name_sid=… \| desc_sid=… \| …}}</nowiki></code>
	# <code><nowiki>{{TranslationDef \| type=hero_specialization \| target_id=<id> \| …}}</nowiki></code>		# N × <code><nowiki>{{TranslationDef \| type=hero_specialization \| target_id=<id> \| language=… \| …}}</nowiki></code> — one row per language
	# N × <code><nowiki>{{HeroSpecializationBonus \| spec_id=<id> \| ordinal=N \| …}}</nowiki></code> (1367 total bonus rows across all 126 specs)		# N × <code><nowiki>{{HeroSpecializationBonus \| spec_id=<id> \| ordinal=N \| …}}</nowiki></code> (1367 total bonus rows across all 126 specs)

Line 15:		Line 15:
	{{#cargo_declare:_table=HeroSpecialization		{{#cargo_declare:_table=HeroSpecialization
	\| id = String		\| id = String
	~~\| name = String~~
	~~\| description = Wikitext~~
	\| name_sid = String		\| name_sid = String
	\| desc_sid = String		\| desc_sid = String
Line 26:		Line 24:
	{{HeroSpecializationDef		{{HeroSpecializationDef
	\| id = String		\| id = String
	\| ~~name~~ = String		\| icon = String
	~~\| description~~ = ~~Wikitext~~		<!-- Localization references — display text lives in the Translation table, type='hero_specialization' -->
	\| name_sid = String		\| name_sid = String
	\| desc_sid = String		\| desc_sid = String
	~~\| icon = String~~
	\| source_path = String		\| source_path = String
	}}		}}
Line 37:		Line 34:
	== Field notes ==		== Field notes ==
	* '''<code>id</code>''' is the source JSON id (e.g. <code>human_hero_1_specialization</code>, <code>campaign_hero_4_specialization</code>). The <code>_specialization</code> suffix is preserved.		* '''<code>id</code>''' is the source JSON id (e.g. <code>human_hero_1_specialization</code>, <code>campaign_hero_4_specialization</code>). The <code>_specialization</code> suffix is preserved.
	* '''<code>name_sid</code> / <code>desc_sid</code>''' point at the L10n entries (e.g. <code>human_hero_1_spec_name</code> / <code>human_hero_1_spec_description</code>). Description text is heavy with <code>{0}</code>/<code>{1}</code> placeholders for stat values; the resolver substitutes via the standard pipeline before storing.		* '''<code>name_sid</code> / <code>desc_sid</code>''' point at the L10n entries (e.g. <code>human_hero_1_spec_name</code> / <code>human_hero_1_spec_description</code>), surfaced for traceability. Description text is heavy with <code>{0}</code>/<code>{1}</code> placeholders for stat values; the resolver substitutes via the standard pipeline before storing the translation.
	* '''~~<code>~~name~~</code> / <code>desc<~~/~~code>~~''' ~~carry the resolved~~ English ~~text inline. Translations~~ live on the <code>~~<nowiki>{{TranslationDef \|~~ type=hero_specialization~~}}</nowiki>~~</code> ~~row~~.		* '''Display name / description''' for every language (English included) live in the [[Template:TranslationDef\|Translation]] table, <code>type='hero_specialization'</code>.
	* '''No <code>hero_id</code> back-reference.''' The Hero → HeroSpecialization direction is sufficient (forward join via <code>Hero.specialization_id = HeroSpecialization.id</code>). Reverse queries — "which hero has this spec" — work via the same join~~. Per D-028~~.		* '''No <code>hero_id</code> back-reference.''' The Hero → HeroSpecialization direction is sufficient (forward join via <code>Hero.specialization_id = HeroSpecialization.id</code>). Reverse queries — "which hero has this spec" — work via the same join.

	== Related tables ==		== Related tables ==
	* [[Template:HeroDef\|Hero]] — joined on <code>id = Hero.specialization_id</code> (1:1 in practice; the schema permits N:1 in case a future patch shares specs across heroes).		* [[Template:HeroDef\|Hero]] — joined on <code>id = Hero.specialization_id</code> (1:1 in practice; the schema permits N:1 in case a future patch shares specs across heroes).
	* [[HeroSpecializationBonus]] — joined on <code>id = spec_id</code> (1:N).		* [[HeroSpecializationBonus]] — joined on <code>id = spec_id</code> (1:N).
	* [[Template:TranslationDef\|~~<code>TranslationDef</code>~~]] — ~~one row per spec with~~ <code>type=hero_specialization</code>, ~~<code>target_id=id</code>~~.		* [[Template:TranslationDef\|Translation]] — display text in every language (English included), joined on <code>id = Translation.target_id WHERE Translation.type='hero_specialization' AND Translation.language='{{{lang\|en}}}'</code> (1:N, one row per language).

	== Notes ==		== Notes ==
Line 51:		Line 48:
	</noinclude><includeonly>{{#cargo_store:_table=HeroSpecialization		</noinclude><includeonly>{{#cargo_store:_table=HeroSpecialization
	\| id = {{{id\|}}}		\| id = {{{id\|}}}
	~~\| name = {{{name\|}}}~~
	~~\| description = {{{description\|}}}~~
	\| name_sid = {{{name_sid\|}}}		\| name_sid = {{{name_sid\|}}}
	\| desc_sid = {{{desc_sid\|}}}		\| desc_sid = {{{desc_sid\|}}}

76561198026315966: obelisk-bot: uploading initial Cargo templates

2026-05-13T01:12:43Z

obelisk-bot: uploading initial Cargo templates

← Older revision		Revision as of 01:12, 13 May 2026
Line 57:		Line 57:
	\| icon = {{{icon\|}}}		\| icon = {{{icon\|}}}
	\| source_path = {{{source_path\|}}}		\| source_path = {{{source_path\|}}}
	}}</includeonly>		}}
			Created <code>HeroSpecialization</code> entry: <code>{{{id\|}}}</code></includeonly>

76561198026315966: obelisk-bot: uploading initial Cargo templates

2026-05-13T00:02:24Z

obelisk-bot: uploading initial Cargo templates

← Older revision		Revision as of 00:02, 13 May 2026
Line 3:		Line 3:

	The specialization carries identity (name, desc, icon) plus a list of structured <code>bonuses[]</code> effects that compose the spec's mechanical impact. Bonuses are emitted as inline		The specialization carries identity (name, desc, icon) plus a list of structured <code>bonuses[]</code> effects that compose the spec's mechanical impact. Bonuses are emitted as inline
	<code>{{HeroSpecializationBonus}}</code> rows on the same wiki page.		<code><nowiki>{{HeroSpecializationBonus}}</nowiki></code> rows on the same wiki page.

	== Page layout ==		== Page layout ==
	<code>Data:HeroSpecialization/<id></code> carries:		<code>Data:HeroSpecialization/<id></code> carries:

	# <code>{{HeroSpecializationDef \| id=… \| name=… \| desc=… \| icon=… \| …}}</code>		# <code><nowiki>{{HeroSpecializationDef \| id=… \| name=… \| desc=… \| icon=… \| …}}</nowiki></code>
	# <code>{{TranslationDef \| type=hero_specialization \| target_id=<id> \| …}}</code>		# <code><nowiki>{{TranslationDef \| type=hero_specialization \| target_id=<id> \| …}}</nowiki></code>
	# N × <code>{{HeroSpecializationBonus \| spec_id=<id> \| ordinal=N \| …}}</code> (1367 total bonus rows across all 126 specs)		# N × <code><nowiki>{{HeroSpecializationBonus \| spec_id=<id> \| ordinal=N \| …}}</nowiki></code> (1367 total bonus rows across all 126 specs)

	== Schema ==		== Schema ==
Line 16:		Line 16:
	\| id = String		\| id = String
	\| name = String		\| name = String
	\| ~~desc~~ = Wikitext		\| description = Wikitext
	\| name_sid = String		\| name_sid = String
	\| desc_sid = String		\| desc_sid = String
Line 27:		Line 27:
	\| id = String		\| id = String
	\| name = String		\| name = String
	\| ~~desc~~ = Wikitext		\| description = Wikitext
	\| name_sid = String		\| name_sid = String
	\| desc_sid = String		\| desc_sid = String
Line 38:		Line 38:
	* '''<code>id</code>''' is the source JSON id (e.g. <code>human_hero_1_specialization</code>, <code>campaign_hero_4_specialization</code>). The <code>_specialization</code> suffix is preserved.		* '''<code>id</code>''' is the source JSON id (e.g. <code>human_hero_1_specialization</code>, <code>campaign_hero_4_specialization</code>). The <code>_specialization</code> suffix is preserved.
	* '''<code>name_sid</code> / <code>desc_sid</code>''' point at the L10n entries (e.g. <code>human_hero_1_spec_name</code> / <code>human_hero_1_spec_description</code>). Description text is heavy with <code>{0}</code>/<code>{1}</code> placeholders for stat values; the resolver substitutes via the standard pipeline before storing.		* '''<code>name_sid</code> / <code>desc_sid</code>''' point at the L10n entries (e.g. <code>human_hero_1_spec_name</code> / <code>human_hero_1_spec_description</code>). Description text is heavy with <code>{0}</code>/<code>{1}</code> placeholders for stat values; the resolver substitutes via the standard pipeline before storing.
	* '''<code>name</code> / <code>desc</code>''' carry the resolved English text inline. Translations live on the <code>{{TranslationDef \| type=hero_specialization}}</code> row.		* '''<code>name</code> / <code>desc</code>''' carry the resolved English text inline. Translations live on the <code><nowiki>{{TranslationDef \| type=hero_specialization}}</nowiki></code> row.
	* '''No <code>hero_id</code> back-reference.''' The Hero → HeroSpecialization direction is sufficient (forward join via <code>Hero.specialization_id = HeroSpecialization.id</code>). Reverse queries — "which hero has this spec" — work via the same join. Per D-028.		* '''No <code>hero_id</code> back-reference.''' The Hero → HeroSpecialization direction is sufficient (forward join via <code>Hero.specialization_id = HeroSpecialization.id</code>). Reverse queries — "which hero has this spec" — work via the same join. Per D-028.

Line 52:		Line 52:
	\| id = {{{id\|}}}		\| id = {{{id\|}}}
	\| name = {{{name\|}}}		\| name = {{{name\|}}}
	\| ~~desc~~ = {{{~~desc~~\|}}}		\| description = {{{description\|}}}
	\| name_sid = {{{name_sid\|}}}		\| name_sid = {{{name_sid\|}}}
	\| desc_sid = {{{desc_sid\|}}}		\| desc_sid = {{{desc_sid\|}}}

76561198026315966: obelisk-bot: uploading initial Cargo templates

2026-05-12T23:33:20Z

obelisk-bot: uploading initial Cargo templates

New page

<noinclude>
One row per hero specialization (126 in the 2026-05-03 corpus: 108 faction + 9 campaign + 5 tutorial + 4 test). Each spec is the unique passive that distinguishes one hero mechanically — every Hero record carries <code>specialization_id</code> pointing at one of these.

The specialization carries identity (name, desc, icon) plus a list of structured <code>bonuses[]</code> effects that compose the spec's mechanical impact. Bonuses are emitted as inline
<code>{{HeroSpecializationBonus}}</code> rows on the same wiki page.

== Page layout ==
<code>Data:HeroSpecialization/<id></code> carries:

# <code>{{HeroSpecializationDef | id=… | name=… | desc=… | icon=… | …}}</code>
# <code>{{TranslationDef | type=hero_specialization | target_id=<id> | …}}</code>
# N × <code>{{HeroSpecializationBonus | spec_id=<id> | ordinal=N | …}}</code> (1367 total bonus rows across all 126 specs)

== Schema ==
{{#cargo_declare:_table=HeroSpecialization
| id = String
| name = String
| desc = Wikitext
| name_sid = String
| desc_sid = String
| icon = String
| source_path = String
}}

<pre><nowiki>
{{HeroSpecializationDef
| id = String
| name = String
| desc = Wikitext
| name_sid = String
| desc_sid = String
| icon = String
| source_path = String
}}
</nowiki></pre>

== Field notes ==
* '''<code>id</code>''' is the source JSON id (e.g. <code>human_hero_1_specialization</code>, <code>campaign_hero_4_specialization</code>). The <code>_specialization</code> suffix is preserved.
* '''<code>name_sid</code> / <code>desc_sid</code>''' point at the L10n entries (e.g. <code>human_hero_1_spec_name</code> / <code>human_hero_1_spec_description</code>). Description text is heavy with <code>{0}</code>/<code>{1}</code> placeholders for stat values; the resolver substitutes via the standard pipeline before storing.
* '''<code>name</code> / <code>desc</code>''' carry the resolved English text inline. Translations live on the <code>{{TranslationDef | type=hero_specialization}}</code> row.
* '''No <code>hero_id</code> back-reference.''' The Hero → HeroSpecialization direction is sufficient (forward join via <code>Hero.specialization_id = HeroSpecialization.id</code>). Reverse queries — "which hero has this spec" — work via the same join. Per D-028.

== Related tables ==
* [[Template:HeroDef|Hero]] — joined on <code>id = Hero.specialization_id</code> (1:1 in practice; the schema permits N:1 in case a future patch shares specs across heroes).
* [[HeroSpecializationBonus]] — joined on <code>id = spec_id</code> (1:N).
* [[Template:TranslationDef|<code>TranslationDef</code>]] — one row per spec with <code>type=hero_specialization</code>, <code>target_id=id</code>.

== Notes ==

[[Category:Cargo Definitions]]
</noinclude><includeonly>{{#cargo_store:_table=HeroSpecialization
| id = {{{id|}}}
| name = {{{name|}}}
| desc = {{{desc|}}}
| name_sid = {{{name_sid|}}}
| desc_sid = {{{desc_sid|}}}
| icon = {{{icon|}}}
| source_path = {{{source_path|}}}
}}</includeonly>