0 of 0

File information

Last updated

Original upload

Created by

gleamage

Uploaded by

gleamage

Virus scan

Safe to use

Tags for this mod

5 comments

  1. BetariusSigmagon
    BetariusSigmagon
    • member
    • 5 kudos
    How do you install it? Frosty or some other method? I just keep getting an error that frosty cant install it
  2. n7shepard1987
    n7shepard1987
    • member
    • 0 kudos
    Are the variants in a specific shop or just anywhere?
  3. gleamage
    gleamage
    • member
    • 3 kudos
    Completely irrelevant but will someone be interested in a mini tweak that makes Crusader's accuracy more similar to its ME3 version? Kind of have the necessary files in hand but way too LAZY to go through the drill to post it.
  4. Noitox
    Noitox
    • member
    • 1 kudos
    Does this Mod work with Balanced Weapons and/or Groundside Firepower Pack? Would be nice to know.
    I'm now at Rank 8 and want to give this weapons a try reaching the maximum.
    1. gleamage
      gleamage
      • member
      • 3 kudos
      Sorry for the late reply. I don't personally use these mods so I can only give speculations.
      Having peeked into what the two mods in question do, I lean towards mine being compatible with both of them since :
      - Balanced Weapons seems to be focused on tweaking weapon damage. This shouldn't require touching the files I have touched : development projects and rank X siphon variant weapon files (weapon damage is stored in a sperate spreadsheet).
      - Groundside Firepower Pack, having introduced so much, is a bit less certain. But adding new weapons in that mod is done via fresh projects so I don't think it can interfere with mine.

      Regardless, do note that if you only want to try siphon variants in SP, there is no need to keep my main mod activated. Simply activate my mod when you want to craft siphon weapons and drop it when you are done. If you also want to have concussive and bulwark on siphon, there will be conflicts if another mod overwrites the MP specific siphon weapon files. In that case try the v1.1 update optional file I'm about to release and it should avoid the conflict.