Cartel Enforcer

no candidatemember

Nothing on this build to point it at.

method missing, with nothing on this type to point at

207 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

207 reports

refusedmember

There was a candidate on this build and Polyfill did not trust it enough to use it.

AddSpeedControl is overloaded here, so which one it became is not decidable

206 reports

no candidatemember

Nothing on this build to point it at.

method missing, with nothing on this type to point at

202 reports

no candidatemember

Nothing on this build to point it at.

method missing, with nothing on this type to point at

202 reports

no candidatemember

Nothing on this build to point it at.

method missing, with nothing on this type to point at

202 reports

no candidatemember

Nothing on this build to point it at.

method missing, with nothing on this type to point at

202 reports

no candidatemember

Nothing on this build to point it at.

method missing, with nothing on this type to point at

202 reports

no candidatemember

Nothing on this build to point it at.

method missing, with nothing on this type to point at

202 reports

no candidatemember

Nothing on this build to point it at.

method missing, with nothing on this type to point at

202 reports

no candidatemember

Nothing on this build to point it at.

method missing, with nothing on this type to point at

202 reports

refusedtype

There was a candidate on this build and Polyfill did not trust it enough to use it.

its name changed, and Il2Cpp.GUIDManager is sealed, so nothing can stand in for it

5 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

5 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

mono-builtThe method is there and unchanged - `public virtual void Equip(Avatar _avatar)` at AvatarEquippable.cs:61 in 0.4.5f2 and :60 in 0.4.6. What does not match is the argument: the mods name ScheduleOne.AvatarFramework.Avatar, the Mono type, where an IL2CPP build has Il2CppScheduleOne.AvatarFramework.Avatar. Nothing Polyfill puts in the game answers a reference to the Mono surface.

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

refusedmember

There was a candidate on this build and Polyfill did not trust it enough to use it.

its answer cannot be handed back under the old name: Il2CppObjectBase.Pointer is not on it

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

5 reports

refusedmember

There was a candidate on this build and Polyfill did not trust it enough to use it.

its answer cannot be handed back under the old name: Il2CppObjectBase.Pointer is not on it

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

refusedmember

There was a candidate on this build and Polyfill did not trust it enough to use it.

ChangeInfluence is overloaded here, so which one it became is not decidable

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

field missing; 2 members could be meant, so none is chosen

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

refusedmember

There was a candidate on this build and Polyfill did not trust it enough to use it.

RemoveCustomer is overloaded here, so which one it became is not decidable

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

refusedmember

There was a candidate on this build and Polyfill did not trust it enough to use it.

its answer cannot be handed back under the old name: Il2CppObjectBase.Pointer is not on it

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

refusedmember

There was a candidate on this build and Polyfill did not trust it enough to use it.

its answer cannot be handed back under the old name: Il2CppObjectBase.Pointer is not on it

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

refusedmember

There was a candidate on this build and Polyfill did not trust it enough to use it.

ExitBuilding is overloaded here, so which one it became is not decidable

5 reports

refusedmember

There was a candidate on this build and Polyfill did not trust it enough to use it.

PlayVO is overloaded here, so which one it became is not decidable

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

field missing; 2 members could be meant, so none is chosen

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

refusedmember

There was a candidate on this build and Polyfill did not trust it enough to use it.

its answer cannot be handed back under the old name: Il2CppObjectBase.Pointer is not on it

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

5 reports

refusedmember

There was a candidate on this build and Polyfill did not trust it enough to use it.

its answer cannot be handed back under the old name: Il2CppObjectBase.Pointer is not on it

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

refusedmember

There was a candidate on this build and Polyfill did not trust it enough to use it.

its answer cannot be handed back under the old name: Il2CppObjectBase.Pointer is not on it

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

refusedmember

There was a candidate on this build and Polyfill did not trust it enough to use it.

nothing stands in for any type in its signature, so putting the name back a second time would only duplicate it

5 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

field missing; 2 members could be meant, so none is chosen

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

refusedmember

There was a candidate on this build and Polyfill did not trust it enough to use it.

its answer cannot be handed back under the old name: Il2CppObjectBase.Pointer is not on it

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

field missing; 2 members could be meant, so none is chosen

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatefield

Nothing on this build to point it at.

the field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

no-stand-inthe field became a property, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on

