If the mod uses the old project format ( i.e., there's no at the top), see How to: Configure projects to target platforms to set the platform to Any CPU. csproj project file, remove these lines if present: If you explicitly changed it to x86, you'll need to change it back to Any CPU to avoid errors for 64-bit players. New mod projects target Any CPU by default. If you use this to distinguish between XNA Framework (on Windows) and MonoGame (on other platforms), you should use the new Constants.GameFramework instead. Review TargetPlatform constants Constants.TargetPlatform indicates whether the mod is running on Android, Linux, MacOS, or Windows. For SMAPI mods, there are two main requirements for 64-bit compatibility: Most SMAPI mods will work in both 32-bit and 64-bit mode already, and content packs don't need to do anything (they're compatible if the SMAPI mod loading them is). This will only affect players who explicitly go through the process to make the game 64-bit, and most mods are already compatible with 64-bit mode. The vast majority of players will use the normal 32-bit version. The SMAPI installer automatically detects whether you have a 32-bit or 64-bit version of the game. SMAPI will always support the official version of the game, which is currently 32-bit on Windows. Otherwise you can just use the default versions, which are simpler and work fine. You only need this if you play on Windows and experience OutOfMemoryException crashes. Changing the game to 64-bit unlocks access to all available memory to avoid that (if the computer itself has enough memory available). In 64-bit mode, it has unlimited access to your computer's memory.ģ2-bit is fine for most players, but those with a large number of mods (or large mods) can experience OutOfMemoryException crashes. Since the game is normally 32-bit, it shares the first ≈3GB of memory with every 32-bit app on your computer. The game's bitness affects how much memory it can use. 2.2 How do I update mod code for 64-bit?.

Windows 7 modded edition