There is an issue on fresh PA install (or after deleting your localstore) hotbuild_settings.js, line 540 : var settings = decode(localStorage.settings) => it returns a null => which quickly follow with a "Uncaught TypeError: Cannot read property 'hotbuildconfig' of null" I tried to replace it with decode(localStorage[localStorage.uberName + ".paSettings"]); and it seems to work, but I have no idea of what you were doing with settings previously :]
Awesome! Replaced the lines with the line you provided and it works for me too now! I haven't done anything inside this file, as I have no clue of actually modifying a mod, I just installed the game, installed PAMM, clicked on install Hotbuild and started the game. Thanks for your time! Really awesome and glad that it works now.
I was talking to the mod maintainer I guess a new version should be release to PAMM soon™ But i'm happy you were able to apply this temporary fix on your installation directly, but I can't guarantee it's the right one
It's whats I was afraid of, I remove a symptom, not cured the disease Hopefully proeleert will be able to fix it for good.
ok updated to 1.22 WARNING for users that didn't have issues ! : export current settings before upgrading ! then upgrade and reimport...
ok updated to 1.23 - Hotbuild Settings should work in PTE now also. WARNING for users that didn't have issues ! : export current settings before upgrading ! then upgrade and reimport...
Having issues accessing hotbuild settings. I open it up in the PTE and nothing shows up. It's blank. I did NOT export/import settings, because I wanted to just reset them and redo my entire build thingy (it has been a while since I updated it, after all.) I deleted my local storage folder, just to be safe, but no change. Need my DxDiag? EDIT: checking the stable now. Give me a second to confirm if it works there or not. EDIT 2: Works on Stable. I'll also check if it transfers to PTE. EDIT 3: Settings do transfer. Duh.
Sorry for asking a stupid question but I can't figure this out for the life of me. When I set the WASD default keybindings with Hotbuild, I no longer have an attack move hotkey? There doesn't seem to be a good space to fit one in either...
Well everybody is free to give me a better WASD export to make as defaults. The one now is pretty old anyways...
this lacks other keyboard layouts than qwerty: - qwertz-layout for German keyboards with umlauts äöü, easily the most programmer unfriendly layout. - azerty layout for France. - possibly korean and japanese overlays for the querty layout.
I know I should work on that, but with all these breaking patches and other stuff it's not so high on my priority list...