Humans can become Raytraxians through several kinds of interaction: environmental hazards, transmogrifying items, contact or conversion by another Raytraxian, event-specific objects, and authorized private-server controls. Identify the route and event state before attempting it because similar-looking objects can produce different forms.
Choose a transformation route
Environmental transformations
Start in a fresh server and identify the room. Approach one object only. Community guidance associates Crystal Chasm crystals with Kaiju routes and Flooded Area fins with Shork-related outcomes, but exact contacts and variants can change.
Record the object’s color, model, event state, and result. Do not mix a crystal touch with another Raytraxian’s attack and then attribute the result to one source. If you want to remain Human, treat unidentified hazards as unsafe.
The Hazard Locations guide maps risk types without promising fixed spawn coordinates.
Transmogrifying items
Community examples include Orange Bucket for Catte, Fedora for Fed, Hazmat Suit interactions associated with Hazzy, and ice cream associated with Sprinklekit. Other documented names include Lemon Slice, Blue Soap, Strange Crystal, Shades, Strange Flower or Fruit, Taser, Toxic Barrel, and Witchbrew-related objects.
The community item page is marked work in progress. Use Transmogrifying Items to check current status and never assume a historical exact use count. Some items may transform an existing Raytraxian rather than a Human.
Infection or conversion by players
If another Raytraxian grabs or converts you, note the attacker’s form and the final UI name. Team pressure can make it hard to identify which interaction completed the change, so use a controlled private-server test for exact acquisition evidence.
After becoming a Raytraxian, stop using the Human route. Read the action bar, identify teammates and exits, and check whether the form has unique movement or abilities. The Raytraxian Combat guide gives the role reset.
Event-exclusive transformations
Power Outage and Blackout change the facility and can expose different forms or objects. Confirm the event through lighting, electronics, barriers, doors, buttons, UI, and event banner. Do not wait for an old interval.
Community groups currently place Manic, Dagoda, Melon Shork, and Saturn under Power Outage; Hebi, Buck, Jammer, Night Shade, Nightcrawler, Nuclear Rabbit, Sinox, and Wisp under Blackout. These are working lists, not guaranteed complete totals.
Protection and special cases
Community documentation describes the Hazmat Suit as protection from many hazards or transmogrifying items, while infection under certain conditions can lead to Hazzy. Exact protection coverage is a live field. Test one hazard at a time and do not assume the suit protects from another player.
Nightcrawler also has route-specific behavior. Community documentation distinguishes goggled Nightcrawler from a mutation or minion outcome. Read Nightcrawler before testing.
Verification record
For each route, record source type, object or attacker, room, event, Human state, use count if visible, resulting form, action bar, server date, and confidence. Mark the result Community corroborated until a controlled current test reproduces it.
The official experience confirms that players fight against or as Raytraxians. Detailed transformation routes are community reported or corroborated, checked August 13, 2026. Exact contact counts, timers, chances, and complete immunity rules are not guessed.
Failed transformation troubleshooting
If a reported route does not work, confirm that you began as the intended role, the event is active, the object has not already been consumed, and the server is current. Remove protective equipment when testing a direct item route only if it is safe and intentional. Rejoin before changing more than one variable. A failed result can mean an outdated route, wrong variant, private-server difference, cooldown, prior contact, or event requirement; it does not automatically prove the item is decorative. Record the exact failure message or lack of response and leave the outcome unverified until another controlled attempt agrees.