Jump to content

Quaksen

Moderator
  • Posts

    5573
  • Joined

  • Last visited

  • Days Won

    218

Posts posted by Quaksen

  1. default toggle key is "0" key on the numerical keypad. This can be changed by editing the "autoaim_indicator.json" file located in res_mods\0.9.5\scripts\client\mods\

    Actually, default toggle is is "none". There is no toggle key by default.

    You'll need to change the key in the file mentioned in the quote.

    The key codes needed are here:

    http://www.soloviyko.com/faq/enable-large-minimap-for-those-of-you-who-would-like-the-option-of-a-large-minimap-by-pressing-e-g-left-ctrl/

    (For example, Keypad 0 is keycode: 82.

  2. I've selected "Random Battles" and the "Send to Platoon chat" - but it only seems to post when there's less than 7 alive, like the "Send to team chat" says.

    It should be posting when everyone is alive too, surely? :-)

    (Since "spam ban warning" isn't an issue in a platoon chat)

     

    Edit:

    Found the config file for it and changed the line for the max amount on team.

    I'm guessing the installer should be setting that to 0, if you select the Platoon option  :D

  3. So, after closing the game a few minutes ago, I cannot reopen it.

    It's stopping on the "Loading, please wait" screen.

    (Was using 3.9.10 when it did it, clean installed 3.9.10v1 and it still happens)

    [ModSettingsAPIUpdaterInstance] crashed
    <type 'exceptions.ValueError'>
    unknown url type: ?userid=-1
      File "python\scripts\client\gui\scaleform\daapi\view\lobby\settings\ModSettingsAPIUpdater.py", line 44, in checkForUpdates
      File "scripts/common/Lib/urllib2.py", line 126, in urlopen
      File "scripts/common/Lib/urllib2.py", line 392, in open
      File "scripts/common/Lib/urllib2.py", line 254, in get_type
    

    Edit: It loaded now, but I'll leave the post to find out what was up

    As an added note, in Settings / Mods tab, it says "vundefined" instead of the version number

    _Aslain_logs.zip

    python.log

  4. With the latest installer (3.9.4) I'm not getting the error anymore.

    (Haven't installed or uninstalled any programs, nor rebooted since last install attempt with 3.9.2, and haven't changed mods being installed)

    So might have been something in the installer afterall, that was fixed?  :blink:

    (Edit; Spoke too soon, 3.9.5 throws it again for me  :P )

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use and Privacy Policy.