Tweaks and hammer binds are totally different.
A tweak is a change in a property for certain class in the game, a property
you are not meant to change in first place. If these properties were made configurable (defined as
config vars in uscript) they would be stored in some ini file, but they are not, hence you need to load the tweaks everytime you run the game.
Furthermore
tweaks shouldn't work online: they do because of a bug in UT which lets you carry on the changes you made offline to online games. Why do you think that you need to load them before joining a server? ... Tweaks make use of a security flaw ^^ to gain advantages. "Hacks" or "exploits" is a more proper term for them.
However not all the tweaks are malicious. f.ex. text and some of the FPS tweaks.
We thought formatted text was interesting for teamplay which is what assault is about, also to make the fonts readable at higher resolutions, so we made a feature of it in 136.
Some FPS tweaks will be an option in 136 menus too.
-
Poll's results: it's obvious the community wants screen-shake, rockets texture and any kind of change in sounds to be blocked, so they will be...
As for weapons/projectiles textures there is a a small advantage for the 'BLOCK' option but it's a virtual tie.
Blocking them all will make half the community complain, allowing them will make the other half complain too.
Best solution is to block them all (BLOCK option won the voting anyway) then creating options in 136 menus for some alternative textures. Althought it will bring a whole new debate and we've already delayed the release enough because of tweaks discussions
Let's try to make it fast please -->
Here
_