5 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

5 reports

refusedmember

There was a candidate on this build and Polyfill did not trust it enough to use it.

IsPlayerVisible is overloaded here, so which one it became is not decidable

5 reports

no candidatetype

Nothing on this build to point it at.

type no longer exists in Assembly-CSharp; 2 types share the name Avatar, so which one it became is not decidable here

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.AvatarFramework.Avatar was compiled against the other branch.

5 reports

refusedtype

There was a candidate on this build and Polyfill did not trust it enough to use it.

its name changed, and Il2CppScheduleOne.AvatarFramework.AvatarSettings/LayerSetting is sealed, so nothing can stand in for it

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.AvatarFramework.AvatarSettings/LayerSetting was compiled against the other branch.

5 reports

refusedtype

There was a candidate on this build and Polyfill did not trust it enough to use it.

its name changed, and Il2CppScheduleOne.AvatarFramework.Eye/EyeLidConfiguration is not a class

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.AvatarFramework.Eye/EyeLidConfiguration was compiled against the other branch.

5 reports

no candidatetype

Nothing on this build to point it at.

type no longer exists in Assembly-CSharp; 2 types share the name Console, so which one it became is not decidable here

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Console was compiled against the other branch.

5 reports

refusedtype

There was a candidate on this build and Polyfill did not trust it enough to use it.

its name changed, and Il2CppScheduleOne.DevUtilities.NetworkSingleton`1 is generic

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.DevUtilities.NetworkSingleton`1 was compiled against the other branch.

5 reports

refusedtype

There was a candidate on this build and Polyfill did not trust it enough to use it.

its name changed, and Il2CppScheduleOne.DevUtilities.PlayerSingleton`1 is generic

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.DevUtilities.PlayerSingleton`1 was compiled against the other branch.

5 reports

no candidatetype

Nothing on this build to point it at.

type no longer exists in Assembly-CSharp; 2 types share the name Singleton`1, so which one it became is not decidable here

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.DevUtilities.Singleton`1 was compiled against the other branch.

5 reports

no candidatetype

Nothing on this build to point it at.

type no longer exists in Assembly-CSharp

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Dialogue.DialogueContainer was compiled against the other branch.

5 reports

no candidatetype

Nothing on this build to point it at.

type no longer exists in Assembly-CSharp; 2 types share the name Draggable, so which one it became is not decidable here

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Dragging.Draggable was compiled against the other branch.

5 reports

no candidatetype

Nothing on this build to point it at.

type no longer exists in Assembly-CSharp; 2 types share the name CustomerData, so which one it became is not decidable here

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Economy.CustomerData was compiled against the other branch.

5 reports

refusedtype

There was a candidate on this build and Polyfill did not trust it enough to use it.

its name changed, and Il2CppScheduleOne.Economy.StandardsMethod is sealed, so nothing can stand in for it

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Economy.StandardsMethod was compiled against the other branch.

5 reports

refusedtype

There was a candidate on this build and Polyfill did not trust it enough to use it.

its name changed, and Il2CppScheduleOne.GameTime.GameDateTime is not a class

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.GameTime.GameDateTime was compiled against the other branch.

5 reports

no candidatetype

Nothing on this build to point it at.

type no longer exists in Assembly-CSharp; 2 types share the name TimeManager, so which one it became is not decidable here

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.GameTime.TimeManager was compiled against the other branch.

5 reports

refusedtype

There was a candidate on this build and Polyfill did not trust it enough to use it.

its name changed, and Il2CppScheduleOne.Levelling.FullRank is not a class

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Levelling.FullRank was compiled against the other branch.

5 reports

no candidatetype

Nothing on this build to point it at.

type no longer exists in Assembly-CSharp; 3 types share the name Map, so which one it became is not decidable here

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Map.Map was compiled against the other branch.

5 reports

no candidatetype

Nothing on this build to point it at.

type no longer exists in Assembly-CSharp; 5 types share the name Message, so which one it became is not decidable here

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Messaging.Message was compiled against the other branch.

5 reports

refusedtype

There was a candidate on this build and Polyfill did not trust it enough to use it.

its name changed, and ScheduleOne.Messaging.Message, which it was nested in, is not in this assembly

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Messaging.Message/ESenderType was compiled against the other branch.

