How to fix the mount conflict with Unlimited Sprint mod. Both mods use mount priority 31999.
Update: Since NStriker has given bug fixing permission I have uploaded a version of this mod that has has the mount priority changed for user convenience. Only use my version if you are using Unlimited Sprint Mod or have another mount priority conflicting mod.No Reapers and Max Scan Range - MPC (Mount Priority Changed) Everyone may want to read my description page for more info about EGM compatibility and what this mod does and does not do.
Unpack the Legendary Explorer in the folder of your choice like any compressed files that you have dealt with.
Import the "No Reapers and Max Scan Range" mod into ME3Tweaks Mod Manager if you haven't already done so. Do NOT apply the mod just import.
In ME3Tweaks right click the "No Reapers and Max Scan Range" mod and choose "open mod folder"
In the No Reapers and Max Scan Range mod folder open the "DLC_Mod_SCS_No_Reapers" sub folder and then open "CookedPCConsole" sub folder under that.
In the address bar of Windows file explorer right click "CookedPCConsole" and "copy address as text" This will give you the file location path needed for Legendary Explorer.
Run "LegendaryExplorer.exe" from the location that you uncompressed the Legendary Explorer 7zip file.
It should have the path to Mass Effect Legendary Edition prefilled. If not put in the path. Then continue on
Look for and click on the "MNT mount editor" in the "Legendary Explorer"
Mount Editor will run
In "Mount Editor" the last drop down on the bottom right need to be changed to "Mass Effect 3 LE"
Then click "Load mount file"
In the Address bar for opening the file delete any existing address and right click in the address bar and paste then press "Enter" on the keyboard. This will put in the path for the "Mount.dlc" file for No Reapers and Max Scan Range mod.
Select the "Mount.dlc" file and click "Open"
Now you will see the Mount priority set to "31999". Change that to "31899" (This was a free slot in my mod list) Do NOT make any other changes.
Click "Save mount file", Click "Save", choose "Yes" to overwrite the existing file.
You should get a pop-up box that says "Done" Click "OK"
Go back to ME3Tweaks Mod Manager and Apply the "No Reapers and Max Scan Range" Mod
Open Mass Effect 3 Legendary Edition and test to see if this mod and all other mods are now working. If it works congratulations you do not need to read the rest of this post.
Update: Tried to clarify this a little more. If it doesn't work you may have done something wrong or "31899" is conflicting with another mod. If you have a conflict you will have to find a free mount priority slot. The quickest way to find a mount priority slots is to run "ME3Tweaks Mod Manager". Click Tools --> Generate new DLC mod (Starter Kit) --> Mass Effect 3 (Legendary Edition). The right hand pain lists ME3Tweaks known mods and their mount priority numbers. Look for a free slot number in the 31xxx range. These are the mods that have been reported to ME3Tweaks only. If the mod has not been reported to ME3Tweaks it will not show up in this list. Any changes you make manually will also not show up here. When you change the mount priority No Reapers and Max Scan Range it will still report it at 31999.
Hi , first of all thank you for the fix guide, second I may be doing something wrong but saving the Mount.dlc with the new assigned priority doesn't change it after checking in Generate new DLC mod (Starter Kit) load order.
I wasn't clear on the Generate new DLC mod (Starter Kit). I think I even botched it on my very first post. When I went back and reread it I had to edit it. I should make another edit to make it clearer.
It only shows the known mods and their priorities. It does NOT update the list with any changes unless the mod author reports that to ME3Tweaks. It is more like a quick and dirty way to look for an open slot.
If you open the "Mount.dlc" file again and it has the priority number that you set then it was successfully modified.
Don't forget that you will need to re-apply the mod (The very last step) to get your changes to work. If the mod works you successfully changed it and it doesn't have any conflicts.
This mod does NOT work with the EGM (Enhanced Galaxy Mod) when you use the Galactic Core option regardless if the mount priority slot has no conflicts. It does work with EGM without the Galactic Core option (the default option). Keep that in mind if you are trying to fix the conflict. Galactic Core has similar functionality (turn reapers on/off and an in-game upgrade of the scanner).
I haven't played since Legendary Edition came out, so sorry I haven't responded. This is for LE3, not original ME3. It uses the DLC mode of the mod editor that was new at that time and changes literally 2 variables in coalesced.bin. One about scan range and one for Reaper movement speed (set to 0). That's it.
Unless the tools changed in the last 2 years (likely), it should still work. But I for sure don't have the original files or LE installed at this time to check.
Someone way down in the comments found out it shares a mount number with another mod, so that could make it not work. Also, if you have any other mods installed that change the same variables then that will override this.
For those wondering how this mod appears in the game: Scans will still alert Reapers. You'll see the blips on the edge of the galaxy, music will play, and EDI will react as if you're being chased. BUT -- the Reapers will never appear in the system, no matter how many times you scan.
This should be added to the mod description ... while the unlimited scan range works as intended i was also confused that the alert level rises ... not really a problem if you only scan once, then no reapers should appear.
so yes, this mod works for me just as Izenphine pointed out
It's mentioned around here that it conflicts with the Unlimited Sprint Mod, and possibly other mods like EGM. fangnebula made a different version above that you might try.
So fyi the people who use the Extended Galaxy Alpha mod and say this mod doesn't work there's a choice when you install the E.G.A mod to turn off reapers. I just noticed it and feel really dumb.
I can't speak for others. This mod still works for me with EGM (Core QoL version). Also, Reaper alertness will still trigger, but they never appear when fully alert, which is fine. I want to test the load order w/other EGM versions but don't know how. Can someone help?
Well, due to the fact that i have an EGM, i was worried that this mod would not work. But fortunately everything is fine. The strip about the readiness of the Reapers is full, but they themselves are not. Thank you for this mod!
57 comments
Update: Since NStriker has given bug fixing permission I have uploaded a version of this mod that has has the mount priority changed for user convenience. Only use my version if you are using Unlimited Sprint Mod or have another mount priority conflicting mod. No Reapers and Max Scan Range - MPC (Mount Priority Changed)
Everyone may want to read my description page for more info about EGM compatibility and what this mod does and does not do.
Open Mass Effect 3 Legendary Edition and test to see if this mod and all other mods are now working. If it works congratulations you do not need to read the rest of this post.
Update: Tried to clarify this a little more.
If it doesn't work you may have done something wrong or "31899" is conflicting with another mod. If you have a conflict you will have to find a free mount priority slot. The quickest way to find a mount priority slots is to run "ME3Tweaks Mod Manager". Click Tools --> Generate new DLC mod (Starter Kit) --> Mass Effect 3 (Legendary Edition). The right hand pain lists ME3Tweaks known mods and their mount priority numbers. Look for a free slot number in the 31xxx range. These are the mods that have been reported to ME3Tweaks only. If the mod has not been reported to ME3Tweaks it will not show up in this list. Any changes you make manually will also not show up here. When you change the mount priority No Reapers and Max Scan Range it will still report it at 31999.
any idea as to why this might be happening?
It only shows the known mods and their priorities. It does NOT update the list with any changes unless the mod author reports that to ME3Tweaks. It is more like a quick and dirty way to look for an open slot.
If you open the "Mount.dlc" file again and it has the priority number that you set then it was successfully modified.
Don't forget that you will need to re-apply the mod (The very last step) to get your changes to work. If the mod works you successfully changed it and it doesn't have any conflicts.
This mod does NOT work with the EGM (Enhanced Galaxy Mod) when you use the Galactic Core option regardless if the mount priority slot has no conflicts. It does work with EGM without the Galactic Core option (the default option). Keep that in mind if you are trying to fix the conflict. Galactic Core has similar functionality (turn reapers on/off and an in-game upgrade of the scanner).
Unless the tools changed in the last 2 years (likely), it should still work. But I for sure don't have the original files or LE installed at this time to check.
Someone way down in the comments found out it shares a mount number with another mod, so that could make it not work. Also, if you have any other mods installed that change the same variables then that will override this.
Update, its the unlimited sprint mod that it conflicts with.
Can you change the mount number for your mod?
"in EGM file ME3\Binaries\EGMSettings.ini
InitPlotManagerValueByIndex 28993 bool 1"
For those wondering how this mod appears in the game: Scans will still alert Reapers. You'll see the blips on the edge of the galaxy, music will play, and EDI will react as if you're being chased. BUT -- the Reapers will never appear in the system, no matter how many times you scan.
Not even the extended scan is working.
so yes, this mod works for me just as Izenphine pointed out
Edit:
ugh, it's supposed to be for original ME3 only but its put under Legendary...
Thank you for this mod!