No out of bounds on Grifball?

Games Halo 5: Guardians
1

This is dumb, players getting out of the grifball court. You are ruining the game. 343 please fix this and make a kill boundry that spawns when the game starts

2

I think they are doing that in the update thats out literally right now

3

> 2535405450804460;2:
> I think they are doing that in the update thats out literally right now

players are still getting outside of the map. lol Oh you mean now now cause I can’t even access the lobby LOL

4

I think it’s hilarious. Adds a new spice to the game. You’ve just gotta keep them from getting out! control the ball!

5

> 2628440139686205;4:
> I think it’s hilarious. Adds a new spice to the game. You’ve just gotta keep them from getting out! control the ball!

Yeah I tried to betray them but before I knew it, they were already outside.

6

> 2535409103705542;3:
> > 2535405450804460;2:
> > I think they are doing that in the update thats out literally right now
>
>
> players are still getting outside of the map. lol Oh you mean now now cause I can’t even access the lobby LOL

Yeah 343 listened when you said 343 fix this

7

Peep this: (let us know if it worked)

CONTENT UPDATE NOTES
3.1.16 Update:

  • Fixed an issue that caused invisible map barriers and walls to not function correctly, allowing players and objects to get outside the intended boundaries of a map - Fixed an issue that caused gravity volumes to not function as intended
8

> 2535405450804460;6:
> > 2535409103705542;3:
> > > 2535405450804460;2:
> > > I think they are doing that in the update thats out literally right now
> >
> >
> > players are still getting outside of the map. lol Oh you mean now now cause I can’t even access the lobby LOL
>
>
> Yeah 343 listened when you said 343 fix this

It took awhile for the download to start :l

9

> 2533274875982754;7:
> Peep this: (let us know if it worked)
>
> CONTENT UPDATE NOTES
> 3.1.16 Update:
>
> - Fixed an issue that caused invisible map barriers and walls to not function correctly, allowing players and objects to get outside the intended boundaries of a map
> - Fixed an issue that caused gravity volumes to not function as intended

yaaay lock this thread. lol

10

Do you not read other posts? Like ever?

11

Kill boundaries got glitched in development.

12

> 2560081931056311;10:
> Do you not read other posts? Like ever?

Did you not read any post on this thread?

13

Damn…I was playing last night with some friends and it was probably the most fun I’ve had in Halo 5 for a while. Just because it felt like Halo 2 again with people glitching and getting outside of maps and whatnot. If you find out how to get passed the outside mountain wall there is a whale figure that you can try to hammer into the court.

14

> 2535405450804460;12:
> > 2560081931056311;10:
> > Do you not read other posts? Like ever?
>
>
> Did you not read any post on this thread?

I don’t understand your question. I was asking because this post has been made hundreds of times over the last week.

15

It only took them a few days to patch it… BUT an update is live now that fixes that. Your prayers have been answered my friend.

3.1.16 Update:

  • Fixed an issue that caused invisible map barriers and walls to not function correctly, allowing players and objects to get outside the intended boundaries of a map - Fixed an issue that caused gravity volumes to not function as intendedMultiplayer:

  • New Arena map added: Torque - New game types added to Arena: Grifball, Assault, and Fiesta Slayer - Gravity Hammer added to Warzone, Arena, and Forge - Halo: Combat Evolved M6D Pistol added to Warzone and Forge - Players can no longer “re-roll” random weapon REQs in Warzone - Implemented stricter idle boot duration period - Fixed an issue with kill feed not showing weapon icon and Perfect Kill medal for the Halo 2 Battle Rifle - Fixed an issue where the Mantis Destroyed medal was not being awarded for destroying a Mantis(Source: https://www.halowaypoint.com/en-us/games/halo-5-guardians/updates/Hammer-Storm)

I thought the MP adjustments were already fixed, but they did not denote that separately so I am not sure. This was all under 3.1.16 update and above 2.26.16 update

16

Locked at OP’s request.