Problem in the supplied instructions
The original how-to adds an IsBoss branch after IsEnemy. Bosses already satisfy IsEnemy, so the later else-if does not assign them to the boss-marker vector. M2City r1 routes enemies inside the existing branch: bosses go to m_BossPositionVector and ordinary enemies to m_MonsterPositionVector. Embedded invisible BOM characters were removed from the instructions.

Behavior and integration
This copy defines a boss as mob rank at least 4, mob type 0 and not a stone. It marks nearby instantiated enemies; it does not discover every boss spawn on the whole map, expose respawn timers or create a server boss tracker.
Merge the InstanceBase predicate/name-color enum, Python export, minimap vector/render block and colorInfo/introLoading registrations. Place NAMECOLOR_BOSS before NAMECOLOR_NUM and initialize its color. Clear the boss vector at every matching minimap reset/rebuild/Destroy site, not only once. Review custom rank/type values and hidden/minimap visibility rules in your fork. The default color is blue and is configurable in colorInfo.py.

Validation
The single supplied how-to was read. The exact revised routing and IsBoss logic compiled under C++11 with fake tables and passed rank thresholds, missing mob table, stone exclusion, other mob type, boss/ordinary-enemy routing and non-enemy cases. There was no Direct3D rendering, actual client build or live spawn test. Keep the previous binary/root available for rollback; no invented creator/version is assigned.

Editorial resource — M2City
Version: Legacy integration fragments; exact fork unspecified; M2City r1 (2026-11-04)
Rights: Public redistribution confirmed by owner; upstream notices retained. No blanket open-source relicensing.
Validation: Exact reviewed logic compiled with clang++ C++11 and passed isolated fake-engine assertions. No complete binary build/gameplay test.
Source: Owner-supplied source; public creator/feature reference where established
SHA-256: 4ac4739579a74576b18860e89ee050ce457f1fec38f9080c802b19372f0c2403