bridgedtypewas no candidate
Il2CppScheduleOne.Clothing.EClothingApplicationTypePolyfill pointed this at its successor when the game started.
202 reportsIn 1.0.1
no candidatemember
Il2CppScheduleOne.Clothing.ClothingDefinition::set_ApplicationType(EClothingApplicationType)Nothing on this build to point it at.
method missing, with nothing on this type to point at
189 reportsIn 1.0.1
no candidatemember
Il2CppScheduleOne.Clothing.ClothingDefinition::set_ClothingAssetPath(String)Nothing on this build to point it at.
method missing, with nothing on this type to point at
189 reportsIn 1.0.1
bridgedtype
Il2CppScheduleOne.ItemFramework.EItemCategoryPolyfill pointed this at its successor when the game started.
out-of-rangeAlready lived in Il2CppScheduleOne.Core.Items.Framework at 0.4.5f2 - ItemFilter_Category imports it from there in the oldest build on record. The move predates Polyfill.
189 reportsIn 1.0.1
no candidatemember
Il2CppScheduleOne.ItemFramework.ItemDefinition::get_Keywords()Nothing on this build to point it at.
method missing, with nothing on this type to point at
189 reportsIn 1.0.1
no candidatemember
Il2CppScheduleOne.ItemFramework.ItemDefinition::set_Category(EItemCategory)Nothing on this build to point it at.
method missing, with nothing on this type to point at; the base type BaseItemDefinition has set_Category under different parameters
189 reportsIn 1.0.1
no candidatemember
Il2CppScheduleOne.ItemFramework.ItemDefinition::set_Keywords(Il2CppStringArray)Nothing on this build to point it at.
method missing, with nothing on this type to point at
189 reportsIn 1.0.1
no candidatefield
Il2CppScheduleOne.Clothing.ClothingDefinition::ApplicationTypeNothing on this build to point it at.
field missing, with nothing on this type to point at
2 reportsIn 1.0.1
no candidatefield
Il2CppScheduleOne.Clothing.ClothingDefinition::ClothingAssetPathNothing on this build to point it at.
field missing, with nothing on this type to point at
2 reportsIn 1.0.1
no candidatefield
Il2CppScheduleOne.Clothing.ClothingDefinition::ColorableNothing 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 reportsIn 1.0.1
no candidatefield
Il2CppScheduleOne.Clothing.ClothingDefinition::DefaultColorNothing 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 reportsIn 1.0.1
no candidatefield
Il2CppScheduleOne.Clothing.ClothingDefinition::SlotNothing 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 reportsIn 1.0.1
no candidatefield
Il2CppScheduleOne.ItemFramework.ItemDefinition::CategoryNothing on this build to point it at.
the field became a property on BaseItemDefinition, 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 on BaseItemDefinition, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on
2 reportsIn 1.0.1
no candidatefield
Il2CppScheduleOne.ItemFramework.ItemDefinition::CustomItemUINothing 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 reportsIn 1.0.1
no candidatefield
Il2CppScheduleOne.ItemFramework.ItemDefinition::DescriptionNothing on this build to point it at.
the field became a property on BaseItemDefinition, 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 on BaseItemDefinition, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on
2 reportsIn 1.0.1
no candidatefield
Il2CppScheduleOne.ItemFramework.ItemDefinition::IconNothing on this build to point it at.
the field became a property on BaseItemDefinition, 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 on BaseItemDefinition, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on
2 reportsIn 1.0.1
no candidatefield
Il2CppScheduleOne.ItemFramework.ItemDefinition::IDNothing on this build to point it at.
the field became a property on BaseItemDefinition, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on
no-stand-inNothing moved. ID has belonged to BaseItemDefinition since before 0.4.5f2 and still does, one assembly up in Il2CppScheduleOne.Core, and ItemDefinition inherits it. What differs is its KIND: the mods emit a field token, and Il2CppInterop projects the native field as a property. A field token never falls back to an accessor, so a property under the same name would be read by nobody, and a real managed field would hold a value the game never reads - a bridge that compiles and lies. The mod author's fix is a rebuild against the shipped Il2CppScheduleOne.Core.dll, with no source change.
2 reportsIn 1.0.1
no candidatefield
Il2CppScheduleOne.ItemFramework.ItemDefinition::KeywordsNothing on this build to point it at.
field missing, with nothing on this type to point at
2 reportsIn 1.0.1
no candidatefield
Il2CppScheduleOne.ItemFramework.ItemDefinition::NameNothing on this build to point it at.
the field became a property on BaseItemDefinition, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on
no-stand-inThe same kind mismatch as ItemDefinition::ID, in the same place and for the same reason. Name is BaseItemDefinition's, inherited, and reached through a property rather than a field. See that entry.
2 reportsIn 1.0.1
no candidatefield
Il2CppScheduleOne.ItemFramework.ItemDefinition::StackLimitNothing on this build to point it at.
the field became a property on BaseItemDefinition, 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 on BaseItemDefinition, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on
2 reportsIn 1.0.1
no candidatefield
Il2CppScheduleOne.ItemFramework.ItemDefinition::UsableInFiltersNothing on this build to point it at.
the field became a property on BaseItemDefinition, 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 on BaseItemDefinition, and a field cannot be answered with one - the mod needs rebuilding against the MelonLoader it runs on
2 reportsIn 1.0.1
no candidatefield
Il2CppScheduleOne.ItemFramework.StorableItemDefinition::BasePurchasePriceNothing 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 reportsIn 1.0.1
no candidatefield
Il2CppScheduleOne.ItemFramework.StorableItemDefinition::ShopCategoriesNothing 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 reportsIn 1.0.1
no candidatefield
Il2CppScheduleOne.ItemFramework.StorableItemDefinition::StoredItemNothing 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 reportsIn 1.0.1
no candidatefield
Il2CppScheduleOne.Registry/ItemRegister::DefinitionNothing 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 reportsIn 1.0.1
no candidatefield
Il2CppScheduleOne.Registry/ItemRegister::IDNothing 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 reportsIn 1.0.1
bridgedmember
Il2CppScheduleOne.UI.Shop.ShopInterface::CreateListingUI(ShopListing)Polyfill pointed this at its successor when the game started.
2 reportsIn 1.0.1
no candidatefield
Il2CppScheduleOne.UI.Shop.ShopInterface::ListingsNothing 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 reportsIn 1.0.1
no candidatefield
Il2CppScheduleOne.UI.Shop.ShopListing::ItemNothing 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 reportsIn 1.0.1
no candidatefield
Il2CppScheduleOne.UI.Shop.ShopListing::nameNothing 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 reportsIn 1.0.1
no candidatefield
Il2CppScheduleOne.UI.Shop.ShopListing::OverriddenPriceNothing 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 reportsIn 1.0.1
no candidatefield
Il2CppScheduleOne.UI.Shop.ShopListing::OverridePriceNothing 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 reportsIn 1.0.1
no candidatefield
Il2CppScheduleOne.UI.Shop.ShopListing/CategoryInstance::CategoryNothing 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 reportsIn 1.0.1
bridgedtype
ScheduleOne.Clothing.ClothingDefinitionPolyfill pointed this at its successor when the game started.
mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Clothing.ClothingDefinition was compiled against the other branch.
2 reportsIn 1.0.1
no candidatetype
ScheduleOne.Clothing.EClothingApplicationTypeNothing 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.Clothing.EClothingApplicationType was compiled against the other branch.
2 reportsIn 1.0.1
bridgedtype
ScheduleOne.Clothing.EClothingColorPolyfill pointed this at its successor when the game started.
mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Clothing.EClothingColor was compiled against the other branch.
2 reportsIn 1.0.1
bridgedtype
ScheduleOne.Clothing.EClothingSlotPolyfill pointed this at its successor when the game started.
mono-builtMono branch name. Every game type in this build is Il2CppScheduleOne.*, so a mod asking for ScheduleOne.Clothing.EClothingSlot was compiled against the other branch.
2 reportsIn 1.0.1
no candidatetype
ScheduleOne.DevUtilities.Singleton`1Nothing 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 reportsIn 1.0.1
bridgedtype
ScheduleOne.ItemFramework.EItemCategoryPolyfill pointed this at 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.EItemCategory was compiled against the other branch.
2 reportsIn 1.0.1
bridgedtype
ScheduleOne.ItemFramework.ItemDefinitionPolyfill pointed this at 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.
2 reportsIn 1.0.1
bridgedtype
ScheduleOne.ItemFramework.StorableItemDefinitionPolyfill pointed this at 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.
2 reportsIn 1.0.1
no candidatetype
ScheduleOne.RegistryNothing 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.
2 reportsIn 1.0.1
no candidatepatch target
ScheduleOne.Registry::AwakeNothing 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.Registry::Awake was compiled against the other branch.
2 reportsIn 1.0.1
refusedtype
ScheduleOne.Registry/ItemRegisterThere was a candidate on this build and Polyfill did not trust it enough to use it.
its name changed, and ScheduleOne.Registry, 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.Registry/ItemRegister was compiled against the other branch.
2 reportsIn 1.0.1
bridgedtype
ScheduleOne.Storage.StoredItemPolyfill pointed this at 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.
2 reportsIn 1.0.1
bridgedtype
ScheduleOne.UI.Items.ItemUIPolyfill pointed this at 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.Items.ItemUI was compiled against the other branch.
2 reportsIn 1.0.1
bridgedtype
ScheduleOne.UI.Shop.ClothingShopInterfacePolyfill pointed this at 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.Shop.ClothingShopInterface was compiled against the other branch.
2 reportsIn 1.0.1
no candidatepatch target
ScheduleOne.UI.Shop.ClothingShopInterface::StartNothing 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.Shop.ClothingShopInterface::Start was compiled against the other branch.
2 reportsIn 1.0.1
bridgedtype
ScheduleOne.UI.Shop.EShopCategoryPolyfill pointed this at 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.Shop.EShopCategory was compiled against the other branch.
2 reportsIn 1.0.1
bridgedtype
ScheduleOne.UI.Shop.ShopInterfacePolyfill pointed this at 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.Shop.ShopInterface was compiled against the other branch.
2 reportsIn 1.0.1
bridgedtype
ScheduleOne.UI.Shop.ShopListingPolyfill pointed this at 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.Shop.ShopListing was compiled against the other branch.
2 reportsIn 1.0.1
bridgedtype
ScheduleOne.UI.Shop.ShopListing/CategoryInstancePolyfill pointed this at 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.Shop.ShopListing/CategoryInstance was compiled against the other branch.
2 reportsIn 1.0.1
no candidatemember
UnityEngine.ImageConversion::LoadImage(UnityEngine.Texture2D, System.Byte[])Nothing on this build to point it at.
the method still exists but its parameters changed
2 reportsIn 1.0.1