Encounter map
Where to find Pin
Random boss poolsPin appears in 1 random floor pool. The weights below are relative to the other entries in each pool, not a guaranteed encounter chance.
Compare bosses in cellarFight guide · Cellar
How to fight Pin
Pin alternates between a jump toward Isaac and a brief emergence to spit an explosive shot.
Normal boss behavior in Repentance. Champion variants can change these patterns.
Before entering
Give yourself space to dodge sideways. Attack when Pin emerges instead of chasing its underground position.
- 1
Burrowing jump
Watch for: Pin bursts from the ground toward Isaac before diving underground again.
Try: Move across the jump's path rather than trying to outrun it in the same direction.
- 2
Airborne shots
Watch for: In Repentance, medium and long jumps release diagonal projectiles; long jumps add a second burst.
Try: Keep watching the airborne body after your first dodge so the extra shots do not catch you.
- 3
Explosive spit
Watch for: Pin partly emerges to launch an explosive projectile, then jumps from that same spot afterward.
Try: Leave space around the projectile's landing area and prepare for the next jump from its firing position.
Game-file pools
Spawn entries
Game-file referenceRaw data and official artEntity fields, portrait files, and source notes for this boss.
Raw entity values
Health and entity data
- Base HP
- 100
- Stage HP scaling value
- 0
- Entity ID and variant
- 62.0
- Contact damage field
- 1
These are raw entity fields. Armor, floor scaling, phase transitions, shared health, and scripted waves can make the fight differ from the base HP value.
Asset mapping
Official portrait assets
The Pin versus-screen portrait comes from the supplied game art. The original filenames are retained below.
- Portrait file
- Portrait_62.0_Pin.png
- Boss-name image file
- BossName_62.0_Pin.png
Source notes
How this record is built
Boss identity and portrait metadata come from bossportraits.xml. Random floor membership, weights, and Double Trouble room IDs come from bosspools.xml. Health and entity fields come from entities2.xml. Fixed story locations and route explanations are reviewed editorial context.