@Robloxian-Craft Animates ent_fire !picker setteam # (replace # with 2 for red, 3 for blu) for already spawned sentries OR ent_create obj_sentrygun teamnum # (2 for red, 3 for blu)
We did have this info almost that many years ago. SourceMod server plugin devs like myself knew about the Unassigned team for years. It's well known to us.
I remember while playing on Skial DeathRun 2 or 3 years ago, there was a glitch where if you typed "join_class [classname]" in the console before joining a team, you'd instantly spawn at point 0,0 on the map with BLU colored cosmetics. If you change to RED team, your cosmetics would stay blue but you'd otherwise look red. If the map being played on had point 0,0 on the playable area, you could use this to play tricks on the other players. Then one day, I tried this glitch and it allowed me to skip past the team assignment entirely, keeping me on team unassigned. I wrecked some of my teammates for a bit, and then they killed me (notably, the kill feed showed my name in grey). I wish I could've recorded this happening, because it only worked once and sadly they have long since fixed the glitch. I can never reproduce it anymore and I wish I could try it just once more. Thank you for igniting a burning memory with this video, appreciate your hard work!
imagining a cursed halloween map where merasmus converts a selection of the server to be his minions on team unassigned, and they get switched back after they get killed
@@MrFireWolfFreak fortress bosses do not put you on team "UNASSIGNED" they actually put you on team BLU (Since the normal players are RED and the boss player is BLU) but I get what you mean.
"But the jetpack will push unassigned teammates.. for some reason." I love how Source is so convoluted and difficult to explain that even Shounic sometimes finds something he can only shrug and say "I don't know" in response to.
Nah he just didn't look it up and it would need digging through code for something silly and not normally seen Otherwise it would be a small snippet about why
isnt the jetpack programmed to push players when you use it? its probably working only on gray players cuz they are the only one with collision in this sittuation
You could do a wrangler based gamemode with unassigned players since they don’t target red team, making the wrangler the only option for attacking. (Red vs Unassigned in some way)
Red team would have to be disallowed from playing engineer in order to differentiate red team from team unassigned, since they both use the same model textures. Other than that it would be pretty much fine, except that team unassigned would have always be defense since they can't cap, and they also wouldn't be able to block capture so rushing point would be meta for red, and very hard to counter by team unassigned
Players aren't meant to be on Unassigned, really. When we put players on Unassigned using a sourcemod server plugin and that player died, it'd crash the player off the server.
I think some custom MVM missions have used this for gray robots hostile to both regular teams. EDIT: Specifically, gray robots hostile to the red team and to the regular robots.
Its how it should be story wise too, i wonder why valve didnt use this mixef with boss truce mechanic for MvM. Probably for simplicity coding the mode.
@@liloak00 Always those playtesters... Its why we cant have nice things. People can be friendly so often ingame i think people would get a hand of it, especially if it was to a point it is a comsetic difference and both teams can heal and buff each other in MvM.
So interesting, because this feels like a "Neutral party" that doesn't care about team Red's or Blu's feeble goals. Their priorities are above your comprehension
imagine the lore for the mysterious and legendary unassigned engineer with his blue sentry that kills his own master and has a truce with red team and his blue teleporter that telefrags itself
In TFC there were 4 teams - but you could actually assign players to "teams" 5,6,7 and so on via memory edits/editing mods. One of the teams would give you the text "FOR 5 SECONDS" as the team name, as it's overflowing a read in string table. Beyond 6 or so you would just crash the server and every single connected player. Simpler times.
I'd actually like to see an extra clip of this. At 2:10 or so, to me it looked more like it could damage an already on-fire player, but the first hit on BLU that did damage was only after RED's fire went out. Could just be coincidence, but some extra testing would be interesting. EDIT: Nevermind me, at 4:46 a similar thing happens and my hypothesis is destroyed. It really is due to range for BLU.
Internally there must be two different checks that are used depending on the distance, and they happen to give opposite results. For whatever reason, there's a transition from one section of code to another after a certain distance or amount of time passes. My guess would be that it's the point where the game stops checking to make sure that the flare doesn't collide with the person that just shot it.
I like how this is basically a mismatch of the consequences of some checks being 'if player is/isn't my team' versus 'if player is/isn't any other team'. It doesn't matter at all until you official support a third playable team, so none of these are 'bugs'. (Also, probably a lot of these are consequences of halloween/mvm type modes where you fight NPC enemies, and just picking whatever interaction made those modes work well.)
My thoughts exactly, basically all of these interactions come from different ways of various things checking what team someone is on. All of them function perfectly when the players involved are on valid teams, so this unexpected behavior isn't an issue as long as players stay on valid teams.
I remember hackers exploiting Team Unassigned on the PS3 version. They would punish regular players by forcing them onto that team, keeping them from joining another team or doing anything aside from disconnecting.
I know im not the only one thinkin this, why tf was ps3 network toxic as hell? COD series had rage hackers for days, they purposely ddos littlebigplanet servers, they gate kept a lot of obscure game titles like lost planet and soulcalibur, constantly did facebook scams in inbox
@Thats Legit Sony begged for it. Do not tempt Linux fanatics. And definitely don't lock out their OS after you used it being able to install and run on the console as a major selling point.
One of your best videos yet. A couple points: 1. The purple Monoculus effects made me realize it's like a compromise against RED and BLU. 2. You should test a modded server where one team is Unassigned (but with PRP 🟪 textures). This stuff is so delicious to me, nice work Shounic san.
This is actually what I stumbled upon years ago on VHS servers. Where I type in joinclass Spy without choosing teams, I spawn in as a blu Spy that could kill RED and damage Hale. Was nuts.
It's kinda funny that you can see why most of these things work like this too, there's just a bunch of different ways to code things to work with the enemy/allied team, especially assuming there's only red and blu
i'm imagining a 3-team gamemode (no idea what map it'd work in) where you can play as unassigned and get to spawn in halloween NPCs to compensate for their jank
I'm assuming it wouldn't work but since the halloween bosses share team unassigned I was wondering if medic could heal them in any capacity. Otherwise, really cool video and impressive amount of testing.
@@Underqualified_Gunman No skeletons are nextbots, that's why you can kill them even if you are in team unassigned. I'm also pretty sure every other halloween npcs are also nextbots.
@@billybobjoephilcorncobtiptopge Small flaw in your logic. You can hurt the skeletons while unassigned but you can't damage the bosses while unassigned. For your argument for the bosses being nextbots to make sense would require the bosses to be capable of being damaged by an unassigned player.
about unassigned, there's a random dice roll regarding ragdolls of the unassigned team, that makes tf2 client crash, it's somehow related to materials loading function, with that said you can trigger the crash by using the dead ringer or just dying, maybe it's also related to hats
I love how everything is completely random here. You get a bit of both logics at the same time. And honestly, even as a dev, I have no idea how the hell that can happen. You would easily imagine there's are weird "rules" as each components are treated differently (aka spawn doors) But the flare hitting or not hitting close/long range vs red/blue hitbox detection is an absolute mystery. Even if you wanted, you would struggle to make up such rules ! Thanks for testing them all. Great stuff right there
probably a case of the arming distance for flare been broken. whit arming distance a distance anything need to fly before X can happen, Real life it can explode. TF2 mostly pass through friendly.
its probably just a case of when your not on red or blue the code defaults to one team then after having added over a hundred different weapons and you'll run into cases were the default was red for one weapon and vice versa.
Team unassigned reminds me of modded PS3 days where you could make a bind to set someone to team unassigned which wouldn't allow them to select a class and would force them to leave the server unless they had a team change bind which is good for targeting some modders. You could also target buildings to make them destroyable by any team.
I remember this happening to me in an idle server. I had HTML MOTD off, and the server had a dumb thing where it was supposed to put you in spectator until you turned HTML back on. I don't know what happened then, but it put me on this team instead of spectator, and I did a little messing around with everyone else. Pretty fun bug, would do it again if I knew it still worked.
Considering the "unassigned" team is also used for the holloween bosses, I'd assume unassigned players are treated the same way, and are unaffected by the truce
It would be awesome if this was fleshed out some more, even if it’s inaccessible. Being a Jester of sorts and helping/harming whichever team you want (and being on Merasmus’ side during Halloween) would be such an interesting phenomenon to have available to us. I mean yeah, we can technically already do that to a degree, but being able to kill “teammates” and heal “enemies” would add another chaotic layer to it 😂
This has some interesting potential for a Red VS Blu VS Modified Unassigned (for balance and fixes, if at all possible). Like two team competitive VSH or MVM, or two teams fighting against eachother and a Halloween mob army "led" by a single, VSH-esque unassigned player. The creativity this could open if the jank is tamable and fixable is great.
Great video, it was actually very fun to give you (alongside other chat members) ideas of what things to test, and it's good to see that everything made it through even as cliffnotes.
I could imagine this as some sort of "Purgatory" team for an Arena like mode, much like that halloween map where you become dispenser ghosts upon death. Maybe you'd be faced with significant de-buffs but if you can get a 3 killstreak you will be put on either Red or Blu.
It would be good like 3 team Red & Blue players Fight Unassigned player Red & Blue can damage eachother but there main objective it to stop unassigned player from destroying the world I had custom map idea name - Day of the Reckoning Gamemode -unknown Red & Blue spawn is seperate but they will lead path to the exit gray team which im call unassigned team as gray Will be running and hiding from them but if you dont kill them in the next 1:30m they will summon all the boss which is why i named this map "day of the reckoning" Might seem like "oh easy mode but if you dont kill them they will summon 'it' and it will be a massacre"
I think a pretty cool concept would be having Team Unassigned defend from Red/Blu trying to capture the points while they try to “unassign” other points.
Honestly I'd LOVE to see a long ass video of the quirks behind the unassigned team. It's so funny seeing the things we've never known about this beautiful shit show of a game
A fun quirk of the 4th team you can 'exploit' in game is to join a casual server during warmup, and simply don't do anything. When the game eventually starts, you'll be able to spectate Blu team members (and the bomb on payload) indefinitely, and you'll appear as a dead blu team member on the scoreboard and in the chat.
I'm not sure if its possible due to Source's spaghetti code, but if someone manages to hijack the way unassigned team works people could make some pretty cool shit out of this.
Team Unassigned is technically also used in HL2 Deathmatch, but only if Teamplay is disabled. You can see it if you input the console command "jointeam #" with a value from 2 to 3, with it stating you joined team "Unassigned" instead of either the Combine or Rebels. The mod Open Fortress features Free-for-All, and you can choose a color for your Mercenary's outfit.
Well i found a fact. Did you know an Unassigned, can't hurt blue from small distance? well it's because the projectile of the flare-gun and e.t.c. When the blue player tries to shoot projectile through his teammate, the game decides to ignore the collisions between the player and projectile from the smallest range. [If not then explode, red or from far away]. But unassigned ignores blue for some reason, but not red. It's because: blue and the unassigned have the same value team [ prob idk ]
I remember back in CS 1.6, a server I played on had a mod that would allow (unintentionally, I believe) spectators to spawn in as a player. They couldn't purchase anything and were hostile to both teams and vice versa. That allowed for a lot of fun.
I love how whenever you dissect TF2’s code, Blu team always seems to have a tiny bit more of an advantage, like how in the cart video when the carts where fast enough, Red’s got stuck but Blu’s never did and just sped ahead. Then in the video Blu is immune to some damage while Red is not
the unassigned team reminds me of this old glitch i used to play around with, to make players think that sentries were haunted i'd enter a match(arena) and using a team assignment bug(you had to re-enter the match BEFORE the start of a round once you loaded in), i would have the role of spectator but was able to directly spectate engineers as an unassigned player the sentries would immediately shoot wherever this "ghost" was, and you could spectate engineers to have sentries fire at their creators it's still around, i just can't remember too clearly what you had to do to achieve this..
Not quite the same, but Team Fortress Classic had a yellow and green team that were used on a couple of special four team maps. You could use the console as a spy to disguise as yellow/green on the standard red/blue maps... that was always fun.
Imagine they used this to have some Event stuff where a random player would become some Mega Boss and get a boatload of buffs. Or some special map where unassigned had to try and abuse their weird spaghetti mechanics to force a stalemate.
@@s0nnyburnett Small problem. VS Hale has 2 teams. The red team and Saxton Hale. What is being suggested here has 3 teams. Red, blu, and Saxton Hale. Another thing, VS Hale sees the Red team trying to Kill the Hale and Hale trying to kill the Red team. This has the Red and Blu teams fighting over an objective while the Hale tries to keep both teams from completing the objective. Really, the only similarity between the suggestion put forth here and th VSH community gamemode is the fact that it's asymmetrical.
@@ovaiggy Small problem. VS Hale has 2 teams. The red team and Saxton Hale. What is being suggested here has 3 teams. Red, blu, and Saxton Hale. Another thing, VS Hale sees the Red team trying to Kill the Hale and Hale trying to kill the Red team. The original comment didn't actually say anything about the objective in the first part of the comment so I can't actually make a proper comparison there. But honestly, the only similarity between VSH and the first part of the comment is the fact that one player is put on a separate team from everyone else and is given a bunch of buffs to compensate.
Unassigned (Grey) should be a free for all / troll team. When you choose that "team", everyone can attack you, and you can attack everyone. The downsides are you can't cap intelligence, cant go into the safe rooms, cant have medics on red / blu heal you, cant use red / blu teleporters, can't push carts, no ability to see players outlines including your own teammates, cant get ammo and health fromred / blue dispensers, and I could go on! Team Unassigned (Grey) should be played like everyone against me whether for fun, as a personal challenge, or to disrupt and troll the match.
This feels like a potential Miss Pauling class option. One of 'em per game, a-la Saxton Hale, but instead of being like a boss everyone else has to fight, Pauling just runs around doing crowd control, for lack of a better word. Bonking people back to spawn, if they get too far, delivering intelligence back to where it should be, and generally being like an administrator of the game (aha get it because Pauling works directly under the actual Administrator) that makes sure people don't get too carried away, and distracted from the main objective, which she herself can't complete. I guess she'd be kind of like a babysitter for a match, unless the person playing her wants to goof around as well. Lot of comedic potential in Pauling standing outside of the spawn door, like "Come on, guys. Let me in.", with the poor BLU team huddled in a corner, knowing that if they let her in, they won't be able to take a single step off the spawn grounds.
This could be a fun concept for a necromancer/wizard gamemode where it's a normal blu vs. red match but every once in a while the top score player gets auto-balanced to unassigned and gets random halloween spells over time while being able to spawn skeletons with a cooldown.
This reminds me of the 4-team gamemode in TF2 Classic. I wish that someone could make a vscript map/gamemode that allows for more than 2 teams. It would result in some interesting shenanigans!
I noticed that Fistful of Frags, another Source game, uses team unassigned for the free-for-all gamemode, people just spawn in with a randomly picked skin out of the 4 normal teams
tl;dr 4th team is "unassigned", used for players before they pick a team (when spectator is disabled), neutral control points, the objective on doomsday, halloween enemies (and krampus) and certain other map elements. on the whole works as its own team gameplay-wise pretty well, with the only bugs being with close-range projectiles, buildings, and misc stuff like the shortstop shove or YER disguises. visually you look red, but your hud and projectiles are blue, basically cus the code checks if youre red, and if not you look blue, and vice versa. in chat & the killfeed youre grey, and in the tab menu youre a spectator.
Team Unassigned would technically be used during deathmatch sessions, which HL2 Deathmatch does if teamplay is off. TF2 does not feature FFA however, so team Unassigned is very much a leftover that was given a purpose.
On tf2 dodgeball you could abuse the unassigned team to spawn into red or blue team even when a match was already running and some players already died. For example you could join when it was left to a 1v1. If I remember correctly, you join a server, but don't choose any team and also don't join spec, then wait for a map change, then join spectator, and then join red or blue and you would spawn in instantly. Useful for helping the winning team win even more, or for getting lots of kills if you join the losing team.
Memories of this glitch back in UGC servers that set your team to spectator without killing you (technically putting you in unassigned) , oh boy i remember the chaos that happened during those times, another side effect it had at the time was that if you did it with a revved up minigun, it would stay revved up but you'd run in the normal heavy walking speed, and oh boy did it cause unassigned heavies (especially with brass beast) to wreck havoc upon everyone on the server.
Would looking at these interactions in a build that predates stuff like Halloween and other npc uses of the unassigned team be likely to have any interesting effects?
My best guess would be that either "unassigned" was a copy-paste from one of the other teams, or else it was the first team made and then the others were copy-pasted from it and edited. Some of the additional weirdness probably comes from it being edited at some point for the halloween and/ or robot mode (I can't fucking remember what it's called, I've never played it), and because the copy-paste probably happened at some point in the middle of development when shit was half-done.
I think it happened to me randomly one day while playing casual mode: in setup time we were goofing out between teams, waiting for other players.Then the time counter ended right when i was forcing myself through a bunch of blue and red players and i was auto-balanced right after. I kept playing like usal but there was something really wrong with the game, like going through blue team while being in red team, my preview class was blue instead of red... It was really strange. I think I triggered some glitch.
imagine if there was a server network dedicated to you being able to join team unassigned like how this guy did it would be like having a new tf2 update
This must be why sentries summoned with commands act so weird, they’re on team unassigned.
if you do not specify in the command on which team they should be on they get on team unassigned so yes
Pog!
How do we make them red then?
@Robloxian-Craft Animates ent_fire !picker setteam # (replace # with 2 for red, 3 for blu) for already spawned sentries OR ent_create obj_sentrygun teamnum # (2 for red, 3 for blu)
@@linustrain thank you
if we had this information 10-15 years ago people would have made a lot of fan content about Unassigned as if it were a real faction.
Yeah they would have been the dark spoky team from gray man.
i mean OWN exists
it would've been on the comic
I am sure someone will do it now
We did have this info almost that many years ago. SourceMod server plugin devs like myself knew about the Unassigned team for years. It's well known to us.
I remember while playing on Skial DeathRun 2 or 3 years ago, there was a glitch where if you typed "join_class [classname]" in the console before joining a team, you'd instantly spawn at point 0,0 on the map with BLU colored cosmetics. If you change to RED team, your cosmetics would stay blue but you'd otherwise look red. If the map being played on had point 0,0 on the playable area, you could use this to play tricks on the other players.
Then one day, I tried this glitch and it allowed me to skip past the team assignment entirely, keeping me on team unassigned. I wrecked some of my teammates for a bit, and then they killed me (notably, the kill feed showed my name in grey). I wish I could've recorded this happening, because it only worked once and sadly they have long since fixed the glitch. I can never reproduce it anymore and I wish I could try it just once more.
Thank you for igniting a burning memory with this video, appreciate your hard work!
Burning memory?
Yes
It's all just a burning memory, huh?
Did this on cocainum, airblasted people into the death zones on the side. I was banned for a week lol
New Brain Bit Unlocked: *The Strange Festive Burning Memory*
imagining a cursed halloween map where merasmus converts a selection of the server to be his minions on team unassigned, and they get switched back after they get killed
Or after Merasmus dies. We can't forget about that.
there are freak fortress bosses that work like this
@@MrFireWolfFreak fortress bosses do not put you on team "UNASSIGNED" they actually put you on team BLU (Since the normal players are RED and the boss player is BLU) but I get what you mean.
5:03 After being killed so many times by the engineer that wanted guaranteed crits with the frontier justice, the sentry decided to take revenge
Or because he farmes strange wrench/pda
Don't trust them, Pumpkin Man! They're a furry!
@@davidvelasco4423 sounds like scary thing
"You killed me for guaranteed crits, so i will do the same!"
slugcat !!!
Finally, Gray Mann's team is playable!
Kidnapping by eagle sold separately
robots in mvm are on team unassigned - confirmed
Nah this is the administrator's team. Red+Blue=Purple
His team is blu
@@tye-wynd5218no he's not blu is Blutarch Mann
"But the jetpack will push unassigned teammates.. for some reason."
I love how Source is so convoluted and difficult to explain that even Shounic sometimes finds something he can only shrug and say "I don't know" in response to.
Spaghetti monster moment
It doesnt mean he dont know, he just don't told us since its not an interesting information
Nah he just didn't look it up and it would need digging through code for something silly and not normally seen
Otherwise it would be a small snippet about why
isnt the jetpack programmed to push players when you use it? its probably working only on gray players cuz they are the only one with collision in this sittuation
@@Dr_Dan_ Jetpack overwrites player velocity
"The teleporter has a heart attack" caught me so off guard
You could do a wrangler based gamemode with unassigned players since they don’t target red team, making the wrangler the only option for attacking. (Red vs Unassigned in some way)
Amazing idea! There’d have to be some balancing cause I feel like if one person gets the upper hand they’ll never lose.
Red team would have to be disallowed from playing engineer in order to differentiate red team from team unassigned, since they both use the same model textures. Other than that it would be pretty much fine, except that team unassigned would have always be defense since they can't cap, and they also wouldn't be able to block capture so rushing point would be meta for red, and very hard to counter by team unassigned
I think i wouod also be awsome to have a VSH like gamemode like this, it would be like fighting merasmus on Halloween.
Players aren't meant to be on Unassigned, really. When we put players on Unassigned using a sourcemod server plugin and that player died, it'd crash the player off the server.
@@JustinTrudeauIsASexGodgeez, the game _really_ hates unassigned, huh?
I think some custom MVM missions have used this for gray robots hostile to both regular teams.
EDIT: Specifically, gray robots hostile to the red team and to the regular robots.
Its how it should be story wise too, i wonder why valve didnt use this mixef with boss truce mechanic for MvM. Probably for simplicity coding the mode.
@@Kacpa2 iirc the story was playtesters kept trying to kill eachother so they just made everyone red
@@Kacpa2 Valve's infamous play-testers got too confused at the concept of working with the opposite team color.
@@liloak00 Always those playtesters... Its why we cant have nice things. People can be friendly so often ingame i think people would get a hand of it, especially if it was to a point it is a comsetic difference and both teams can heal and buff each other in MvM.
@@liloak00 I think some custom servers let the players be red or blue on the same team?
So interesting, because this feels like a "Neutral party" that doesn't care about team Red's or Blu's feeble goals. Their priorities are above your comprehension
Gray Mann finally decided to hire his own mercenaries
@@billybobjoephilcorncobtiptopge He did hire TF classic team in the comics.
Unassigned engineer, in particular, seems to have goals beyond anyone's understanding.
his goal is to end the game by stalemate
only he wins
imagine the lore for the mysterious and legendary unassigned engineer with his blue sentry that kills his own master and has a truce with red team and his blue teleporter that telefrags itself
In TFC there were 4 teams - but you could actually assign players to "teams" 5,6,7 and so on via memory edits/editing mods. One of the teams would give you the text "FOR 5 SECONDS" as the team name, as it's overflowing a read in string table. Beyond 6 or so you would just crash the server and every single connected player.
Simpler times.
teams are RED, GRN, BLU, YLW and FOR 5 SECONDS
COULD YOU STOP USING THE FORBIDDEN TEAMS
FOR 5 SECONDS
A lot of these "make sense" especially with the if not red then blu logic. But the flare gun range thing? Wtf is going on there?
nutsack
Same check for team colour passthrough makes it break apparently.
I suspect the flaregun passthrough is just a case of the code defaults to blu if its not red.
I'd actually like to see an extra clip of this. At 2:10 or so, to me it looked more like it could damage an already on-fire player, but the first hit on BLU that did damage was only after RED's fire went out. Could just be coincidence, but some extra testing would be interesting.
EDIT: Nevermind me, at 4:46 a similar thing happens and my hypothesis is destroyed. It really is due to range for BLU.
Internally there must be two different checks that are used depending on the distance, and they happen to give opposite results. For whatever reason, there's a transition from one section of code to another after a certain distance or amount of time passes. My guess would be that it's the point where the game stops checking to make sure that the flare doesn't collide with the person that just shot it.
Team Fourtress
Team Fortress 2 Classic
Fortress Team
Team 4tress.
We've expecting Team fortress 3 but we forgot Valve had Threefobia so we will have Team Fourtress 4 confirmed! 🎉🎉
team 5tress
I like how this is basically a mismatch of the consequences of some checks being 'if player is/isn't my team' versus 'if player is/isn't any other team'. It doesn't matter at all until you official support a third playable team, so none of these are 'bugs'. (Also, probably a lot of these are consequences of halloween/mvm type modes where you fight NPC enemies, and just picking whatever interaction made those modes work well.)
My thoughts exactly, basically all of these interactions come from different ways of various things checking what team someone is on. All of them function perfectly when the players involved are on valid teams, so this unexpected behavior isn't an issue as long as players stay on valid teams.
I remember hackers exploiting Team Unassigned on the PS3 version. They would punish regular players by forcing them onto that team, keeping them from joining another team or doing anything aside from disconnecting.
they would shit their pants if you forced host, noclipped out of spawn and stripped them of their godmode powers to terrorize the entire server lmao
I know im not the only one thinkin this, why tf was ps3 network toxic as hell? COD series had rage hackers for days, they purposely ddos littlebigplanet servers, they gate kept a lot of obscure game titles like lost planet and soulcalibur, constantly did facebook scams in inbox
@@thatslegit
Yikes...
@Thats Legit
Sony begged for it. Do not tempt Linux fanatics. And definitely don't lock out their OS after you used it being able to install and run on the console as a major selling point.
@@freedustin I mean, fair. Doesn't mean they have to ruin the experience for others though.
I enjoy this cursed 4th team and its blursed neutral mechanics. Excited to see what people will do with this new found knowledge for cursed gamemodes.
0:01 team bread
Are you telling me, that the sentries, after being made existent in this plane by the engineer, instantly regret their choices and start killing him?
Unassigned engineer chose not to include the 3 laws of robotics in his sentry.
And then the sentry chose violence.
One of your best videos yet. A couple points:
1. The purple Monoculus effects made me realize it's like a compromise against RED and BLU.
2. You should test a modded server where one team is Unassigned (but with PRP 🟪 textures).
This stuff is so delicious to me, nice work Shounic san.
Nice catch on the purple color :)
This is actually what I stumbled upon years ago on VHS servers. Where I type in joinclass Spy without choosing teams, I spawn in as a blu Spy that could kill RED and damage Hale. Was nuts.
Versus haxton sale
versus hale saxton
All the halloween creatures having different bizarre rules is so on point for spaghetti code
It's kinda funny that you can see why most of these things work like this too, there's just a bunch of different ways to code things to work with the enemy/allied team, especially assuming there's only red and blu
i'm imagining a 3-team gamemode (no idea what map it'd work in) where you can play as unassigned and get to spawn in halloween NPCs to compensate for their jank
Gravel pit may work
Thanks for the video Shounic! More tf2 code videos are much appreciated!
I'm assuming it wouldn't work but since the halloween bosses share team unassigned I was wondering if medic could heal them in any capacity. Otherwise, really cool video and impressive amount of testing.
this could work since they are possibly just made the same way training bots are just heavily edited logic
@@otne1im pretty sure they arent and are nextbots (the same system used for the skeletons and the zombies in l4d2)
@@otne1 the halloween bosses and skeletons are npcs if i remember right like youd see in hl2.
@@Underqualified_Gunman No skeletons are nextbots, that's why you can kill them even if you are in team unassigned. I'm also pretty sure every other halloween npcs are also nextbots.
@@billybobjoephilcorncobtiptopge
Small flaw in your logic.
You can hurt the skeletons while unassigned but you can't damage the bosses while unassigned.
For your argument for the bosses being nextbots to make sense would require the bosses to be capable of being damaged by an unassigned player.
“Spec, Team Red and Team Blu. These are the only three teams in TF2.”
Bars? 🔥
This is definitely the most "well duh" and "Wow! This is really interesting!" video I've seen from your channel. Keep up the great work man!
3:41 damn sonic, why you slapping the Halloween bosses like that?
Ah yes sonic the hedgehog
*STAND. ON. THE. POINT!*
5:02 top 10 anime betrayals
about unassigned, there's a random dice roll regarding ragdolls of the unassigned team, that makes tf2 client crash, it's somehow related to materials loading function, with that said you can trigger the crash by using the dead ringer or just dying, maybe it's also related to hats
I love how everything is completely random here. You get a bit of both logics at the same time. And honestly, even as a dev, I have no idea how the hell that can happen. You would easily imagine there's are weird "rules" as each components are treated differently (aka spawn doors)
But the flare hitting or not hitting close/long range vs red/blue hitbox detection is an absolute mystery. Even if you wanted, you would struggle to make up such rules !
Thanks for testing them all. Great stuff right there
probably a case of the arming distance for flare been broken.
whit arming distance a distance anything need to fly before X can happen, Real life it can explode. TF2 mostly pass through friendly.
its probably just a case of when your not on red or blue the code defaults to one team then after having added over a hundred different weapons and you'll run into cases were the default was red for one weapon and vice versa.
As explained at the end, it's most likely that the team check is binary, and assumes that if you aren't red, then you're blu, and vise-versa.
Team unassigned reminds me of modded PS3 days where you could make a bind to set someone to team unassigned which wouldn't allow them to select a class and would force them to leave the server unless they had a team change bind which is good for targeting some modders.
You could also target buildings to make them destroyable by any team.
Actually you can create a unassigned building via commands,they will work exactly as shown
I remember this happening to me in an idle server. I had HTML MOTD off, and the server had a dumb thing where it was supposed to put you in spectator until you turned HTML back on. I don't know what happened then, but it put me on this team instead of spectator, and I did a little messing around with everyone else. Pretty fun bug, would do it again if I knew it still worked.
I feel like there's a lot of potential with this to be used for TTT in TF2.
3:49 Finally after all these years, soldier and merasmus made up
6:01 LMAO I DIDNT EXPECT THAT
But this entire video is so interesting cuz how many things act differently, truly source spaghetti at its finest
I'm really curious as to how the Halloween Boss truce interacts with the unassigned team...
Considering the "unassigned" team is also used for the holloween bosses, I'd assume unassigned players are treated the same way, and are unaffected by the truce
At last, the fourth team;
General Renovation Engineering Yard
Or maybe
Professional Renovation Planning League
Grey (or maybe Gray, eh?) is the obvious choice, but I like PRPL being the only team with a four letter acronym.
It would be awesome if this was fleshed out some more, even if it’s inaccessible. Being a Jester of sorts and helping/harming whichever team you want (and being on Merasmus’ side during Halloween) would be such an interesting phenomenon to have available to us.
I mean yeah, we can technically already do that to a degree, but being able to kill “teammates” and heal “enemies” would add another chaotic layer to it 😂
So does the third degree work across team?
Say if a red medic is healing a disguised blue spy and an unassigned pyro axed them?
...That genius theory needs to be tested and sounds amazing
This has some interesting potential for a Red VS Blu VS Modified Unassigned (for balance and fixes, if at all possible). Like two team competitive VSH or MVM, or two teams fighting against eachother and a Halloween mob army "led" by a single, VSH-esque unassigned player.
The creativity this could open if the jank is tamable and fixable is great.
Great video, it was actually very fun to give you (alongside other chat members) ideas of what things to test, and it's good to see that everything made it through even as cliffnotes.
I could imagine this as some sort of "Purgatory" team for an Arena like mode, much like that halloween map where you become dispenser ghosts upon death.
Maybe you'd be faced with significant de-buffs but if you can get a 3 killstreak you will be put on either Red or Blu.
It would be good like 3 team Red & Blue players
Fight Unassigned player
Red & Blue can damage eachother but there main objective it to stop unassigned player from destroying the world
I had custom map idea name
- Day of the Reckoning
Gamemode
-unknown
Red & Blue spawn is seperate but they will lead path to the exit gray team which im call unassigned team as gray
Will be running and hiding from them but if you dont kill them in the next 1:30m they will summon all the boss which is why i named this map "day of the reckoning"
Might seem like "oh easy mode but if you dont kill them they will summon 'it' and it will be a massacre"
I think a pretty cool concept would be having Team Unassigned defend from Red/Blu trying to capture the points while they try to “unassign” other points.
Honestly I'd LOVE to see a long ass video of the quirks behind the unassigned team. It's so funny seeing the things we've never known about this beautiful shit show of a game
A fun quirk of the 4th team you can 'exploit' in game is to join a casual server during warmup, and simply don't do anything. When the game eventually starts, you'll be able to spectate Blu team members (and the bomb on payload) indefinitely, and you'll appear as a dead blu team member on the scoreboard and in the chat.
5:59 who will telefrag the teleporter?
I'm wondering what part of the code makes the teleporter commit self destruct.
@@I_Hate_RUclips.Why do you hate RUclips?
@@matt.w guess
I love automatic comment censoring!
@@I_Hate_RUclips. im betting it probably happens whenever you try to telefrag an unassigned entity, to stop marasmus from being telefragged maybe?
I'm not sure if its possible due to Source's spaghetti code, but if someone manages to hijack the way unassigned team works people could make some pretty cool shit out of this.
Team Unassigned is technically also used in HL2 Deathmatch, but only if Teamplay is disabled. You can see it if you input the console command "jointeam #" with a value from 2 to 3, with it stating you joined team "Unassigned" instead of either the Combine or Rebels.
The mod Open Fortress features Free-for-All, and you can choose a color for your Mercenary's outfit.
Fistful of Frags also uses team unassigned for the free-for-all deathmatch mode
Can't wait for a Vscript map to bring the unassigned team as an actual team
Map Name: Neutrality
Or call it Grayscale since neutral players show up grey in the killfeed and text chat.
I actually managed to get this working in a Vscript... script.
Well i found a fact. Did you know an Unassigned, can't hurt blue from small distance? well it's because the projectile of the flare-gun and e.t.c. When the blue player tries to shoot projectile through his teammate, the game decides to ignore the collisions between the player and projectile from the smallest range. [If not then explode, red or from far away]. But unassigned ignores blue for some reason, but not red.
It's because: blue and the unassigned have the same value team [ prob idk ]
4:26 This is gonna create some "escape plan" alternative memes.
I remember back in CS 1.6, a server I played on had a mod that would allow (unintentionally, I believe) spectators to spawn in as a player. They couldn't purchase anything and were hostile to both teams and vice versa. That allowed for a lot of fun.
This would make a good team for admins and observers.
thats what spec is for lmao
Think of it this way, they can join the fun while not actually being part Red or Blu.
I love how whenever you dissect TF2’s code, Blu team always seems to have a tiny bit more of an advantage, like how in the cart video when the carts where fast enough, Red’s got stuck but Blu’s never did and just sped ahead. Then in the video Blu is immune to some damage while Red is not
3:40 Asian parents when you get a 98 on your exam
the unassigned team reminds me of this old glitch i used to play around with, to make players think that sentries were haunted
i'd enter a match(arena) and using a team assignment bug(you had to re-enter the match BEFORE the start of a round once you loaded in), i would have the role of spectator but was able to directly spectate engineers as an unassigned player
the sentries would immediately shoot wherever this "ghost" was, and you could spectate engineers to have sentries fire at their creators
it's still around, i just can't remember too clearly what you had to do to achieve this..
Not quite the same, but Team Fortress Classic had a yellow and green team that were used on a couple of special four team maps. You could use the console as a spy to disguise as yellow/green on the standard red/blue maps... that was always fun.
Loved this video. Did not expect there to be so many diffefent interesting interactions but thanks for researching it all
Imagine they used this to have some Event stuff where a random player would become some Mega Boss and get a boatload of buffs.
Or some special map where unassigned had to try and abuse their weird spaghetti mechanics to force a stalemate.
isn't that the saxton hale maps?
@@s0nnyburnett Where does the spaghetti come in?
The first one is basically VSH.
@@s0nnyburnett
Small problem.
VS Hale has 2 teams. The red team and Saxton Hale.
What is being suggested here has 3 teams.
Red, blu, and Saxton Hale.
Another thing, VS Hale sees the Red team trying to Kill the Hale and Hale trying to kill the Red team.
This has the Red and Blu teams fighting over an objective while the Hale tries to keep both teams from completing the objective.
Really, the only similarity between the suggestion put forth here and th VSH community gamemode is the fact that it's asymmetrical.
@@ovaiggy
Small problem.
VS Hale has 2 teams. The red team and Saxton Hale.
What is being suggested here has 3 teams.
Red, blu, and Saxton Hale.
Another thing, VS Hale sees the Red team trying to Kill the Hale and Hale trying to kill the Red team.
The original comment didn't actually say anything about the objective in the first part of the comment so I can't actually make a proper comparison there.
But honestly, the only similarity between VSH and the first part of the comment is the fact that one player is put on a separate team from everyone else and is given a bunch of buffs to compensate.
6:01
"the teleporter will have an heart attack"
best line i've ever heard
Unassigned (Grey) should be a free for all / troll team. When you choose that "team", everyone can attack you, and you can attack everyone. The downsides are you can't cap intelligence, cant go into the safe rooms, cant have medics on red / blu heal you, cant use red / blu teleporters, can't push carts, no ability to see players outlines including your own teammates, cant get ammo and health fromred / blue dispensers, and I could go on!
Team Unassigned (Grey) should be played like everyone against me whether for fun, as a personal challenge, or to disrupt and troll the match.
Team Unassigned is used in the Open Fortress mod for FFA mode, and was also in HL2 Deathmatch if Teamplay is off.
This feels like a potential Miss Pauling class option. One of 'em per game, a-la Saxton Hale, but instead of being like a boss everyone else has to fight, Pauling just runs around doing crowd control, for lack of a better word. Bonking people back to spawn, if they get too far, delivering intelligence back to where it should be, and generally being like an administrator of the game (aha get it because Pauling works directly under the actual Administrator) that makes sure people don't get too carried away, and distracted from the main objective, which she herself can't complete. I guess she'd be kind of like a babysitter for a match, unless the person playing her wants to goof around as well.
Lot of comedic potential in Pauling standing outside of the spawn door, like "Come on, guys. Let me in.", with the poor BLU team huddled in a corner, knowing that if they let her in, they won't be able to take a single step off the spawn grounds.
You should host another server again with this activated. It would be interesting to see what else could be found with this.
"Spec, team RED, team BLU
These are the only three teams in TF2"
Excellent rhymes
This could be a fun concept for a necromancer/wizard gamemode where it's a normal blu vs. red match but every once in a while the top score player gets auto-balanced to unassigned and gets random halloween spells over time while being able to spawn skeletons with a cooldown.
Damn this must've took so long to document, big props to shounic for this, this was really entertaining.
This reminds me of the 4-team gamemode in TF2 Classic. I wish that someone could make a vscript map/gamemode that allows for more than 2 teams. It would result in some interesting shenanigans!
The code being "> Is Player Red? If No Assume Blu" and ">Is Player Blu? If No Assume Red" fits right into TF2 lore
*0:54** IT'S THAT O.W.B ? ! OUR WORLD NOW ?!*
IS IT?!
I noticed that Fistful of Frags, another Source game, uses team unassigned for the free-for-all gamemode, people just spawn in with a randomly picked skin out of the 4 normal teams
Who would've thought team UNS owned so much of the map before any of the teams showed up
This is one of the most amazing things I've seen in this game, incredible job as always shounic!
Honestly a gamemode with this third, neutral team would be really fun.
5:55 that’s gotta be the spaghettiest source thing I’ve seen
Honestly a gamemode like this would be cool, like an event of reality breaking and stuff
*It's broken, breyated, forgotten and abondoned Team. But Community we are all same brothers. Sgt Viktor Reznov.*
4:13 yes, my favorite samurai jack villain; aputator
This comment is like 1 year old but it still nade me laugh
Spec, Team red, Team blue.. These are the only teams in tf two (tf2)
that rhymes
7:25 you wrote r/b sentries wont attack unassigned despite showing otherwise earlier in the video
oops
oops
Oops
tl;dr 4th team is "unassigned", used for players before they pick a team (when spectator is disabled), neutral control points, the objective on doomsday, halloween enemies (and krampus) and certain other map elements.
on the whole works as its own team gameplay-wise pretty well, with the only bugs being with close-range projectiles, buildings, and misc stuff like the shortstop shove or YER disguises.
visually you look red, but your hud and projectiles are blue, basically cus the code checks if youre red, and if not you look blue, and vice versa. in chat & the killfeed youre grey, and in the tab menu youre a spectator.
Team Unassigned would technically be used during deathmatch sessions, which HL2 Deathmatch does if teamplay is off. TF2 does not feature FFA however, so team Unassigned is very much a leftover that was given a purpose.
So Team Grey is canon
On tf2 dodgeball you could abuse the unassigned team to spawn into red or blue team even when a match was already running and some players already died. For example you could join when it was left to a 1v1. If I remember correctly, you join a server, but don't choose any team and also don't join spec, then wait for a map change, then join spectator, and then join red or blue and you would spawn in instantly. Useful for helping the winning team win even more, or for getting lots of kills if you join the losing team.
Always love the thoroughness of your videos, but sometimes it can be hard to hear if you said "can" or "can't" like at 1:33 -- 2:00 -- 4:02 -- 5:48
Indeed. "can" or "cannot" would be better for videos like this
6:01 - I guess this is made so you *can't* telefrag Headless Hatman - he is assigned to the "Unassigned" team.
can unassigned medic heal npcs?
4:01
Watch the video mate
@@Luka-bt2ve he means the Halloween NPCs
Memories of this glitch back in UGC servers that set your team to spectator without killing you (technically putting you in unassigned) , oh boy i remember the chaos that happened during those times, another side effect it had at the time was that if you did it with a revved up minigun, it would stay revved up but you'd run in the normal heavy walking speed, and oh boy did it cause unassigned heavies (especially with brass beast) to wreck havoc upon everyone on the server.
A clear example of discrimination against the unassigned community smh
it'd make sense doing this where its like a "fuck it everyone dies" and you just you just ifght anyone and you just spawn in a middle spawn on the map
Would looking at these interactions in a build that predates stuff like Halloween and other npc uses of the unassigned team be likely to have any interesting effects?
6:03
Tele-fragging unassigned players results in the *teleporter* dying.
That made me laugh
5:29 RACISM
Makes sense twam unassigned works mostly on red team cuz Red team is canonically team fighting the Grey Mann
RACISM LORE 1:58
My best guess would be that either "unassigned" was a copy-paste from one of the other teams, or else it was the first team made and then the others were copy-pasted from it and edited. Some of the additional weirdness probably comes from it being edited at some point for the halloween and/ or robot mode (I can't fucking remember what it's called, I've never played it), and because the copy-paste probably happened at some point in the middle of development when shit was half-done.
I think it happened to me randomly one day while playing casual mode: in setup time we were goofing out between teams, waiting for other players.Then the time counter ended right when i was forcing myself through a bunch of blue and red players and i was auto-balanced right after.
I kept playing like usal but there was something really wrong with the game, like going through blue team while being in red team, my preview class was blue instead of red... It was really strange. I think I triggered some glitch.
imagine if there was a server network dedicated to you being able to join team unassigned like how this guy did it would be like having a new tf2 update