5 reports

no candidatetype

Nothing on this build to point it at.

type no longer exists in Assembly-CSharp; 4 types share the name Behaviour, so which one it became is not decidable here

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.Behaviour.Behaviour was compiled against the other branch.

5 reports

no candidatetype

Nothing on this build to point it at.

type no longer exists in Assembly-CSharp; 2 types share the name Ray, so which one it became is not decidable here

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.CharacterClasses.Ray was compiled against the other branch.

5 reports

no candidatetype

Nothing on this build to point it at.

type no longer exists in Assembly-CSharp; 2 types share the name Appearance, so which one it became is not decidable here

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.Framework.Appearance was compiled against the other branch.

5 reports

no candidatetype

Nothing on this build to point it at.

type no longer exists in Assembly-CSharp; 4 types share the name Behaviour, so which one it became is not decidable here

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.Framework.Behaviour was compiled against the other branch.

5 reports

no candidatetype

Nothing on this build to point it at.

type no longer exists in Assembly-CSharp; 2 types share the name NPCData, so which one it became is not decidable here

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.Framework.NPCData was compiled against the other branch.

5 reports

no candidatetype

Nothing on this build to point it at.

type no longer exists in Assembly-CSharp; 15 types share the name Entry, so which one it became is not decidable here

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Product.ProductList/Entry was compiled against the other branch.

5 reports

no candidatetype

Nothing on this build to point it at.

type no longer exists in Assembly-CSharp; 2 types share the name Contract, so which one it became is not decidable here

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Quests.Contract was compiled against the other branch.

5 reports

no candidatetype

Nothing on this build to point it at.

type no longer exists in Assembly-CSharp; 2 types share the name Registry, so which one it became is not decidable here

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Registry was compiled against the other branch.

5 reports

no candidatetype

Nothing on this build to point it at.

type no longer exists in Assembly-CSharp

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.UI.Handover.HandoverScreen/EHandoverOutcome was compiled against the other branch.

5 reports

no candidatetype

Nothing on this build to point it at.

type no longer exists in Assembly-CSharp; 5 types share the name Data, so which one it became is not decidable here

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.UI.MainMenu.MainMenuPopup/Data was compiled against the other branch.

5 reports

no candidatetype

Nothing on this build to point it at.

type no longer exists in Assembly-CSharp; 2 types share the name NavigationSettings, so which one it became is not decidable here

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Vehicles.AI.NavigationSettings was compiled against the other branch.

5 reports

refusedtype

There was a candidate on this build and Polyfill did not trust it enough to use it.

its name changed, and Il2CppScheduleOne.Vehicles.AI.VehicleAgent/NavigationCallback is sealed, so nothing can stand in for it

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Vehicles.AI.VehicleAgent/NavigationCallback was compiled against the other branch.

5 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

mono-builtThe Mono delegate constructor shape, qualified spelling. Il2CppInterop builds its delegates a different way.

5 reports

no candidatemember

Nothing on this build to point it at.

1 report

no candidatemember

Nothing on this build to point it at.

1 report

bridgedmember

Polyfill pointed this at its successor when the game started.

211 reports

bridgedmemberwas no candidate

Polyfill pointed this at its successor when the game started.

211 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

211 reports

bridgedmemberwas no candidate

Polyfill pointed this at its successor when the game started.

211 reports

bridgedmemberwas no candidate

Polyfill pointed this at its successor when the game started.

211 reports

bridgedmemberwas no candidate

Polyfill pointed this at its successor when the game started.

211 reports

bridgedmemberwas no candidate

Polyfill pointed this at its successor when the game started.

211 reports

bridgedmemberwas no candidate

Polyfill pointed this at its successor when the game started.

206 reports

bridgedmemberwas no candidate

Polyfill pointed this at its successor when the game started.

206 reports

bridgedtypewas no candidate

Polyfill pointed this at its successor when the game started.

206 reports

bridgedmemberwas no candidate

Polyfill pointed this at its successor when the game started.

206 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

206 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

206 reports

bridgedmemberwas no candidate

Polyfill pointed this at its successor when the game started.

206 reports

bridgedmemberwas no candidate

Polyfill pointed this at its successor when the game started.

206 reports

bridgedmemberwas no candidate

Polyfill pointed this at its successor when the game started.

