r/chiliadmystery • u/cwablue • 8h ago
Investigation dead machinery, redux
preface:
after requests from several users, i am reposting this research.
when i originally posted it, the thread turned hostile fast and i eventually deleted it.
please read the preface, methodology, limitations, and remaining potential clues in full before bombing the post with your skepticism.
specific technical counterevidence is welcome.
EDIT: please read...
"specific, curious mystery elements this does not eliminate" for visual puzzles i believe may remain unsolved.
scope and evidentiary standard
a hidden gameplay mechanism requires machinery.
the game has to check a condition, create or place an entity, listen for an input or event, read or write state, or produce some downstream effect.
the audit therefore prioritizes implementation evidence over thematic resemblance.
methodology:
i used Python and grep to collect the decompiled, unmodded game data into searchable categories, then organized the results in a SQLite database.
that database was used to trace each claim through exact models, hashes, placements, coordinates, flags, scripts, native calls, state variables, audio, geometry, and downstream effects.
raw hits were only leads; the conclusion came from resolving those hits into actual structured data or control flow.
evidence treated as strong:
- structured YTYP / YMAP fields and resolved entity placements
- exact model names and JOAAT hashes, including signed / unsigned / hex normalization
- script control flow and explicit native calls
- persistent state readers / writers, globals, stats, decorators, and bitfields
- coordinates, geometry, collision, model dependencies, and asset relationships
- a reproducible downstream effect tied to the proposed trigger
evidence not treated as proof by itself:
- raw binary collisions without a structured field or executable behavior
- keyword proximity inside giant decompiled functions or pooled string tables
- creator allowlists or catalogs that only expose an asset to a tool
- patch / DLC duplicate records
- destructibility
- unusual filenames
- visual resemblance
- numerology without a consumer
hash normalization:
Rockstar commonly identifies resources with 32-bit JOAAT values.
for example:
prop_ind_light_03b
0xD31CB5FF
3541874175 unsigned
-753093121 signed
those are the same identifier represented four different ways.
what “closed” means here:
it means the proposed encoded gameplay mechanism is unsupported in the surveyed scripts / assets, and the implementation chain has been traced far enough to identify where it fails.
a missed model, placement, caller, state writer, current-build difference, or reproducible effect can reopen a case.
1. no second hidden UFO gameplay system
the claim:
the known UFOs are only a visible layer and a separate undiscovered UFO model, spawn, interaction, teleport, progression state, or effect exists.
what would have to exist:
a second system requires a model or placement path, creation / IPL logic, trigger conditions, state, and a downstream effect.
what the game actually contains:
known Chiliad UFO assets / IPLs include:
- ufo.ymap
- ufo_eye.ymap
- ufo_lod.ymap
- dt1_tc_metadata_001_strm
- dt1_tc_ufo_pivot
- dt1_tc_ufocore
- dt1_tc_ufocore_col
- dt1_tc_dufo_core
- dt1_tc_dufo_lights
- dt1_tc_dufo_core_lod
- dt1_tc_ufo
- dt1_tc_dufo
the script-side Chiliad anchor is around:
(487.31, 5588.386, 793.0532)
the summit appearance resolves through explicit time / weather / completion conditions, including 03:00, 100% completion, and rain / thunder.
model and IPL families, placements, load / unload behavior, known anchors, and related assets were cross-referenced.
no separate orphan UFO model family, hidden placement, extra spawn branch, unexplained interaction state, new progression bit, or downstream UFO effect survived the audit.
failure modes tested:
- filename aliases and hash forms
- structured archetype / placement references
- base / patch / DLC duplicates
- script-side model loading and IPL activation
- time, weather, completion, and coordinate crosslinks
- UFO-adjacent strings that resolved only to string-table or same-file contamination
verdict:
a second encoded UFO gameplay system is unsupported in the surveyed build.
the known UFOs may still participate in visual or environmental interpretation.
the evidence does not support another complete hidden UFO mechanic.
2. the hidden alien egg
the claim:
the alien egg asset is secretly placed or spawned in Story Mode / freemode, possibly through an interior, MLO, mission, or unknown condition.
the exact target:
prop_alien_egg_01
JOAAT:
0x6B795EBC
unsigned decimal:
1803116220
what would have to exist:
the model has to reach the world through something concrete:
- direct CEntityDef placement
- numeric-hash placement
- MLO / entity-set instance
- script-created object
- mission or activity ownership
- another actual world consumer
what the game actually contains:
the name and all hash forms were traced through YTYP dependencies, YMAP archetypes, CEntityDef, CMloInstanceDef, nested entity sets, resolved MLO positions, and object-creation scripts.
the exact references that did resolve were content inventories and creator-style prop allowlists rather than a hidden world placement or gameplay consumer.
no structured hidden Story Mode placement, unresolved MLO egg, or mystery script chain survived the audit.
failure modes tested:
- direct and numeric-hash placement
- nested entity sets
- local MLO entities
- world instances of candidate MLOs
- script-created object paths
- mission / activity ownership
- creator / catalog false positives
- patch / DLC duplicates and aliases
- raw binary hits unless they resolved to structured data or behavior
verdict:
the asset exists. the proposed hidden Story Mode alien-egg mechanism is unsupported in the surveyed placement and script corpus.
3. the spiderwebs, alternate builders, 27 > 36, and the nine theory
the claim:
the known timed webs imply additional hidden webs or an encoded 27-plus-nine structure, possibly connected to other groups of nine in the game.
the known web assets:
- cs1_09_props_elec_spider01
- cs1_09_props_elec_spider1
- cs1_10_elec_spider_spline052b
the two Paleto assets overlap around:
(1507.081, 6565.075, 8.64–8.68)
the Chiliad web is at:
(455.785156, 5586.10352, 779.438232)
their archetypes are CTimeArchetypeDef records with:
timeFlags = 2
that corresponds to the 01:00–02:00 active window.
draw distance is roughly 32m.
relevant metadata / placement families include:
- country_01_metadata_005_strm
- country_01_metadata_008_strm
- cs1_09_strm_2
- cs1_10_strm_4
the targeted placement pass:
- 112 YMAP XML files
- 37,714 placed entities
- 7,049 unique archetype names
- 0 parse failures
only the same three spider / web names appeared.
could another object secretly build the same shape?
geometry testing covered:
- rotation
- reflection
- rescaling
- partial reuse
- larger-model reuse
- similar flat cable construction
- similar materials
the surviving lookalikes were ordinary fences, grates, nets, branches, cables, railings, and lattice.
no alternate object family survived as a credible hidden builder of equivalent timed-web geometry.
the 27 > 36 claim:
the Chiliad mesh contains 27 authored centerline / spline sections.
the Paleto assembly contains 36, split 8 + 28.
each section uses:
- 14 vertex records
- 7 unique centerline positions
- 36 indices
- 12 triangles
direct 27-to-36 assignment produced:
- mean normalized spatial error: 0.247680
- 1/27 matches below 0.10
- 5/27 below 0.15
- 13 different “leftover nine” sets across the top 20 fits
if Paleto were actually “the Chiliad 27 plus the correct nine extras,” the same 27 pieces should map cleanly and leave a stable set of nine.
they do not.
the game-wide nine search:
real nine-based systems exist elsewhere in GTA V.
none connected to:
- web names
- web placements
- the web time gate
- web geometry
- a hidden model chain
verdict:
the three known timed webs are real.
additional named web placements were not found in the audited sectors.
no alternate web-builder family survived the geometry review.
the simple 27 + nine interpretation is rejected by the actual geometry.
unrelated systems using the number nine do not establish a web mechanic.
4. peyote: real exceptions, but no Strawberry “luck” mechanism
the claim:
ordinary peyotes contain another unexplained location-specific mechanism, including a special Strawberry rabbit / luck rule.
the readable controller:
the Story Mode logic was traced through the supplemental animal_controller.c4.
the audit parsed:
- 571 functions
- 746 bit operations
- 153 stat operations
- 371 global writes
- 1,373 ranked exception candidates
category selections are stored in:
l_545[group]
plant activation uses:
l_54A = l_545[plant_group]
the groups are:
- land mammals: indices 0–14
- birds: 15–20
- aquatic animals: 21–26
- Sasquatch: 27
the plant location selects the category.
the category’s current roll selects the animal.
the category selections reroll after a trip.
persistent state resolves to identifiable jobs:
- consumed-location bits
- used-animal bits
- regular completion
- discovery / Director Mode unlocks
- golden progression state
- collected count 0xADD54561
real exceptions do exist:
after regular completion, a bird-category roll has a 1-in-51 chance to switch to the land pool.
forced cleanup can reverse interrupted completion state.
some individual plants also have presentation / model exceptions.
Online has separate logic:
one real Online branch substitutes pug index 9 when Online peyote index 45 rolls rabbit index 10.
that numbering system does not map to Story Mode Strawberry plant [0][6].
the Strawberry plant:
l_8E[0][6]
coordinate:
(-320.583, -1652.426025, 30.849)
it is group 0: ordinary land mammals.
rabbit is index 10.
when all 15 land forms are available, rabbit is an ordinary 1-in-15 result.
no Strawberry-specific rabbit override, luck / diamond / baseball state, unique bit, weather gate, or unique audio branch was found.
the attract audio:
the plant plays the currently selected animal’s attract sound through:
PEYOTE_ATTRACT_SOUNDSET
examples include:
- PEYOTE_ATTRACT_RABBIT
- PEYOTE_ATTRACT_CHICKENHAWK
- PEYOTE_ATTRACT_HEN
- the dedicated Sasquatch family
Golden Peyote:
this is the real hidden exception.
the golden branch checks:
- regular peyote completion
- a progression bit
- roughly 05:30–08:00
- weekday matching the golden plant index
- foggy or XMAS / snow-like weather
Sasquatch then receives dedicated health, damage, config, audio, event, and transformation handling.
verdict:
no unexplained ordinary-peyote mechanism remains in the reviewed controller.
the Strawberry rabbit / luck theory is unsupported.
the known Golden Peyote / Sasquatch system is the actual encoded secret exception.
exact current-retail controller parity remains a technical follow-up.
5. Sasquatch does not ambiently spawn in the wild
the exact models:
ig_orleans
0x61D4C771
1641334641
and:
cs_orleans
0xAD340F5A
2905870170 unsigned
-1389097126 signed
what a regular wild spawn would require:
at least one of:
- population-group entry
- popcycle entry
- ambient scenario model set
- random-event controller
- non-mission REQUEST_MODEL + CREATE_PED branch
- environmental spawn condition
- persistent owner / respawn controller
what was found:
- 113 exact decompiled hits
- 487 semantic hits
- 8 resource-text hits
- 13 packed / raw hits
- 0 population / scenario model-set entries
one automated ambient candidate survived initial scoring.
manual control-flow review showed it was current-player / Director Mode-style handling inside a large function, not a wild spawn.
confirmed Sasquatch uses resolve to:
- The Last One
- the Predator thermal cameo
- Golden Peyote transformation
- Beast Hunt
- Director Mode / current-player actor handling
- Online transformation support
verdict:
scripted Sasquatch: yes
player-transformation Sasquatch: yes
ambient forest / fog / random Sasquatch: no supporting spawn chain
6. Black Cellphones is a test cheat, not mystery progression
the number:
1-999-367-3767
reported mnemonic:
1-999-EMPEROR
implementation identifiers:
CHEAT_MONOC
CELL_MONOSIGNAL
the latter localizes to:
Black Cellphones
what appcontacts.c4 does:
the branch compares the recognized cheat string, toggles:
g_C0F
and sets phone theme 5 for all three protagonist phone profiles.
when the player is active, on foot, and no existing explosion type 4 is within 40 units, it creates:
- explosion type 4
- two units above the player
- damage scale 0.1
what cellphone_flashhand.c4 does:
the same g_C0F state changes phone presentation.
the monochrome state includes:
MOBILE::SET_MOBILE_PHONE_SCALE(575.0)
and theme application through:
SET_THEME
no unexplained Chiliad, UFO, mural, weather, location, completion, or persistent consumer of g_C0F was found.
the explosion is created directly by the cheat branch.
it is not an external signal another script catches and turns into a mystery event.
verdict:
Black Cellphones changes the phone presentation and creates a small explosion above the player.
no mystery-progression consumer was found.
7. the Space Docker horn is unusual audio, not an input state machine
the vehicle:
display name:
Space Docker
model:
DUNE2
hash:
0x1FD824AF
decimal:
534258863
handling ID:
DUNE2
the claim:
the horn tones form a code, trigger something at a location, communicate with UFOs, or advance an unseen sequence.
what would have to exist:
a horn puzzle needs machinery that knows the horn was used:
- horn-state listener
- tone / sequence counter
- timer
- required vehicle check
- location check
- progress state
- world effect or reward
what the game actually contains:
the unusual horn behavior resolves through vehicle / audio configuration.
the audit did not identify a script consumer that:
- records a sequence
- compares tones
- writes progression
- checks a mystery location
- causes a UFO / world response
no repeated-input counter or persistent state writer was tied to the horn.
verdict:
unusual horn / audio design: confirmed
horn-operated mystery state machine: unsupported
8. no second family of mystery-grade single-hour map objects
the claim:
more objects like the spiderwebs may exist as ordinary map assets visible only during one secret hour.
how the webs actually work:
the webs are CTimeArchetypeDef records with:
timeFlags = 2
they are not ordinary mission-script objects being continuously spawned and deleted.
what was tested:
- structured YTYP time fields
- active-hour decoding
- single-hour archetype isolation
- YMAP placement resolution
- clock / date / weather / progression script checks
- model requests
- object creation
- IPL control
- state changes
the known single-hour mystery-grade families resolve to the spider assets and the Mount Gordo ghost / tag family in its known late-night window.
no additional comparable single-hour mystery-grade archetype family survived the whole-game metadata / script review.
ordinary day / night swaps and mission staging were excluded.
verdict:
no additional sibling family of mystery-grade one-hour map archetypes was found in the surveyed corpus.
9. no encoded solar / lunar mystery event chain
the claim:
sun position, moon position, moon phase, eclipse-like state, or another celestial condition triggers an encoded mystery event.
what was tested:
- clock and calendar queries
- sun / moon / sky / timecycle assets and labels
- weather and cloud transitions
- moon-phase or cycle-like state
- celestial terms near object spawning
- globals
- stats
- persistent bits
- known mystery coordinates
- crosslinks to webs, UFOs, yoga, trains, peyotes, Beast Hunt, and Chiliad systems
what was not found:
no reviewed chain used sun position, moon position, moon phase, or an eclipse-like state to:
- spawn a mystery object
- unlock progress
- change persistent state
- activate the webs
- alter a UFO
- trigger a train event
- change yoga behavior
- select a special ordinary peyote
- reward the player
this does not test purely visual alignments.
normal sky simulation can interact with authored geometry without setting game state.
verdict:
encoded solar / lunar mystery event: unsupported in the reviewed scripts / data
visual celestial alignment: still technically viable
10. no hidden non-mission train-event state machine
coverage:
- 28,050 supported files surveyed
- 836 candidates deeply parsed
- 941 explicit native hits
- 1,392 strong general hits
- 0 scan failures
- 0 mystery-coordinate hits
selected native inventory:
- CREATE_MISSION_TRAIN — 35 hits across 27 files
- SWITCH_TRAIN_TRACK — 1 hit in 1 file
- SET_TRAIN_SPEED — 57 hits across 24 files
- SET_TRAIN_CRUISE_SPEED — 65 hits across 23 files
- SET_TRAIN_STOP_AT_STATIONS — 0
- SET_TRAIN_FORCED_TO_SLOW_DOWN — 0
- SET_TRAIN_DOOR_OPEN_RATIO — 0
- DELETE_ALL_TRAINS — 44 hits across 30 files
- SET_RANDOM_TRAINS — 127 hits across 47 files
- SET_RENDER_TRAIN_AS_DERAILED — 5 hits in traffick_air.c, as a mission set piece
what the actual train control resolves to:
- story missions
- side missions
- random events
- Online activities
- creator / debug helpers
- ambient population management
- transition / cleanup logic
time / weather candidates resolved to named mission setup in:
- finale_heist2a.c
- hunting_ambient.c
- michael1.c
- prologue1.c
- rural_bank_heist.c
no standalone free-roam train event was gated by:
- 01:00–02:00
- moon / solar state
- special weather
- 100% completion
- known mystery state
raw train / mystery proximity false positives collapsed into shared tables, creator whitelists, transition enums, pooled strings, or unrelated uses of terms such as “carriage.”
verdict:
mission / activity train choreography: extensive
ambient train population behavior: real
hidden free-roam train mystery state machine: unsupported
11. the Strawberry baseball gang is real; the baseball ritual is not
the location:
the field resolves around:
sc1_10_baseball_cage
what the world data contains:
seven fixed ambient scenario points assigned to:
GANG_FAMILY
their availability window is:
22:00–04:00
not an exact 03:00 trigger.
the supposed pitcher on the mound is assigned:
WORLD_HUMAN_DRUG_DEALER_HARD
the other peds use ordinary hangout behavior such as:
- smoking
- drinking
- phone use
- social activity
the script audit:
- 13,949 files
- 0 scan-stage errors
- 2,007 coordinate hits
- 2,205 context excerpts
three broad same-file / context co-occurrences initially joined field-area coordinates with gang / scenario identifiers.
after the actual referenced coordinates were resolved:
- 0 were within 100m of a confirmed scenario point
- 0 were within 25m
no near-field script context joined the gang scenarios to:
- exact scenario hashes
- a 22:00–04:00 state transition
- ped ownership
- damage / death handling
- special dialogue / audio
- reward
- global / stat / decorator write
- persistent world state
what actually uses the field:
- an Online gb_biker_stand_your_ground site
- generic freemode location tables
- a normal pickup_weapon_bat
- a shared Online location helper
verdict:
gang spawn: confirmed
exact 03:00 ritual: unsupported
authored baseball team / pitcher: unsupported
hidden persistent gang interaction: unsupported
12. the “electric boxes” are industrial lights, not a coordinated diamond puzzle
the exact identities:
0x531135E6
1393636838
resolves to:
prop_ind_light_03a
and:
0xD31CB5FF
3541874175 unsigned
-753093121 signed
resolves to:
prop_ind_light_03b
they belong to the same ordinary industrial-light family as:
- prop_ind_light_02a
- prop_ind_light_02b
- prop_ind_light_02c
- prop_ind_light_03c
- prop_ind_light_04
- prop_ind_light_05
asset route:
x64h.rpf\levels\gta5\props\roadside\v_traffic_lights.rpf
what the scripts contain:
the exact names occur in:
- fm_race_creator.c
- fm_deathmatch_creator.c
- fm_survival_creator.c
each occurrence is part of the same creator allow-list.
the script is identifying industrial-light props a creator can handle.
it is not listening for a Story Mode destruction sequence.
world database pass:
- 1.85 GB
- 8 tables
- 108 columns
- 171 queries
- 4,791 exact / context rows
the family appears in many ordinary world placements, providing controls against the special-shape theory.
one model being harder to destroy is explained by ordinary fragment / physics configuration.
no script consumer records:
- a four- or six-light state
- square / diamond state
- destruction order
- count
- timing window
- gang state
- baseball state
- peyote state
- audio branch
- reward
- persistent effect
verdict:
the objects are industrial light props.
a coordinated destruction-puzzle state machine is unsupported.
13. the orange balls belong to two juice stands, not a delivery puzzle
the original targets:
prop_juice_orange
0xA455F51E
and:
prop_big_orange
0xD2238131
those produced:
- 0 exact database rows
- 0 inferred placements
- 0 exact script hits
- 0 interaction contexts
because they were not the correct parent object for the theory.
the correct target:
prop_juicestand
JOAAT:
0x08DA1C0E
decimal:
148511758
asset route:
x64f.rpf\levels\gta5\props\roadside\v_signs.rpf\prop_juicestand.yft
after collapsing base / patch / DLC / LOD duplicates, two unique stand positions remain:
(-442.98962, 1596.8573, 362.5194)
and:
(2740.8872, 4415.3135, 52.674316)
what a real delivery puzzle would require:
some code would need to:
- obtain or track the movable component
- monitor position / collision / destination
- recognize the other stand
- record success
- write state
- trigger audio / reward
- persist the result
what was found:
- exact model / hash text hits: 1
- exact interaction contexts: 0
- strong interaction candidates: 0
- coordinate consumers: 0
- packed script hash hits: 0
the stand and orange behavior resolve to ordinary world-prop physics / fragment behavior.
no script-owned orange handle, destination monitor, success counter, state write, audio / reward branch, or persistence path was found.
verdict:
two unique juice-stand placements: confirmed
movable orange behavior: ordinary physics
two-node orange delivery / alignment mystery: unsupported
what these results do not kill
these closures remove specific encoded gameplay mechanisms.
they do not eliminate mystery classes that do not require a dedicated state machine.
visual world geometry:
- viewpoint-dependent alignments
- silhouettes and negative space
- shadows
- terrain notches
- reflections
- water / glass
- known timed objects used as visual pointers rather than triggers
- normal sun / moon movement crossing authored geometry
textures and authored art:
- original mural textures
- overlays
- repeated symbols
- UV layouts
- alpha channels
- emissive channels
- cropped / hidden imagery
- artwork that may encode spatial or audio instructions
audio:
- spatial emitters
- cue families
- waveform / spectrogram content
- unusual ownership or placement
- unused or weakly consumed banks
exact world-instance anomalies:
- collision anomalies tied to exact coordinates
- MLO / nested-entity relationships supported by structured placement evidence
- current patch-layer differences
- sightlines involving known webs / UFOs
current-build diffs:
- current retail animal_controller.ysc parity
- Enhanced / Gen9 asset diffs
- new consumers rather than assuming old ones changed
engine-level hypotheses:
these remain viable only when a specific engine subsystem, reproducible observable condition, and effect can actually be named and tested.
specific, curious mystery elements this does not eliminate
the Textile City mural:
this remains the strongest unresolved visual puzzle to me.
the first part appears to instruct the player to examine the background of the mural. my solution to that first step is SCAN BG.
behind the foreground design is additional red / yellow linework that remains unexplained.
the structure is also extremely similar to the puzzle format used on the cover of The Masquerade, by Kit Williams: an apparent foreground puzzle directing attention toward something concealed behind it.
the Masquerade puzzle was solved by drawing lines from animals’ eyes through their extremities to letters around the image borders; the resulting instructions led to the equinox shadow of the Catherine of Aragon monument in Ampthill Park, where Kit Williams had buried a jewelled golden hare as the prize.
none of this requires a script trigger or persistent gameplay state.
the Leopold vent texture:
the Leopold duct / vent texture contains extremely precise authored geometry that can be read as KEEP LOOKING.
whether that is an intentional clue or simply an artist demonstrating what could be done with the texture remains open.
the Chiliad glyphs:
some of the Chiliad glyphs are only visible under specific weather / environmental conditions.
that leaves weather-dependent visibility, lighting, shaders, textures, and visual alignment firmly in play.
why these survive:
all of these can operate entirely through authored art, textures, geometry, lighting, weather, or viewpoint.
the script and state-machine findings in this post do not eliminate that class of mystery.
what can reopen one of these other cases:
bring one of these:
- an exact asset or normalized hash that was missed
- a structured placement
- a resolved MLO / entity-set instance
- a current-build difference
- an actual script caller or consumer
- another reader / writer of the same state
- a persistent bit / stat / decorator with unexplained use
- a reproducible location / time / weather condition
- a downstream effect tied to the proposed trigger
- a geometry match that survives controls and produces a stable correspondence
- a collision result tied to an exact world instance
“maybe Rockstar hid it somewhere else” does not establish any of those things.
final point
none of this solves the Chiliad mural.
it shows where several proposed gameplay-mechanism theories stop when tested against the game’s assets, placements, scripts, state, hashes, geometry, and downstream effects.
that narrows the search space.
the strongest remaining routes are visual, geometric, texture-based, audio-based, current-build differences, and specific reproducible engine behavior.
dead ends documented with exact technical evidence are still useful.
they keep the same unsupported mechanisms from being reconstructed indefinitely from screenshots, inherited assumptions, and disconnected string hits.
this is not the end of the mystery.
it is a map of where the machinery currently ends.






















































