Mules

no candidatemember

Nothing on this build to point it at.

method missing, with nothing on this type to point at

13 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

2 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

2 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

2 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

2 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

2 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

2 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

2 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

2 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

2 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

2 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

2 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

2 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

2 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

2 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

2 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

2 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

2 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

2 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

2 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

2 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

2 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

2 reports

no candidatefield

Nothing on this build to point it at.

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

2 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

2 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

2 reports

refusedmember

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

.ctor is overloaded here, so which one it became is not decidable

2 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

2 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

2 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

2 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

2 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

2 reports

refusedmember

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

.ctor is overloaded here, so which one it became is not decidable

2 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

2 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

2 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

2 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

2 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

2 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

2 reports

refusedmember

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

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

2 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

2 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

2 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

2 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

2 reports

no candidatefield

Nothing on this build to point it at.

field missing, with nothing on this type to point at

2 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

2 reports

no candidatefield

Nothing on this build to point it at.

field missing, with nothing on this type to point at

2 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

2 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

2 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

2 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

2 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

2 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

2 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

2 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

2 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

2 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

2 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

2 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

2 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

2 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

2 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

2 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

2 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

2 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

2 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

2 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

2 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

2 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

2 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

2 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

2 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

2 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

2 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

2 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

2 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

2 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.

2 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.

2 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.

2 reports

refusedtype

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

its name changed, and ScheduleOne.Console, 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.Console/AddEmployeeCommand was compiled against the other branch.

2 reports

no candidatepatch target

Nothing on this build to point it at.

the patched type does not exist here, so this patch will not apply

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

2 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.

2 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.

2 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.

2 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.

2 reports

no candidatepatch target

Nothing on this build to point it at.

the patched type does not exist here, so this patch will not apply

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

2 reports

no candidatepatch target

Nothing on this build to point it at.

the patched type does not exist here, so this patch will not apply

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

2 reports

no candidatepatch target

Nothing on this build to point it at.

the patched type does not exist here, so this patch will not apply

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

2 reports

no candidatepatch target

Nothing on this build to point it at.

the patched type does not exist here, so this patch will not apply

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

2 reports

no candidatepatch target

Nothing on this build to point it at.

the patched type does not exist here, so this patch will not apply

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

2 reports

no candidatepatch target

Nothing on this build to point it at.

the patched type does not exist here, so this patch will not apply

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

2 reports

no candidatepatch target

Nothing on this build to point it at.

the patched type does not exist here, so this patch will not apply

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

2 reports

no candidatepatch target

Nothing on this build to point it at.

the patched type does not exist here, so this patch will not apply

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

2 reports

no candidatetype

Nothing on this build to point it at.

type no longer exists in Assembly-CSharp; 2 types share the name ObjectField, 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.Management.ObjectField was compiled against the other branch.

2 reports

no candidatetype

Nothing on this build to point it at.

type no longer exists in Assembly-CSharp; 2 types share the name ObjectListField, 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.Management.ObjectListField was compiled against the other branch.

2 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.

2 reports

no candidatepatch target

Nothing on this build to point it at.

the patched type does not exist here, so this patch will not apply

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

2 reports

no candidatepatch target

Nothing on this build to point it at.

the patched type does not exist here, so this patch will not apply

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

2 reports

no candidatetype

Nothing on this build to point it at.

type no longer exists in Assembly-CSharp; 9 types share the name EState, 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.MoveItemBehaviour/EState was compiled against the other branch.

2 reports

no candidatetype

Nothing on this build to point it at.

type no longer exists in Assembly-CSharp; 2 types share the name ItemFilter, 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.NPCInventory/ItemFilter was compiled against the other branch.

2 reports

no candidatepatch target

Nothing on this build to point it at.

the patched type does not exist here, so this patch will not apply

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

2 reports

no candidatepatch target

Nothing on this build to point it at.

the patched type does not exist here, so this patch will not apply

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

2 reports

no candidatepatch target

Nothing on this build to point it at.

the patched type does not exist here, so this patch will not apply

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

2 reports