206 reports

bridgedmemberwas no candidate

Polyfill pointed this at its successor when the game started.

206 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

206 reports

bridgedmemberwas no candidate

Polyfill pointed this at its successor when the game started.

206 reports

bridgedmemberwas no candidate

Polyfill pointed this at its successor when the game started.

206 reports

bridgedmemberwas no candidate

Polyfill pointed this at its successor when the game started.

206 reports

bridgedmemberwas no candidate

Polyfill pointed this at its successor when the game started.

206 reports

bridgedtypewas no candidate

Polyfill pointed this at its successor when the game started.

206 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

205 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

205 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

205 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

202 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

202 reports

bridgedmemberwas no candidate

Polyfill pointed this at its successor when the game started.

202 reports

bridgedmemberwas no candidate

Polyfill pointed this at its successor when the game started.

202 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

202 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Audio.AudioSourceController was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Audio.MusicManager was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Audio.PolygonalZone was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.AvatarFramework.Accessory was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.AvatarFramework.Animation.AvatarAnimation was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.AvatarFramework.AvatarSettings was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.AvatarFramework.AvatarSettings/AccessorySetting was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.AvatarFramework.Emotions.AvatarEmotionManager was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.AvatarFramework.Equipping.AvatarEquippable was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.AvatarFramework.Equipping.AvatarMeleeWeapon was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.AvatarFramework.Equipping.AvatarRangedWeapon was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.AvatarFramework.Equipping.AvatarWeapon was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.AvatarFramework.Eye was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.AvatarFramework.Impostors.AvatarImpostor was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Cartel.Ambush was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Cartel.Cartel was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Cartel.CartelActivities was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Cartel.CartelActivity was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Cartel.CartelAmbushLocation was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Cartel.CartelCustomerDeal was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Cartel.CartelDealer was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Cartel.CartelDealInfo was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Cartel.CartelDealManager was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Cartel.CartelGoon was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Cartel.CartelInfluence was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Cartel.CartelInfluence/RegionInfluenceData was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Cartel.CartelRegionActivities was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Cartel.GoonPool was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Cartel.RobDealer was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Cartel.StealDeadDrop was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Combat.CombatBehaviour was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Combat.EImpactType was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Combat.ICombatTargetable was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Combat.IDamageable was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Combat.Impact was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Dialogue.BranchNodeData was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Dialogue.DialogueChoiceData was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Dialogue.DialogueController was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Dialogue.DialogueController_Dealer was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Dialogue.DialogueController/DialogueChoice was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Dialogue.DialogueController/GreetingOverride was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Dialogue.DialogueDatabase was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Dialogue.DialogueHandler was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Dialogue.DialogueNodeData was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Dialogue.EDialogueModule was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Dialogue.NodeLinkData was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Doors.StaticDoor was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Economy.ContractReceipt was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Economy.Customer was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Economy.CustomerAffinityData was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Economy.DeadDrop was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Economy.Dealer was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Economy.DeliveryLocation was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Economy.ECustomerStandard was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Economy.EDealerType was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Economy.EDealWindow was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Economy.ProductTypeAffinity was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.EntityFramework.ToggleableItem was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.GameInput was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.GameTime.EDay was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Graffiti.WorldSpraySurface was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Interaction.InteractableObject was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Interaction.InteractableObject/EInteractableState was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.ItemFramework.CashInstance was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.ItemFramework.EQuality was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.ItemFramework.ItemDefinition was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.ItemFramework.ItemInstance was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.ItemFramework.ItemSlot was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.ItemFramework.QualityItemInstance was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.ItemFramework.StorableItemDefinition was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Law.LawController was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Levelling.ERank was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Levelling.LevelManager was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Lighting.FlickeringLight was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Lighting.PoliceLight was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Map.EMapRegion was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Map.ManorGate was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Map.MapRegionData was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Map.NPCEnterableBuilding was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Map.NPCPoI was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Map.ParkingLot was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Map.POI was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Map.PoliceStation was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Map.PoliceStation/EDispatchType was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Messaging.MSGConversation was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Misc.ToggleableLight was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Money.MoneyManager was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.Behaviour.CallPoliceBehaviour was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.Behaviour.CustomerAttendDealBehaviour was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.Behaviour.DealerAttendDealBehaviour was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.Behaviour.FleeBehaviour was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.Behaviour.FleeBehaviour/EFleeMode was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.Behaviour.GenericDialogueBehaviour was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.Behaviour.NPCBehaviour was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.Behaviour.PursuitBehaviour was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.CharacterClasses.Anna was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.CharacterClasses.Dan was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.CharacterClasses.Dean was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.CharacterClasses.Fiona was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.CharacterClasses.Fixer was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.CharacterClasses.Frank was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.CharacterClasses.Herbert was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.CharacterClasses.Jeff was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.CharacterClasses.Jeremy was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.CharacterClasses.Marco was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.CharacterClasses.Mick was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.CharacterClasses.Thomas was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.Framework.BasicInfo was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.Framework.DealerNPCData was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.Framework.Health was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.Framework.Inventory was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.Framework.Movement was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.Framework.WeatherBehaviour was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.NPC was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.NPCAwareness was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.NPCHealth was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.NPCInventory was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.NPCManager was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.NPCMovement was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.NPCMovement/WalkResult was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.NPCScheduleManager was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.NPCSpeedController was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.NPCSpeedController/SpeedControl was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.Other.DrinkItem was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.Other.SmokeCigarette was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.Relation.NPCRelationData was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.Relation.NPCRelationData/EUnlockType was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.Schedules.NPCAction was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.Schedules.NPCEvent was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.Schedules.NPCEvent_LocationBasedAction was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.NPCs.Schedules.NPCEvent_StayInBuilding was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.ObjectScripts.BrickPress was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.ObjectScripts.Jukebox was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.ObjectScripts.Jukebox/Track was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Packaging.FilledPackaging_StoredItem was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Persistence.LoadManager was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Persistence.SaveInfo was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Persistence.SaveManager was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.PlayerScripts.Health.PlayerHealth was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.PlayerScripts.Player was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.PlayerScripts.PlayerCamera was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.PlayerScripts.PlayerCrimeData was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.PlayerScripts.PlayerCrimeData/EPursuitLevel was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.PlayerScripts.PlayerInventory was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.PlayerScripts.PlayerManager was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.PlayerScripts.PlayerMovement was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Police.PoliceOfficer was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Product.CocaineVisualsSetter was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Product.EDrugType was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Product.MultiTypeVisualsSetter was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Product.Packaging.PackagingDefinition was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Product.ProductDefinition was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Product.ProductItemInstance was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Product.ProductList was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Product.ProductVisualsSetter was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Property.Business was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Property.LaunderingOperation was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Property.Manor was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Property.Property was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Property.RV was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Quests.ContractInfo was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Quests.EExpiryVisibility was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Quests.EQuestState was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Quests.Quest was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Quests.Quest_DealForCartel was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Quests.Quest_DefeatCartel was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Quests.QuestEntry was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Quests.QuestManager was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Quests.QuestWindowConfig was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Storage.StorableItemInstance was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Storage.StorageEntity was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Storage.StorageEntity/EAccessSettings was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Storage.StoredItem was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Storage.WorldStorageEntity was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.UI.CartelInfluenceChangePopup was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.UI.Compass.CompassManager was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.UI.Compass.CompassManager/Element was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.UI.DealCompletionPopup was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.UI.DeathScreen was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.UI.DialogueCanvas was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.UI.DialogueChoiceEntry was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.UI.Handover.HandoverScreen was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.UI.HUD was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.UI.MainMenu.MainMenuPopup was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.UI.NewCustomerPopup was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.UI.NotificationsManager was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.UI.Phone.ContactsApp.ContactsApp was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.UI.QuestEntryHUDUI was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.UI.QuestHUDUI was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.UI.WorldspaceDialogueRenderer was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Vehicles.AI.DriveFlags was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Vehicles.AI.DriveFlags/EObstacleMode was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Vehicles.AI.VehicleAgent was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Vehicles.AI.VehicleAgent/ENavigationResult was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Vehicles.AI.VehicleTeleporter was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Vehicles.LandVehicle was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Vehicles.ParkData was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Vehicles.VehicleLights was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Vehicles.VehicleManager was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Vision.VisionCone was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.VoiceOver.EVOLineType was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.VoiceOver.PoliceChatterVO was compiled against the other branch.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

5 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

5 reports