Skip to content

The problem of duplicate input settings #559

@jzy-chitong56

Description

@jzy-chitong56

As I mentioned before

Human buildings are repeated in the standard unit table

now I have found more repetitive definitions and try Equivalence

SANCTUM	AI_COMP	ARCANE_SANCTUM	0	0
CORRUPT_WELL	AI_COMP	MOON_WELL	0	0             ------  This is to enable WELL JOB  can use CORRUPT_WELL
ELF_GUARD_TOWER	AI_COMP	HIGH_TOWER	0	0
ALCHEMIST	AI_COMP	ALCHEMIST_M3	0	0             ------  act as  ALCHEMIST  M1 M2 M3  --   tc_add3
NAGA_DRAGON	AI_COMP	NAGA_SNAP_DRAGON	0	0
NAGA_SERPENT	AI_COMP	NAGA_COUATL	0	0
NAGA_WITCH	AI_COMP	NAGA_SIREN	0	0
NAGA_HYDRA	AI_COMP	NAGA_TURTLE	0	0

Firstly, I don't quite understand why these Naga units need to be defined twice on standard unit table
And then I don't know how to define this equivalence anymore
like you see
ELF_GUARD_TOWER tc HIGH_TOWER
NAGA_ tc NAGA_

Actually, I also want to do ZEPPLIN tc UD_ZEPPLIN
then save job and follow JOB can use UD_ZEPPLIN


Then there was an error when compiling the report , I understand that it can't be written like this

The following are repeated definitions

globals

#INCLUDETABLE <$VER$\UnitEquivalence.txt> #EFR #COND "%2" eq "AI_COMP"
  integer %3 = %1
  integer o%3 = o%1
#ENDINCLUDE
InitAiUnits
...
#INCLUDETABLE <$VER$\UnitEquivalence.txt> #EFR #COND "%2" eq "AI_COMP"
		set %3 = %1
#ENDINCLUDE

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions