Keep Sprite Equipment Attached When Facing Left

Store an equipment socket in a declared character coordinate space and mirror it exactly once. Texture flipping, transform mirroring and atlas trimming affect different parts of that calculation. A weapon that stays on the wrong side after turning often reveals an unclear coordinate contract rather than bad animation artwork.

Key Takeaways

• Record sockets against the original frame canvas, with an explicit origin and units.
• Separate texture-only flipping from mirroring a visual parent and its children.
• Test an off-center socket and multiple trim offsets before using production art.

The method below assumes a 2D character with frame-based artwork. It defines its own mathematical convention instead of claiming that every engine uses the same pivot or flip behavior. Adapt the conversion at the importer boundary.

Write the coordinate contract before the code

For this example, the original canvas is 64 × 64 units, with its top-left edge at (0, 0), positive X to the right and positive Y downward. Coordinates are continuous edge coordinates: the right edge is X = 64. The character's local origin is an anchor at (32, 56) in that canvas. A hand socket sits at (46, 28).

Therefore the unmirrored socket relative to the character origin is (14, -28). These values are a synthetic fixture, not measurements from a shipped asset. With the character origin at world position (100, 200) and no rotation or scale, the socket is at (114, 172).

Do not mix this convention with integer pixel indices. A mirrored pixel index uses W - 1 - x; a continuous point mirrored across the center of a canvas uses W - x. For a general anchor, reflecting a local offset around that anchor is simpler: negate its local X. Mirroring around the character anchor is not always the same as mirroring around the canvas center.

Keep trimming out of the logical socket

Two trimmed frames may place the same logical hand at different positions in their stored rectangles. Suppose frame A has trim origin (8, 4) and frame B has (12, 2). The stored socket coordinates are (38, 24) and (34, 26), respectively. Adding the corresponding trim origins restores (46, 28) in both cases.

Prefer storing the logical coordinate directly when the delivery format permits it. If the exporter stores a trimmed coordinate, include the translation needed to reconstruct the original one. PixiJS's texture model distinguishes original dimensions, trim metadata and texture frames; those fields should not be treated as interchangeable coordinates.

Rotated atlas entries require their documented rotation conversion before this translation. The table deliberately excludes packing rotation so the first fixture isolates trimming and mirroring.

Choose one mirroring owner

There are two valid designs, but combining them blindly mirrors the socket twice.

In a visual-parent design, place the character artwork and attachment socket under the same visual transform. A horizontal scale of -1 on that parent mirrors both local positions. Leave the socket's local X at 14; do not negate it again. Keep gameplay movement and collision ownership outside that visual subtree when they should not inherit the reflection.

In a texture-only design, flip the character image and explicitly compute the attachment's facing-dependent local position. In Godot, Sprite2D.flip_h is documented as flipping the texture. Node2D describes parent transforms that move, rotate and scale children. Do not assume a texture flip is equivalent to a negative parent scale.

For the defined anchor-space fixture, the left-facing socket offset is (-14, -28), yielding world position (86, 172). Decide separately how the weapon's image, its own grip anchor and its draw order respond to facing. Correct socket placement does not automatically orient a sword blade correctly.

Run the acceptance test before adding animation

Use a visible cross at the socket and a small asymmetric test weapon. First freeze frame A. Record right-facing (114, 172) and left-facing (86, 172). Then switch to frame B without moving the character. The socket should remain at those same world positions because the original-canvas hand coordinate did not change.

This illustrative calculation checks the translation contract independently of an engine:

anchor, world = (32, 56), (100, 200)
for trim, stored in [((8, 4), (38, 24)), ((12, 2), (34, 26))]:
    original = tuple(a + b for a, b in zip(trim, stored))
    local = tuple(a - b for a, b in zip(original, anchor))
    assert original == (46, 28) and local == (14, -28)
    assert (world[0] + local[0], world[1] + local[1]) == (114, 172)
    assert (world[0] - local[0], world[1] + local[1]) == (86, 172)

After that passes, add rotation, parent scale and animated socket movement individually. A following weapon that lags by one update may instead have a transform-propagation timing problem. A jump on detach needs a local-to-global reparenting check. For grouped sprites, verify whether member positions are local or world coordinates.

Reject an incomplete socket timeline

Correct coordinates on frame A do not repair a missing socket on frame B. Define the required (action, frame ID, socket ID) keys from the exported animation's actual frame IDs, then compare them with the socket records before playing it. This independent illustrative guard deliberately omits one required key:

expected = {('attack', frame, 'hand') for frame in ['A', 'B']}
actual = {('attack', 'A', 'hand')}
missing = expected - actual
assert missing == {('attack', 'B', 'hand')}

For this fixture, reject the handoff with the exact missing key. If production intentionally holds a socket from the previous pose, encode that policy explicitly instead of using accidental stale state. Validate duplicate keys before constructing a dictionary, because a dictionary can hide an overwritten record.

Approve the attachment only after both facings, both trim cases and the actual runtime hierarchy pass. The arithmetic validates this coordinate convention; it does not prove an importer, physics shape or every attachment animation implements it.

Evidence and editorial responsibility

FrameSprite Engineering prepared this AI-assisted guide using primary engine documentation and a synthetic coordinate fixture. The team has a commercial interest in FrameSprite. No engine execution or production attachment test is claimed. Editorial ownership and contact.