Assassinations: Before You Go Gold

Games Other Halo
1

I do not like assassinations and I think they are a waste of time.

However, they are in the game and I’m going to have to deal with that.

So, I have devised a compromise that is so simple, 343 can’t ignore it.

In fact it’s so simple, they could even patch it in later.

My idea is a gameplay menu option called:

Assassination Behaviour (Similar in concept to Crouch Behaviour).

While accessing this menu item, you are presented with three options:

-Default: Tapping the melee button in an assassination situation will perform a simple beat down and holding the melee button will perform an assassination.

-Always Assassinate: Either tapping or holding the melee button when the opportunity for an assassination presents itself will always perform an assassination.

-Never Assassinate: Either tapping or holding the melee button when presented with the opportunity for an assassination will always result in a beat down.

See? Simple. This way I get my efficient gameplay, and whoever wants a time wasting kill move can have theirs in the same game.

And please people, don’t tell me “Just don’t hold the button!” or some crap.

If that worked flawlessly, I wouldn’t complain.

And look 343, I’ll even write some bad mock code of no particular language to guide the idea:

//Assassination Behaviour
//(Assumes player is within melee range of an enemy that can be assassinated).
.
bool ASSOPP = false;
int ASSOPPSET = 0;
string INPUT = X;
.
CHECK INPUT; /Determines which button is pressed and changes INPUT./
IF INPUT = MELEETAP OR IF INPUT = MELEEHOLD;
…(CHECKBACK ASSOPP; /Determines if target has back turned and changes ASSOPP to true if that is the case./
…IF ASSOPP = TRUE;
…(CHECKSET ASSOPPSET; /Determines which setting was chosen (Default = 0, Always = 1, Never = 2) and changes ASSOPPSET./
…IF ASSOPPSET = 0;
…(
…IF INPUT = MELEETAP;
…(MELEEATTACK);
…ELSE;
…(ASSASSINATION);
…)
…ELSEIF ASSOPPSET = 1;
…(ASSASSINATION)
…ELSE;
…(MELEEATTACK)
…)
…ELSE MELEEATTACK;
…)
ELSE (Do nothing);
INPUT = X;
ASSOPP = false;
ASSOPPSET = 0;
.
//End.

Something like that. You get the idea.

Make it happen!

2

I’m glade you gave a reasonable alternative to your problem with it but your making this more complicated than it needs to be. You have a choice either hold down the melee button or just tap it. It’s simple and better.

3

> I’m glade you gave a reasonable alternative to your problem with it but your making this more complicated than it needs to be. You have a choice either hold down the melee button or just tap it. It’s simple and better.

…

4

Didn’t they already say there was a menu option that turns off assassinations? I defenitely heard it around here somewhere.

5

or just press and not hold melee instead

6

> or just press and not hold melee instead

You’re the second guy in a thread with 3 replies that tells me this when I specifically said in my post not to tell me this because I know, and that it doesn’t work.

This solution works and is easy to implement. It’s no different than crouch behaviour. Jeez.

7

> Didn’t they already say there was a menu option that turns off assassinations? I defenitely heard it around here somewhere.

When you’re making custom games, yes.

What I’m asking for here is to make the button behave as if I only tap it or hold it as an option.

It doesn’t change the game; it just prevents you from making a stupid mistake by pressing a button 0.01 seconds too long.

8

> > I’m glade you gave a reasonable alternative to your problem with it but your making this more complicated than it needs to be. You have a choice either hold down the melee button or just tap it. It’s simple and better.
>
> …

I can’t believe one guy Thanked this post and another one quoted it disregarding the horrible grammar.

OP, asassinations are part of Halo. So are loadouts and all the stuff I know you hate because you don’t like CoD. Adapt.

9

I support this. Please give a valid reason as to why not. Someone.

10

> > I’m glade you gave a reasonable alternative to your problem with it but your making this more complicated than it needs to be. You have a choice either hold down the melee button or just tap it. It’s simple and better.
>
> …

I’m sorry OP, but almost everyone who posted here just gave the dumbest responses I’ve ever heard. Must be tired or something. I can relate completely. Half the time I think I tap the button but I preform the assassination, so your option would be great, and kind of obvious.

Support.

11

> > > I’m glade you gave a reasonable alternative to your problem with it but your making this more complicated than it needs to be. You have a choice either hold down the melee button or just tap it. It’s simple and better.
> >
> > …
>
> I can’t believe one guy Thanked this post and another one quoted it disregarding the horrible grammar.
>
> OP, asassinations are part of Halo. So are loadouts and all the stuff I know you hate because you don’t like CoD. Adapt.

Do you even understand what this post is about?

12

> > Didn’t they already say there was a menu option that turns off assassinations? I defenitely heard it around here somewhere.
>
> When you’re making custom games, yes.
>
> What I’m asking for here is to make the button behave as if I only tap it or hold it as an option.
>
> It doesn’t change the game; it just prevents you from making a stupid mistake by pressing a button 0.01 seconds too long.

Are you sure? I’m fairly sure they said something about a control setting.

13

Hay. So. In Reach I’ll be behind a guy, and I will TAP, not HOLD but TAP mind you, the right bumper. And I will go into a distracting, waste0of-time animation.

