-
Posts
113 -
Joined
-
Last visited
Content Type
Partners
Guides
Events
Forums
Profiles
Everything posted by aelius
-
3) "I didn't see it happen." This sentence causes the second most emotional damage to me out of any sentence in the english language besides "I wish I had a daughter". I understand the logic of this, I really do, but there has to be some point where enough of the Ts have been complaining about a guard for them to be switched to T. Even if admins aren't supposed to take a Ts word when they use !fk, if a player named Harvard Business has !fk used on them by 12 out of 16 Ts in one map, they should get temporarily CT banned. I believe admins began to favor CTs in decisions way too much after gangs were introduced and the playercount is low, but it's not like that anymore. And even when the ratio is tilted toward Ts, I'd rather have a bunch of CTs that are bad at controlling prisoners then a bunch of CTs giving orders that allow them to turn the gamemode into some screwed up version of DM. If players are being routinely reported for freekill, and an admin doesn't see any of them, after a certain amount of reports the CT should be manually handed a temporary CT ban by an admin. 4) "I already gave you a warning shot, I can kill you." Why does everyone think this? This isn't a thing! You can kill after warning shot for the same order, but it resets for a new order. If you think I'm wrong, then you're suffering from the Mandela effect. In the JB Rules page; "Warning shots (1 Shot, 1-99 DMG) are required unless the T is rebelling or blatantly disobeying orders. After a warning shot is given if the T keeps disobeying the same order they can be killed." The page's emphasis, not mine. This isn't so much of a matter of changing a rule as it is simple enforcement. I can't count the amount of times I've typed !fk, an admin questions the CT, the CT says "gave a warning shot" and the admin gives the CT a pass even if the warning shot was for an order 2 minutes prior. This excuse can be proven wrong just by looking at logs, because the reason for killing the CT just gave can be proved as completely wrong if the logs were used to show the warning shot was for a previous order and not the same. This is just another way the Epic Bosses abuse the rules to no repercussions.
-
MS2: Repeating Orders
aelius posted a topic in Jailbreak -- jb.steam-gamers.net
2) "I'm not going to repeat the order. Do the order." This happens to all Ts. Completely disregarding situations where people simply have bad mics or quiet mics, there are times where Epic Bosses maliciously change the way they deliver an order to make it unclear. Epic Bosses say the order as fast as they can so that if you're not listening intently to their $5 walmart microphone you can't hear them. When you ask them to repeat, they either do the same thing, or say "I don't have to repeat my order, just follow it." I'm not being figurative when I say every player on JB has an experience where an Epic Boss gives an order that sounds like Tom Hardy had cleft lip and was trying to speak in moon runes. No one can understand them, and then they sit there, warning shotting and killing the Ts until the LR sound plays and they laugh to themselves over mic about what a big brain play they pulled. It's either this, or they give a purposefully misleading order (that they can rephrase better to an admin) to get free kills. An example is the order "when cell doors open, bum rush to the bottom of under main cell stairs, crouch, and freeze." You might not have caught it at first, but there's a good trick in there that an Epic Boss can use to kill half of the Ts. If some Ts go under main cell stairs, and some Ts go to the bottom of main cell stairs, just warning shot then kill the larger group of Ts. As rules stand right now, CTs don't need to repeat an order when a T requests it (this rule is not on the rules page, but according to @fantastic "it's implied"). Any time a T is killed for standing still in their cell and typing in chat "repeat the order" or "what's the order" is just a bullshit kill that should 100% be treated as a freekill. I know the rules don't reflect this, which is why a rule should be added where orders have to be repeated at least once upon request. Now, you might ask, "don't we have a rule to prevent this behavior?" Well yes! There's "CTs must give reasonable orders", where reasonable orders are orders that are "straightforward, clear, to the point, easy to understand, not meant to confuse or trick, and gives the prisoners enough time to follow." Doesn't this address this issue? It does! Well I hope the admins are on, and if they are I hope they see it happen, or else you're out of luck. That brings us to situation 3! TL;DR: Giving super fast or confusing orders so they can get more kills, not repeating order when T players ask. Rule: Orders have to be repeated at least once upon request. -
MS1: Changing Rules for Crossfire
aelius posted a topic in Jailbreak -- jb.steam-gamers.net
So @Trazz has told me to break up my post into 6 posts to not derail discussion, so I'm going point by point. "It was crossfire, my bad. Not slaying though." Crossfire is a rule implemented with good intentions, but has been delivering bad results. Crossfire for Jailbreak is just association for TTT. Now, instead of a CT making an effort to only kill the one rebelling T in a stack, it's all too common for a CT to target the T as much as possible, and if they kill anyone else in the process, "well who gives a fuck, I'll just claim crossfire and not slay". Yeah, the admin might have seen a CT just kill 6 people in the killfeed, but they didn't see it happen, so they can't act. Crossfire has also allowed for CTs/Epic Bosses to take more risky engagements against Ts with weapons. Before crossfire was abused, if someone had a pistol with other Ts in medic, you bring the Ts out, line them up, find the pistol, and take it. Now, Epic Bosses can try to fire into medic to kill the person with the pistol, commonly crossfiring other Ts that are being used as bait. I propose that a CT can only claim crossfire for either 1 or 2 collateral kills. Anything over that and crossfire should not cover them. If this rule change was implemented, not only could admins slay CTs who crossfire over that amount, but players can go back to policing other players to slay for crossfire like how it was before crossfire started to be abused. I play CT, and when I crossfire multiple people trying to kill a rebeller who is using them as bait, I slay. I don't have to, but I just ruined the round for the people I killed. I'd much rather be forced to slay for crossfire, then let the Epic Bosses use crossfire as an excuse to get a 4K. TL;DR: Using crossfire as an excuse to spray in stacks. Rule: Crossfire only applies for 1/2 collateral kills. After that, slay. -
Alright I know this is a long read but stay with me. TL;DR at the bottom, but I have six rule changes/additions I would like to suggest to prevent shitty CTs from abusing the current rules to farm kills. Here goes. I used to love Jailbreak. It was my favorite gamemode to play in GMod or in CS:GO. On SG, I loved JB the best in early 2018; it started to become less fun heading into 2019, and around August of 2019, my feelings about the game on SG changed dramatically. It started as a fun game I could sink time into just fucking around and having a good time with other players, but now it's become a form of emotional roulette. I can have a great time, an O.K. time, or a rage-inducing, hernia-forming shitfest that makes me want to break my keyboard. And I'm willing to bet that if you play T, you identify with that 100%. There's several reasons for this, but the main reason is Jailbreak's rules are being used by a very specific type/set of CT player(s) to inflict as much damage and kill as many Ts as possible, to the detriment of all T players. This has caused a change in not only how the game is played, but the goal of this game. In this post, I will address how I believe the "goals" of JB have changed, the type of CT players that are abusing the rules and ruining the game for Ts, five common situations/rules that ruin rounds for Ts, and ways to mitigate these bad players' behavior. I know everyone won't agree with all the changes I suggest, so I'm hoping to engage a discussion on all the separate rule suggestions I bring up. The "goal" of Jailbreak At the top of the JB rules thread, the post says "The guards order the prisoners around, but can shoot them if they're following orders and not attacking. The goal is for Ts to rebel & take control of the prison by killing every CT." This shows the intended goal for Ts is to rebel and kill all CTs. But what does it say about the goal for CTs? I would say the goal for CTs would be to order prisoners around and kill the rebelling players, just like it used to be, and how many players would agree the game should be played. But some very specific people that play CT, who are disliked by a large amount of Ts for their playstyle, would say the goal for CTs is to "kill all prisoners." There's an important distinction there, one that I think the community, and many CTs, have forgot. When I say "these CTs", I mean the players whose sole goal is to rack up as many kills as possible, and confuse the Ts into doing just enough that they can say they're rebelling. These players give confusing orders, they shoot into stacks under the guise of "crossfire", they change the order they said to get damage in ("I said face west, not back!"), and they blatantly fk because they know an admin can't do anything about it if they didn't see it. For simplicity's sake, let's call these players the Epic Bosses. These Epic Bosses know that if an admin didn't see it, they can get away with anything. In fact, some JB players can vouch that these Epic Bosses have even bragged about their intentions when playing CT on the server when admins aren't on. These are the CT players that make the game terrible for Ts. They turn T gameplay from a game about following orders and eventually rebelling, to a game where you have to decipher their rules like decoding the Rosetta Stone and hope they don't freeshoot you even when you do follow their order. Now, onto the common situations/rules that I believe make this game AIDs for Ts. 1) "It was crossfire, my bad. Not slaying though." Crossfire is a rule implemented with good intentions, but has been delivering bad results. Crossfire for Jailbreak is just association for TTT. Now, instead of a CT making an effort to only kill the one rebelling T in a stack, it's all too common for a CT to target the T as much as possible, and if they kill anyone else in the process, "well who gives a fuck, I'll just claim crossfire and not slay". Yeah, the admin might have seen a CT just kill 6 people in the killfeed, but they didn't see it happen, so they can't act. Crossfire has also allowed for CTs/Epic Bosses to take more risky engagements against Ts with weapons. Before crossfire was abused, if someone had a pistol with other Ts in medic, you bring the Ts out, line them up, find the pistol, and take it. Now, Epic Bosses can try to fire into medic to kill the person with the pistol, commonly crossfiring other Ts that are being used as bait. I propose that a CT can only claim crossfire for either 1 or 2 collateral kills. Anything over that and crossfire should not cover them. If this rule change was implemented, not only could admins slay CTs who crossfire over that amount, but players can go back to policing other players to slay for crossfire like how it was before crossfire started to be abused. I play CT, and when I crossfire multiple people trying to kill a rebeller who is using them as bait, I slay. I don't have to, but I just ruined the round for the people I killed. I'd much rather be forced to slay for crossfire, then let the Epic Bosses use crossfire as an excuse to get a 4K. 2) "I'm not going to repeat the order. Do the order." This happens to all Ts. Completely disregarding situations where people simply have bad mics or quiet mics, there are times where Epic Bosses maliciously change the way they deliver an order to make it unclear. Epic Bosses say the order as fast as they can so that if you're not listening intently to their $5 walmart microphone you can't hear them. When you ask them to repeat, they either do the same thing, or say "I don't have to repeat my order, just follow it." I'm not being figurative when I say every player on JB has an experience where an Epic Boss gives an order that sounds like Tom Hardy had cleft lip and was trying to speak in moon runes. No one can understand them, and then they sit there, warning shotting and killing the Ts until the LR sound plays and they laugh to themselves over mic about what a big brain play they pulled. It's either this, or they give a purposefully misleading order (that they can rephrase better to an admin) to get free kills. An example is the order "when cell doors open, bum rush to the bottom of under main cell stairs, crouch, and freeze." You might not have caught it at first, but there's a good trick in there that an Epic Boss can use to kill half of the Ts. If some Ts go under main cell stairs, and some Ts go to the bottom of main cell stairs, just warning shot then kill the larger group of Ts. As rules stand right now, CTs don't need to repeat an order when a T requests it (this rule is not on the rules page, but according to @fantastic "it's implied"). Any time a T is killed for standing still in their cell and typing in chat "repeat the order" or "what's the order" is just a bullshit kill that should 100% be treated as a freekill. I know the rules don't reflect this, which is why a rule should be added where orders have to be repeated at least once upon request. Now, you might ask, "don't we have a rule to prevent this behavior?" Well yes! There's "CTs must give reasonable orders", where reasonable orders are orders that are "straightforward, clear, to the point, easy to understand, not meant to confuse or trick, and gives the prisoners enough time to follow." Doesn't this address this issue? It does! Well I hope the admins are on, and if they are I hope they see it happen, or else you're out of luck. That brings us to situation 3! 3) "I didn't see it happen." This sentence causes the second most emotional damage to me out of any sentence in the english language besides "I wish I had a daughter". I understand the logic of this, I really do, but there has to be some point where enough of the Ts have been complaining about a guard for them to be switched to T. Even if admins aren't supposed to take a Ts word when they use !fk, if a player named Harvard Business has !fk used on them by 12 out of 16 Ts in one map, they should get temporarily CT banned. I believe admins began to favor CTs in decisions way too much after gangs were introduced and the playercount is low, but it's not like that anymore. And even when the ratio is tilted toward Ts, I'd rather have a bunch of CTs that are bad at controlling prisoners then a bunch of CTs giving orders that allow them to turn the gamemode into some screwed up version of DM. If players are being routinely reported for freekill, and an admin doesn't see any of them, after a certain amount of reports the CT should be manually handed a temporary CT ban by an admin. 4) "I already gave you a warning shot, I can kill you." Why does everyone think this? This isn't a thing! You can kill after warning shot for the same order, but it resets for a new order. If you think I'm wrong, then you're suffering from the Mandela effect. In the JB Rules page; "Warning shots (1 Shot, 1-99 DMG) are required unless the T is rebelling or blatantly disobeying orders. After a warning shot is given if the T keeps disobeying the same order they can be killed." The page's emphasis, not mine. This isn't so much of a matter of changing a rule as it is simple enforcement. I can't count the amount of times I've typed !fk, an admin questions the CT, the CT says "gave a warning shot" and the admin gives the CT a pass even if the warning shot was for an order 2 minutes prior. This excuse can be proven wrong just by looking at logs, because the reason for killing the CT just gave can be proved as completely wrong if the logs were used to show the warning shot was for a previous order and not the same. This is just another way the Epic Bosses abuse the rules to no repercussions. 5) "I'm not cheating in LR, since I'm not in your LR." This brings me to my penultimate point which I can't believe doesn't have a rule attached to it. On the JB Rules page, there is the rule "A CT is not allowed to cheat or delay during an LR." This rule doesn't address other CTs outside of the LR purposely interfering in the LR, which happens enough to be a problem, especially with these Epic Bosses. They can interfere by standing in front of/next to/behind the player, blocking their movement, or standing in the player's line of sight (like in Gun Toss or Shot 4 Shot), picking up the player's deagle/getting shot by the player, and then killing the T for losing the LR. After looking around in forums and asking in Shoutbox, @Love_ swears there is a rule for this somewhere, but I cannot find it for the life of me. If it does exist, then it needs to be enforced and spread to the playerbase, because many players (including me until this post) aren't aware of this rule. If it doesn't exist, then there should be a rule to prevent CTs from purposely blocking a T from moving around during an LR, or preventing them from having a clear line of sight if it's an LR like Shot 4 Shot. 6) "LR in the next 15 seconds. I'm not going to accept your LR, but LR in 15 seconds." My final situation makes my blood boil every time it happens. A CT tells the remaining prisoners to freeze and LR in a very short amount of time, then either the CT or other CTs deny the LRs, and they kill the prisoners after the assigned time passes. This is just a KOS order. That's all it is. A CT is telling a T to complete an action by a certain time when they need the CTs approval to complete the action, the CT prevents the T from doing it, and then kills the T. This is the same as telling prisoners to rush to big cage when cell doors are shut and then killing them for it. I've scoured the Rules page, the changelog, and question posts to see if there is a rule for this, but again there isn't one. This needs to be stopped, because it is never, ever dealt with. Epic Bosses give the excuse of "I set a time to LR by", and the whole freekill is forgot about. The rule I propose is "A CT cannot deny a standard LR if an 'LR by' timed order is given." Most CTs don't do these things. There are CTs who are bad at being CTs, those who are good at it, and those who have some sixth sense about rebelling prisoners and will never lose a round in their life. And then there are the Epic Bosses. I don't want to ruin the game for CTs, or make it harder for them to win. I want rules to be added to prevent the Epic Bosses of the CT side from ruining the rounds of T players. The Epic Bosses are who this post is directed to; those who are bending the rules to essentially troll. Epic Bosses are the same type of people who come on to the server to mass freekill a bunch of CTs and leave, except Epic Bosses don't have the balls to do that. They take the long con, tip-toeing around rules they can manipulate to get extra kills. The Ts don't want them, the other CTs don't want them, and I promise the admins they don't want them either. The Epic Bosses are the reason why the server is toxic, and why many T players spam freekill when they die. Because if 50% of the time you're dying to Epic Bosses with their not-quite-freekills, the other 50% of the time you'll be expecting your death to be freekill. Kind of a TL;DR (please read the actual post or each rule's section if you comment about it. I think the reasoning is as important as the rule in this case.) There's a group of CT clowns I like to call the "Epic Bosses" who are the main source of problems T players experience. Here are 6 common tactics they use to skirt around freekilling, and rule changes for each tactic. 1: Using crossfire as an excuse to spray in stacks. Rule: Crossfire only applies for 1/2 collateral kills. After that, slay. 2: Giving super fast or confusing orders so they can get more kills, not repeating order when T players ask. Rule: Orders have to be repeated at least once upon request. 3: Players freekilling repeatedly where each time admins couldn't see it happen. Rule: If an admin sees a player reported (!fk) for freekill a significant amount of times in a map in situations where they don't have enough evidence to act, the player gets a temporary CT ban. I'm expecting this to be poorly received. 4: Using warning shots for past orders to justify giving no warning shot and killing for a new order. Rule: No new rule, just spread awareness of the rule that exists and enforce that rule. 5: Blocking a player from moving or having LOS in LR. Rule: CTs cannot interfere in a prisoner's LR if they are not in LR with that prisoner. 6: Denying given LRs when an "LR by" order is given, then killing the T for it. Rule: A CT cannot deny a standard LR if an 'LR by' timed order is given. I would love to discuss each point and their validity as they stand on their own. I understand some of these changes sound far fetched, but there are some that should be relatively easy to implement, and would do a lot of good for the server. I know the SG Jailbreak stands out as a server that is easy for players to get to CT on, but these rules wouldn't harm that. They would simply help prevent bad CT players from making the game terrible for Ts.
-
Garry's Mod Melonbomber
topic replied to aelius's John in Past Events
2 day event hype -
You dare forsake the jesus christ of .io's by putting it at F tier? I don't even need to say the name of the masterpiece that is the best, S+ tier .io game to have ever been made, because anyone who thinks of an .io game has that immediately come to mind. You scum.
-
Listen I can’t record on JB because of angsty preteens so this is my only outlet to express how I truly feel about ur CT playstyle
-
[video=youtube_share;x14ek16fpbc] See, I play stuff besides JB! But if I'm being serious, this video is an ode to the SG SCP server (RIP my man). I didn't get my new GPU to record until after the server got shut down, which sucked because I enjoyed playing on it when I could. Since I can't record on that anymore, I tried to get some guys together and play SL somewhere. It didn't go as planned, but this is the result. P.S. sorry for being dead on forums life is busy y'know also P.S. @Auto stop camping secrets on electric before I spook ur ass
-
I gave you your own little section and you do me dirty ned, now I'm sad (the emotion not the mans)
-
I don't know what you guys are saying, but world peace could definitely be achieved, you pessimists. The steps are economic troubles -> mass genocide -> world peace. Step 2 has been designed to combat nV's point
-
1st post on forum account just to tell me that my "worst" video is better than his best jk u rascal
-
[video=youtube_share;Y9MjsmnXTfI] Since no one wants to watch videos about MiniGames, here's yet another TTT video with some new flair! After receiving some constructive and not-at-all constructive advice on my videos, I changed things around a bit to suit the comments I've been given. Additionally, I was told my videos are too quiet to watch sometimes, so I boosted the volume up to compensate (lmk if it's still too quiet or if it's earrape). Thanks to @Ned for making sure my video doesn't qualify as harassment, thanks @Noxstar for being such a sexy beast (in game at least), and thanks @kennyy for being the best quality control team I could hope for. Hope you guys like it
-
Random Question of the Day [8-5-2019]
topic replied to aelius's Frostbitten in Off Topic
All these boys saying Lay's barbecue haven't experienced the superior version of barbecue chips, the Lay's Kettle Cooked barbecue chips. They got that cronch factor -
Initially after reading the bottom part of Caution's post above I was going to react negatively, as I believe that a substantial number of votes contain enough detail to be worthy of contributing to a post count, but after thinking more about it, I think that making admin app posts not contribute to post counts is a worthwhile tradeoff to help mitigate the free posts. The players who usually have worthwhile contributions to admin app conversations are regulars and administrators that already have a large amount of posts. On the other side of the spectrum, those who use votes as freebies to boost their post counts usually are those under 10 posts (trying to get enough to post their own admin app, you can see this with some of the players who applied in the last two weeks) or those under 50 posts trying to get to the regular status. If those who contribute good posts don't need to increase their post count, and those who usually contribute bad ones need them to increase their post count, it really makes sense to just stop counting admin app posts towards a users post count. Would it be possible to get a vote on this, because this seems like a pretty easy to implement and effective solution.
-
If you didn't vote for yourself, then... Oh no wreck what did you do
-
I agree abstains need to be fixed, but not removed entirely (that would be real bad imo). How about some of the points addressed in this page here under "For Members Responding to Admin Applications" become necessary criteria that have to be addressed for a post to be considered a "valid comment", and if a post doesn't have these things, it gets removed (to prevent post farming)? For example, I would suggest these: 1. "You should provide a reason why the person applying should have admin." 2. "Provide specific examples of why the person would be a good admin, such as past experiences and how the person has been helpful as a regular player." (each post requires one example, maybe?) 3. "If you're voting reapply, give feedback on what they should improve on in addition to your reasons." I would recommend adding the following as "rules" to a valid post: 4. "If you're voting abstain, give a reason why you are not making a firm decision (yes/no/reapply) on the application." 5. "'Cool guy'/'Good guy'/'Knows the rules' are not reasons for stating yes. 'I don't play with you often'/'You need to play on JB/TTT more' are not reasons for stating reapply or no." Making these firm rules to a quality/acceptable post would remove most useless "abstain" votes, including useless yes/no votes that only say "You're a nice guy, and you know the rules!" Does this make sense to anyone else?
-
A “solution” I’ve been thinking about is simple voice over chat precedence. My main issues with chat orders are when myself or others are giving voice orders, a chat order is given during a voice order, and some Ts start to follow chat order while others follow voice (and Ts spam “OH READ CHAT READ CHAT” if the chat order is more beneficial to Ts). An example that I can think of involving myself and @TheZZL occurred a couple weeks ago. I was giving orders over mic with ZZL for Ts to be in pool so we could do a head count, and another regular CT (who I believe is the CT who purposely gives chat orders to confuse, as mentioned above by others) gave a chat order for Ts to go to soccer pitch. Half the Ts started running to soccer, while half stayed in pool, and the unnamed CT started warning shot/killing the CTs in pool (while ZZL and I were still giving orders). Scenarios like this one could be made completely irrelevant if there was a rule that all voice orders take precedent and are considered valid, and the chat order is considered invalid when both are given at the same time. Additionally, as @Gentoo mentioned above, freedays shouldn’t be allowed to be given over chat. I fully support what he said about that. Just like above, there is a constant issue with CTs giving valid voice orders, and some dingus gives a chat order for freeday, mucking up the round for 30 seconds while Ts get freekilled for not following the voice order when CTs don’t notice the freeday in chat.
-
[Server] TTT August Karma Contest
topic replied to aelius's Ned in Past Events
Won't be able to play until the 5th but I'm gonna grind until the 18th, gl boys -
I appreciate this idea, but I still have some mixed feelings about it. I feel like regular players are kind of distanced from staff of the month, as those who receive it seem to get the award partially/largely based off of work they do that normal players don't get to see. For example, the justification for the most recent recipient of staff of the month, roux, included (1) his work mobilizing the media team, (2) "providing input in higher up discussions", and (3) handling player complaints. Two of these reasons are things a regular player might never get the chance to see. However, is that really a bad thing? Should admin of the month be more geared to how the recipient interacts with and supports the players in the community, or should it be about how the recipient benefits the community as a whole (something other staff are much more qualified to judge than regular players)? If the answer is the first, then I support the implementation of this idea. If the answer is closer to the second, then I personally believe the system should stay as is.
-
[Answered] Questions for Jailbreak
topic replied to aelius's Noxstar in SG Info & Discussion
Yeah if Night Light tried to pull that if/then logic with you, that is totally wrong and I've seen an admin (Bubblez maybe? I think?) rip a player a new one when they did the same logic. Just because if gun out=kos, and dropping weapon=gun out, that 100% does NOT mean that dropping a weapon means you had the gun out for long enough to be KOS. That's BS. -
Currently on work trip, I've been wanting to edit for so long but my laptop doesn't have any of my files on it ;( I keep wanting to play SCP because I love the game (play mainly on a diff. server) but when I try to hop on the SG server it's never on when I try to get on, i cri
-
Speaks the truth, but don't pay more than $500 for an aftermarket 2060S
-
RIP Uno (temporarily), but this is a fun question: Smack That, by Akon w/ Eminem, listened to it in 2006. I was 6.
-
With the $400 price range, I'd say a RTX 2060 Super would be pretty great. On Nvidia's website, they're $400, but the cards are definitely overpriced on sites like Amazon.
-
Thank you both, nick's solution worked, I'm just a big dummy dumb dumb.
Forum: Past Events
Forum: Off Topic
Forum: YouTube
Forum: YouTube
Forum: YouTube
Forum: Off Topic
Forum: YouTube
Forum: YouTube
Forum: Off Topic
Forum: Completed
Forum: Off Topic
Forum: Completed
Forum: Completed
Forum: Past Events
Forum: Completed
Forum: SG Info & Discussion
Forum: YouTube
Forum: Tech Talk
Forum: Music
Forum: Tech Talk
Forum: SG Info & Discussion