A coordinate can be local to a map, global after a base offset, or expressed in a different unit from another file. A copied number may be correct in one representation and wrong in another. Label the coordinate system before converting it.
Write the inputs down
Record the map's base/origin, map dimensions, the source of the coordinate and the units expected by the target file. Keep the map's settings, atlas entry and regen file together while investigating. A coordinate from a minimap tooltip should not automatically be treated as the same representation as a raw base-position field.
Illustrative arithmetic using the SAME invented unit throughout:
map origin = (1000, 2000)
local point = ( 120, 80)
global point = (1120, 2080)
If a separate representation uses 100 sub-units per unit,
convert at its boundary once. This is a model, not a
universal declaration of every file format's units.Check the other causes
A valid point can still produce a confusing result if the spawn has a non-zero range, the selected map settings are wrong, the placement is blocked, or the server loads a different copy of the regen file. Start with one known mob, a narrow range and a known walkable location in staging.
Make the result reproducible
Include the map setting/atlas values, the spawn line, where the point was read from and where the entity appeared. State whether your editor already applied the base offset. The M2City Regen Editor can help inspect a map workflow, but importing a file is not proof that every source uses the same coordinate representation.
Reference
A spawn-configuration tutorial supplies historical context for coordinates and ranges. The explicitly labelled arithmetic example here is original and deliberately avoids treating an undocumented scaling convention as universal.