Mark said: > some of the variables he's mucking with are re-set in the more modern configuration files
First off, they aren't variables. There are, in fact, no variables in Quake macros. And those config files aren't official releases or anything. They're just files that were passed around unofficially to help people that weren't able to setup their own macros. > his failure to mention that you need commands like '-left' or '-attack' You only need the "-" version of a command to reset certain functions, or else to prematurely terminate sustaining functions that you want to run for only a limited period of time. For example, "+attack;wait;-attack" is only necessary when you want a key to fire a single shot. If you want a key to keep firing as long as you hold it down, then "+attack" will work just fine. And I might not have explained this part in detail, but my macros did use the syntax correctly. The question about the left command not working came from a user that was writing his own macros instead of copy/pasting mine. > not to mention never even discussing the three-dimensional nature of the game Attention all Audio Quake users! I know that you may have missed the sections in the manual about the targeting detector being able to tell you if a target is above or below you, the tones that indicate ledges that are in front of you and how high they are, etc, but, just in case you did, then you should be aware that Audio Quake is a 3D game. Sometimes, you have to jump off of a ledge to keep from falling to your death (pay attention, Mark). Also, sometimes you have to look up or down when shooting to hit someone that is on a platform, or, in case of the Jedi Quake mod, is flying around on a jet pack. Sorry I kept this super secret from everyone. lol I suppose the cat is out of the bag, now. Anyhow, here is some additional script goodness for you all. The following aliases and scripts will allow you to gradually look up and down in order to shoot at people that are above or below you. Normally, sighted users will hold a key or move a mouse until the angle is correct, but, since we can't judge that as accurately, I've made three macros for use in my own games. The first two look either up or down in fixed increments. The third is used to quickly snap your view/aim back to straight ahead. First, you need these aliases in order to time the movement of looking up or down. Oh, and the wait commands aren't to sabotage you so that you'll be an easy target. They're intended to cause you to wait before sending a new command while your player actually moves their head in the game. If you send the command to start looking up, and then immediately tell the server to stop moving looking up, then your head will have almost not moved at all. The LookPauseLong alias is used when you want to look completely at the sky, or completely at the ground. It gives you lots of time for your head to get from centerview to an extreme. LookPauseShort just gives enough time to move your head in steps. // Head movement timing aliases alias lookpauselong "wait;wait;wait;wait;wait;wait;wait;WAIT" alias lookpauseshort "wait;wait" // Head movement binds bind Q "+lookdown;lookpauselong;-lookdown" // Look at the ground bind q "+lookdown;lookpauseshort;-lookdown" // Look down a little bind E "+lookup;lookpauseLONG;-lookup" // Look at the sky bind e "+lookup;lookpauseshort;-lookup" // Look up a little BIND w "FORCE_CENTERVIEW" // Look straight ahead > after observing the number of players complaining that his "explanation," slowed them down and made them more inefficient Well, if you're accustomed to one keyboard layout, and you switch to another, then, of course, all of your old reflexes will need to be retrained. If I moved all of my commands to new keys, then I'd be slow until I got accustomed to the new arrangement, also. > for him to set himself up as some sort of quake master is incomprehensible to me. I can understand that. From your uninformed rants about the macros and accusations that I sabotage your gameplay with viruses, there are lots of things about computers that are incomprehensible to you. > The fact that he has recently called me "Mark," on the game, *DESPITE* my having switched player names in an attempt to > dodge this whole stupid business, is not only illegal but dishonorable and suspicious. Oh wow. So its illegal to call people by their names on the game? Oh no, come and lock me up! It is only against the rules to identify player names and link them to real people on this list, because this list is archived in a country with laws that force tons of record keeping that the admins would rather not deal with. However, the game chats aren't logged, and the Jedi Quake game is run from a server in Texas, so UK laws don't apply, anyway. And, if you want to stay anonymous, it isn't a good idea to start sending messages in game chat, accusing everyone of secretly being me because they're getting lots of frags, and talking about how I've hacked your computer. No matter what name you use, going on about those topics is a good way for people to identify who you are with out much effort. Bryan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark BurningHawk Sent: Sunday, June 03, 2007 11:56 AM To: AGRIP User and Developer discussion list Subject: [AGRIP-discuss] let's try this again, shall we? I do not wish to respond to Brian's personal attack on me, other than to say that I am disgusted with this list for not keeping the discussion less personal and for not putting a stop to them. When I accused Brian of cheating, or when I point out ways in which the "hard work," he has done to "explain," "macros is flawed and possibly sabotaged, while this is "personal," it pertains to the game, and is , as Brian's's is not, constrained by the technical nature of this list. Because I do not know precisely how something is done does not mean that I do not know it is being done. I am not by far the best quake player, rather I *WAS* not. However, for such an "experienced player," as Brian claims he is , not to know the mod well enough to understand that some of the variables he's mucking with are re-set in the more modern configuration files, his failure to mention that you need commands like '-left' or '-attack', not to mention never even discussing the three-dimensional nature of the game, and after observing the number of players complaining that his "explanation," slowed them down and made them more inefficient, is appalling. for him to set himself up as some sort of quake master is incomprehensible to me. The fact that he has recently called me "Mark," on the game, *DESPITE* my having switched player names in an attempt to dodge this whole stupid business, is not only illegal but dishonorable and suspicious. Because someone can be beaten does NOT mean they aren't using unfair advantage. Plenty of people beat me more than Brian ever did, and I didn't accuse them of anything. Brian had information, posted in his attack on me, which was privileged between one other player and myself, about the questions I was asking regarding how Brian might be cheating. His mention of a "virus on his PC," is something I have only discussed with one other individual. In conclusion, I'm done. I am unsubscribing from this list. While Brian will undoubtedly see this as a passive-aggressive temper tantrum, it's got more to do with the fact that this is just a game, and I have a life. I've tried to back up what I state with what objective information I have; it's apparently not enough. I'm the guy screaming that the house is on fire, while everyone inside thinks it's just a sunny day. It's simply not worth it. I apologize to the list for the band width this has taken. My words stand. --Mark BurningHawk Email: [EMAIL PROTECTED] my website: http://www.panix.com/~mbaxter Namaste _______________________________________________ AGRIP-discuss mailing list [email protected] http://lists.agrip.org.uk/cgi-bin/mailman/listinfo/agrip-discuss _______________________________________________ AGRIP-discuss mailing list [email protected] http://lists.agrip.org.uk/cgi-bin/mailman/listinfo/agrip-discuss
