Template:EnemyData - Revision history

>Eave: run name through override parser before storing - this is to handle disambiguation cases as well as cases where the enemy does not have a name in the data

2020-05-08T09:09:06Z

run name through override parser before storing - this is to handle disambiguation cases as well as cases where the enemy does not have a name in the data

>Eave: run name through override parser before storing - this is to handle disambiguation cases as well as cases where the enemy does not have a name in the data

2020-05-08T09:09:06Z

run name through override parser before storing - this is to handle disambiguation cases as well as cases where the enemy does not have a name in the data

>Eave: run name through override parser before storing - this is to handle disambiguation cases as well as cases where the enemy does not have a name in the data

2020-05-08T09:09:06Z

run name through override parser before storing - this is to handle disambiguation cases as well as cases where the enemy does not have a name in the data

>Eave: removing EnemyGroupName

2020-04-26T00:31:24Z

removing EnemyGroupName

>Eave: removing EnemyGroupName

2020-04-26T00:31:24Z

removing EnemyGroupName

>Eave: removing EnemyGroupName

2020-04-26T00:31:24Z

removing EnemyGroupName

>Eave: s/EnemyGroupName/ModelId - enemygroupname alone is insufficient to determine the model id, so we'll just push that logic into the parser level

2020-04-19T10:48:31Z

s/EnemyGroupName/ModelId - enemygroupname alone is insufficient to determine the model id, so we'll just push that logic into the parser level

>Eave: s/EnemyGroupName/ModelId - enemygroupname alone is insufficient to determine the model id, so we'll just push that logic into the parser level

2020-04-19T10:48:31Z

s/EnemyGroupName/ModelId - enemygroupname alone is insufficient to determine the model id, so we'll just push that logic into the parser level

>Eave: s/EnemyGroupName/ModelId - enemygroupname alone is insufficient to determine the model id, so we'll just push that logic into the parser level

2020-04-19T10:48:31Z

s/EnemyGroupName/ModelId - enemygroupname alone is insufficient to determine the model id, so we'll just push that logic into the parser level

>Eave: add EnemyGroupName field for 3d model name reasons

2020-04-18T06:19:13Z

add EnemyGroupName field for 3d model name reasons

@@ Line 53: / Line 53: @@
 _table=EnemiesTest
 |MonsterId={{{Id|}}}
-|Name={{{Name|}}}
+|Name={{EnemyData/NameOverrides|Name={{{Name|}}}|DataId={{{DataId|}}}|ElementalType={{{ElementalType}}}}}
 |DataId={{{DataId|}}}
 |ModelId={{{ModelId|}}}

@@ Line 56: / Line 56: @@
 |DataId={{{DataId|}}}
 |ModelId={{{ModelId|}}}
 |RareStayTime={{{RareStayTime|}}}
 |HP={{{HP|}}}

@@ Line 6: / Line 6: @@
 |Name=String
 |DataId=String
-|EnemyGroupName=String
+|ModelId=String
 |RareStayTime=Integer
 |HP=Integer
@@ Line 55: / Line 55: @@
 |Name={{{Name|}}}
 |DataId={{{DataId|}}}
-|EnemyGroupName={{{EnemyGroupName|}}}
+|ModelId={{{ModelId|}}}
 |RareStayTime={{{RareStayTime|}}}
 |HP={{{HP|}}}

← Older revision	Revision as of 09:09, 8 May 2020
(No difference)

← Older revision	Revision as of 00:31, 26 April 2020
(No difference)

← Older revision	Revision as of 10:48, 19 April 2020
(No difference)

← Older revision	Revision as of 06:19, 18 April 2020
(No difference)