![]() |
![]() |
|||
![]() |
||||
![]() |
||||
Frequently Asked Forum Questions | ![]() |
|||
![]() |
||||
![]() |
![]() |
|||
![]() | ||||
![]() | ||||
Search Older Posts on This Forum: Posts on Current Forum | Archived Posts | ||||
![]() | ||||
![]() | ||||
![]() | ||||
![]() | ||||
![]() | ||||
![]() |
: Maybe they will change their mind someday?
:
: https://forums.halowaypoint.com/yaf_postst187791_Should-343-use-modded-gametypes.aspx
343's enforcement on this has been pretty lax. But they'll also NEVER endorse modded gametypes, no matter how safe they are, as a company policy for liability and other reasons.
The fact of the matter is, as long as you only change what 343 can change, they can't detect a modded gametype anyway. The non-fixed nature of Megalo scripts means you can't detect the difference between a 'real' script and one a modder made. They can't tell what is a legitimate weapon parameter and what is not without impacting their own flexibility to change things.
So what I'd essentially take this as: people are free to make their own gametypes. However, they take the risk of being banned by uploading to their shares. You won't get in trouble for downloading a gametype to your box. I had a whole suite of modded Forge variants and gametypes in Halo 3 on my local box and never got banned, but I also never put them on my fileshare.
And if 343 decides to change any of this, you can be sure that just like Bungie, they'll sound the alarm from the Bulletin. As it stands though, modified gametypes that still follow the proper in-engine rules are essentially undetectable. And you can't use them to cheat in matchmaking, because they can definitely detect if you try to change the playlist files.