Also my opinion. If there is the posibilty to disable all scripts we should disable them. I also was thinking about using a script to have arty strike on one button. For the last flag on escort this could be deciding. But it is always lame to win because of a feature, that is unknown to most other players.
dont get me wrong, i think that if you can do it with console you should knock yourself out but autosniping is exploiting
Shadow and SIP are both retarded. What do you mean by "scripting a squad arty command to do it instantly" You mean "emp_menu_quickcmd 6 3" for Squad arty or 6 1 for your other squad command? It's a console command, I don't see what you mean when you say you scripted it shadow. Every single F-menu command has a console command for it. You did exactly 0 scripting for that. Also, these scripts aren't cheating, although the scunt rifle one will probably be looked down upon, but the rest are fine. Useless, because anyone who needs a script to control their mouse clicks is doomed to fail anyway, but still fine.
All you did in that code box, was alias emp_menu_quick cmd to something else, and then use that something else. I.e. You added another name for a console command you won't use purely because you already bound a key for it. I don't see why you don't just bind emp_menu_quickcmd rather than aliasing it to something else, and then binding that something else. It's just pointless. And SIP is more retarded, I saw no problem until you claimed to have scripted a way to do squad arty, when all you did was bind a console command to a key. That's like me saying "HEY GUIZ, GUESS WHAT, I WROTE THIS SCRIPT SO YOUR SENSITIVITY DROPS BY 10x WHEN YOU GO INTO SCOPED/IRONSIGHT MODE" Code: zoom_sensitivity_ratio 0.1 I didn't script that, it's just a console command.
I aliased it so people could understand which set of squad powers they were using. Don't knock my easy4nubs style D;
@Trickster: I don't matter in which way people use console commands or scripts. It's just unfair for all the other players, who doesn't know about this. So my opinion is still give these little tricks to everybody (maybe in the wiki) or disable them. Update: Just saw, that it's already in the wiki.
'nuther one. This one slows your sensitivity whilst shooting, make it easier to aim at longer ranges.
Aren't scripts useless while playing on a server if they're clientside? Or are these serverside >_>. Anyway, console command or not, it makes life easier for the noobs which is their purpose, and if they fulfill their purpose then they aren't crap are they? What's the point of flaming anyway? Just say they're doing something really easy and be done with it, 3 words doesn't need to turn into an entire paragraph.
To lessen server lag, the scripts are the same client and server side. the game uses client side scripts for immediate information, for instance, research prerequisites or armor costs or weights, etc. You can delete the research pre requisites or change the descriptions of researches or weapons in your scripts folder, and they'll either appear on the vehicle customization menu or they'll change the actual discription, regardless of whether or not you've researched the items. However, when doing things like buying tanks, the server checks the server side scripts to see if an item has been researched or what not. Mostly, client side scripts are used for stuff like the spray pattern you see when shooting your gun, or to predict when to show a blood splatter or make the sound of a person getting hit when you hit them. If you haven't noticed, just because someone has some blood spilling out of them doesn't mean they were hit. This is most evident with melee, where the hit prediction is often wrong according to the server. Basically empires uses the client side scripts for as much as possible without comprimising the game. For instance, when figuring damage, the server will calculate damage with it's own scripts rather than the client side scripts
Let's not split hairs on the definition of a "Script" people.... All of these are client side scripts. They are typically ways of binding an otherwise simple action that the client can do to make things easier (or harder, but that would just be stupid). For example, let's say you have a single-shot weapon. The way this works is for every +attack (button down click of your mouse) the client fires to the server you fired a bullet. If you click really fast, these commands head off to the server. But it's not tracking your mouse clicks, it's checking your bullet fires. So, if say you wanted to double your firing speed, you could script it such that one mouse click counts as two +attack triggers. Boom, instant increase in damage potential. Doesn't mean squat if you can't aim, but you get the picture. Some games prevent this by also adding in a cap on the refire rate of their single-shot weapons. There are Amxmodx server mods that you can run that essentially ban scripting on the client side. There are sneaky ways around it, but then you're intentionally going against the server's rules (i.e. no scripts). The way they do it is check if there's any special bindings that shouldn't be there. So, even your shortcut key to arty strike would be banned. I personally have no problem unless they allow an exploit (as mentioned above).
,_, Scripts CAN NOT allow exploits. Scripts themselves are exploits. You NEGATE that if everyone has the exploit, WHICH I'M DOING. <___________________<
I like the idea of clicking once to fire twice, I always have trouble with shooting the pistol since it skips my second command :/, I'll look into that. Hope it's not considered cheating, it's not like I'm giving myself infinite ammo or something (though that would be a neat feature...hmmm.)