no candidatepatch target

Nothing on this build to point it at.

the patched type does not exist here, so this patch will not apply

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

2 reports

no candidatepatch target

Nothing on this build to point it at.

the patched type does not exist here, so this patch will not apply

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

2 reports

no candidatepatch target

Nothing on this build to point it at.

the patched type does not exist here, so this patch will not apply

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

2 reports

no candidatepatch target

Nothing on this build to point it at.

the patched type does not exist here, so this patch will not apply

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

2 reports

no candidatepatch target

Nothing on this build to point it at.

the patched type does not exist here, so this patch will not apply

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

2 reports

no candidatepatch target

Nothing on this build to point it at.

the patched type does not exist here, so this patch will not apply

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

2 reports

no candidatepatch target

Nothing on this build to point it at.

the patched type does not exist here, so this patch will not apply

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

2 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.

2 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

2 reports

no candidatemember

Nothing on this build to point it at.

the method still exists but its parameters changed

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

15 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

15 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

13 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

13 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

13 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

13 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

13 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

13 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

13 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

13 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

13 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 reports

bridgedmember

Polyfill pointed this at its successor when the game started.

2 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.

2 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.

2 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.

2 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.

2 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_Fixer was compiled against the other branch.

2 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.

2 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.

2 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.Employees.Cleaner was compiled against the other branch.

2 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.Employees.EEmployeeType was compiled against the other branch.

2 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.Employees.Employee was compiled against the other branch.

2 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.Employees.EmployeeHome was compiled against the other branch.

2 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.Employees.EmployeeManager was compiled against the other branch.

2 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.BuildableItem was compiled against the other branch.

2 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.

2 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.

2 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.IItemSlotOwner was compiled against the other branch.

2 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.

2 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.

2 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.ItemSlotLock was compiled against the other branch.

2 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.

2 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.Management.AdvancedTransitRoute was compiled against the other branch.

2 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.Management.CleanerConfiguration was compiled against the other branch.

2 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.Management.EConfigurableType was compiled against the other branch.

2 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.Management.EntityConfiguration was compiled against the other branch.

2 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.Management.IConfigurable was compiled against the other branch.

2 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.Management.ITransitEntity was compiled against the other branch.

2 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.Management.ManagementInterface was compiled against the other branch.

2 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.Management.RouteListField was compiled against the other branch.

2 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.Management.StringField was compiled against the other branch.

2 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.Management.TransitRoute was compiled against the other branch.

2 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.Management.UI.ConfigPanel was compiled against the other branch.

2 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.IdleBehaviour was compiled against the other branch.

2 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.MoveItemBehaviour was compiled against the other branch.

2 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.

2 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.

2 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.

2 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.Bed was compiled against the other branch.

2 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.PlaceableStorageEntity was compiled against the other branch.

2 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.Datas.DeserializedItemSet was compiled against the other branch.

2 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.Datas.ItemSet was compiled against the other branch.

2 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.

2 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.

2 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.

2 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.

2 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.

2 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.

2 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.

2 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.

2 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.

2 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_Employees was compiled against the other branch.

2 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.

2 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.Tools.ManagementClipboard was compiled against the other branch.

2 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.Tools.ManagementClipboard_Equippable was compiled against the other branch.

2 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.Management.CleanerUIElement was compiled against the other branch.

2 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.Management.ManagementWorldspaceCanvas was compiled against the other branch.

2 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.Management.ObjectFieldUI was compiled against the other branch.

2 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.Management.ObjectListFieldUI was compiled against the other branch.

2 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.Management.ObjectSelector was compiled against the other branch.

2 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.Management.PackagerConfigPanel was compiled against the other branch.

2 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.Management.RouteEntryUI was compiled against the other branch.

2 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.Management.RouteListFieldUI was compiled against the other branch.

2 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.Tooltips.Tooltip was compiled against the other branch.

2 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.UIScreen was compiled against the other branch.

2 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.UIScreenManager was compiled against the other branch.

2 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

2 reports

bridgedtype

Polyfill pointed this at its successor when the game started.

2 reports