I think it’s easy to play Halo with a sense of style. You can make an assassination cool, or anything else you do. You don’t need a dumb 3rd-person animation. I feel like it’s catering to the 14-year-olds. “Oh wow, COOOOLL!!!”

14

> I support this. Please give a valid reason as to why not. Someone.

While there is margin of error of the game responding to the tap vs. hold scenario of Reach, one could argue that depending on how buried this option may be that it could be generally be exploited by the selection of never assassinate as most gamers may never bother to change their controls outside of the default given.

More over, I feel it’d be easier if certain playlists (or maybe gametypes under Pro varities) just had assassinations disable to completely remove the option on an equal and mandatory level instead of a manual level.

15

I agree that it gets annoying when you tap the button and youre drawn into the animation. I don’t object to this idea, it could work. I also find it hilarious after you explained how just tapping doesn’t always work people kept commenting it. WOW… You must have been livid.

Seriously to those that made those comments. Really… Just Really. Come on now, shame on you.

16

Excellent idea my dear sir! More Custom options are always a good thing! :slight_smile:

17

> Hay. So. In Reach I’ll be behind a guy, and I will TAP, not HOLD but TAP mind you, the right bumper. And I will go into a distracting, waste0of-time animation.
>
> I think it’s easy to play Halo with a sense of style. You can make an assassination cool, or anything else you do. You don’t need a dumb 3rd-person animation. I feel like it’s catering to the 14-year-olds. “Oh wow, COOOOLL!!!”

Yeah, this is what this suggestion’s for.

Since they’re not about to remove the assassinations, the best solution is a compromise and I think this works.

18

> > I support this. Please give a valid reason as to why not. Someone.
>
> While there is margin of error of the game responding to the tap vs. hold scenario of Reach, one could argue that depending on how buried this option may be that it could be generally be exploited by the selection of never assassinate as most gamers may never bother to change their controls outside of the default given.

Alright, so we need to remove the option of Toggle Crouch as well. And, on top of that, we should remove all alternative controller layouts. Can’t have that kid playing Bumper Jumper with an advantage.

> More over, I feel it’d be easier if certain playlists (or maybe gametypes under Pro varities) just had assassinations disable to completely remove the option on an equal and mandatory level instead of a manual level.

Well, the custom option to toggle on/off assassinations as they exist in their current state would eliminate the need for removing them in any playlist.

19

> I do not like assassinations: They are a waste of time and actually a detriment to gameplay in my opinion.
>
> However, I’m almost certain they are in the game, as I’m sure flashy animations attract some people.
>
> So, I have devised a compromise that is so simple, if 343 doesn’t include it in the final release, they are just lazy.
>
> In fact it’s so simple, they could even patch it in later.
>
>
> My idea is a gameplay menu option called:
>
> Assassination Behaviour (Similar in concept to Crouch Behaviour).
>
> While accessing this menu item, you are presented with three options:
>
> -Default: Tapping the melee button in an assassination situation will perform a simple beat down and holding the melee button will perform an assassination.
>
> -Always Assassinate: Either tapping or holding the melee button when the opportunity for an assassination presents itself will always perform an assassination.
>
> -Never Assassinate: Either tapping or holding the melee button when presented with the opportunity for an assassination will always result in a beat down.
>
>
> See? Simple. This way I get my efficient gameplay, and whoever wants a time wasting kill move can have theirs in the same game.
>
> And please people, don’t tell me “Just don’t hold the button!” or some crap.
>
> If that worked flawlessly, I wouldn’t complain.
>
>
> And look 343, I’ll even write some bad mock code of no particular language to guide the idea:
>
>
> //Assassination Behaviour
> //(Assumes player is within melee range of an enemy that can be assassinated).
> .
> bool ASSOPP = false;
> int ASSOPPSET = 0;
> string INPUT = X;
> .
> CHECK INPUT; /Determines which button is pressed and changes INPUT./
> IF INPUT = MELEETAP OR IF INPUT = MELEEHOLD;
> …(CHECKBACK ASSOPP; /Determines if target has back turned and changes ASSOPP to true if that is the case./
> …IF ASSOPP = TRUE;
> …(CHECKSET ASSOPPSET; /Determines which setting was chosen (Default = 0, Always = 1, Never = 2) and changes ASSOPPSET./
> …IF ASSOPPSET = 0;
> …(
> …IF INPUT = MELEETAP;
> …(MELEEATTACK);
> …ELSE;
> …(ASSASSINATION);
> …)
> …ELSEIF ASSOPPSET = 1;
> …(ASSASSINATION)
> …ELSE;
> …(MELEEATTACK)
> …)
> …ELSE MELEEATTACK;
> …)
> ELSE (Do nothing);
> INPUT = X;
> ASSOPP = false;
> ASSOPPSET = 0;
> .
> //End.
>
>
> Something like that. You get the idea.
>
> Make it happen!

Finally someone who understands how to deal with the assassination problem. Unlike you, I actually like assassinations, but I agree that there needs to be some way to deal with the problem of people not having fine control over when they assassinate and when they don’t. Your suggestion is perfect.

However, I disagree that the only reason 343 would not put this in would be if they were lazy. Perhaps they want to intentionally make beat downs difficult for players, for some reason.

20

EDIT: Sorry, double post.