Forum Rules 07/06/2016
Prohibited topics include, but are not limited to: Piracy, drugs (including cannabis), pornography, religion, racism, sexism, homo/trans -phobic content, videos and images showing violent death or serious injury, ‘spam threads’, hacking & griefing (endorsement thereof), religion, politics, etc. Prohibition may be suspended for some threads if they are found to be suitable by the Moderation (such as scientific debate).
If there is doubt, the Moderation Team can decide whether a topic is considered illegal. §5 Attitude towards Squad and the Development Team
As per §1 and §2, keep in mind to be respectful and reasonable, not only towards all users of the forum, but also towards the Squad Team and towards any ideas and content and the game itself. Criticism is welcome, but if it is not constructive and/or if it is offensive, the Moderation may need to step in. Please refrain from posting if you are upset, angry or drunk, or you may be punished for things you wouldn’t have otherwise written, which is not in anyone's interest. §6 Language & Legibility
Please post only in English. Non-English content (including non-legible content) may be removed. If you see someone posting in another language because s/he apparently does not speak English, please report their post - if you can, you may reply in their language to explain their question, but please do translate their and your message so it can be reviewed by the Moderation. ‘Hiding’ insults in non-English posts will be punished harshly. Posts written largely in ‘leetspeak’ or full of spelling / grammatical errors may be treated like non-English content. This rule does not extend to PMs. §7 Forum structure & Search
Please ensure when posting a new thread, that the thread is located inside the correct forum section. Check all forum section titles to judge where your thread should belong. Threads created in the wrong forum section will be moved or deleted.
Before posting a new thread, please make use of the forum search to find older threads about the same topic. In doubt, it is recommended to rather post in an existing thread, unless that thread is years out of date. However, do not bump old threads without adding a new question / answer / insight that wasn’t in that thread before - use common sense. §8 Thread Titles
Please name your thread appropriately; the subject title should sum up / explain the content in the thread. If you fail to name your thread properly (such as ‘Hey!’ or ‘Check this out!’ or ‘Help!’), we will either rename or lock the topic. Repeated offense may lead to infractions. The practice of using CAPITALS only in your thread title is not allowed and will be edited or the thread will simply be deleted. Strange or abnormal Unicode characters should be excluded from thread titles for the sake of being distracting and unnecessary.
§9 Thread Capitalization
Please ensure that your post is not in all CAPITALS, as this is not allowed. Any threads posted in all caps will subsequently be removed from the forum. Repeated offenses may lead to infractions against your account. This practice is not approved or accepted here.
§10 Images in posts
When posting images, mind the following restrictions:
.gifs will be allowed and may be removed by Staff if deemed necessary.
Maximum size for images is 1280x1024.
Do not include more than ~1 large image per paragraph of text, unless in image collection / announcement threads. Link to further images.
Consider posting thumbnails. You may post a few more images per post if they are reasonably small, the details are for the Moderation to judge. §11 The use of BBCode
It is allowed to use the BBCode in your posts. Over usage is not allowed. You may use the Bold in a reasonable manner but not for the whole text body. You may use the size feature but in a limited reasonable manner. You may not use any of the additional fonts at all. Color may be used to high light a point but again, not for the whole text body. Moderators will be watching for misuse and will edit when required without giving notice. Continued disregard for this rule will result in Moderator action in the form of warnings. §12 Complaints of Server/Admin Abuse Reports of server/admin abuse will not be posted publicly. All reports concerning this type of behavior should be place in the appropriate sub-forum. http://forums.joinsquad.com/forum/241-report-server-admin-abuse/ All posts made outside of this area will be be removed. Section II: Reporting & Moderation §1 Reporting Posts
There is a Post Report system in place. If you notice a post that violates forum rules, simply use the exclamation mark icon below the users avatar image to send a report to the Moderation. We will then review this post. Your report will not be made public and cannot be linked to your person by anyone outside of the Squad Team. You will not be punished for using the Report system even if the report was false, unless you repeatedly abuse the system to spam it.
Do not ‘report’ posts by replying directly in public to them. In case of spambots, this prompts them to respond in turn, spamming the forum further. This also fuels flame wars and arguments. §2 Reporting Moderators
Moderators are subject to the same forum rules (and some additional rules / exceptions). If you think that a Moderator has treated you unfairly or is otherwise breaking forum rules, please PM the Lead Moderator or any Administrator. Do not accuse Moderators in public, the Squad Team will treat every complaint seriously and it is in our interest to discipline or remove Moderators who are known to break forum rules. §3 Respect Squad Team members and Moderators
Do not ignore or argue against Admin, Moderator or Dev instructions on the forum. If you have a complaint, as per §2, please inform the Team in private. You are expected to follow orders given by the Moderation, Administration and Development Team, and it is necessary for smooth running of the forum to respect their decisions. Being stubborn or ignoring warnings will lead to harsher punishments - however, we do not tolerate Moderator / Admin abuse of power / privileges, so do not hesitate to inform other Team members if you feel treated unfairly. §4 Bans and multiple accounts
If your account is temporarily or permanently banned, do NOT create another account. Bypassing a ban will result in further action, and a permanent ban of all of your accounts.
You are not allowed to have more than one account for any reason. If you share an internet connection with another user who has their own account, it might happen that this account is incorrectly identified as a secondary account - please get in touch with the Moderation or Administration to resolve such issues.
Search the Community
Showing results for tags 'reinforcements'.
Found 2 results
Due to the length of this discussion, I have summarized most of the critical talking points here in the OP, so if you are interested in contributing you dont need to read the whole thread, simply this post. I will keep it updated if it progresses further. Problem: At present, Radio Spawning mechanisms, and Rally Point mechanisms are pretty magical. They allow infinite access to the farthest reaches of the battlefield regardless of their logistical access to reinforcement. Solution: If the team's tickets, which represent the attacking forces ability to reinforce its self, were treated as in-game entities tied to a location, then they can be subject to a logistical paradigm of reinforcements that is not only analogous with real life, but would become a challenging and exciting element of gameplay. Benefits: increased value of life due to local limited access.increased use of medics due to time-to-return penalty of "getting more people to the field"increased value of strategic fortifications providing access to things as well as re-spawns.increased value of logistics as assets that can be forfeited as well as needed for operationincreased use of legitimate tactics due to real constraints.reduced spawn-camping due to inability to infinitely reinforce without dominant occupation for logistics.reduced lone-wolfing due to increased reliance on team-wide infrastructure.solves perpetual FOB wars, and adds the ability to Seige a team's defenses.Legitimate necessity for FOBs and emplacement structures in AAS gamemodes.Disadvantages: Increased gameplay complexity (if all complexity was bad, we'd be playing DOOM)Easier to lose the round more rapidly by severe misfortune, as losing a reinforcement laden truck would hurt the team's tickets in a large portion. (Solved by Automatic Reinforcements below)Easier to troll the team as a logistics member yielding reinforcements intentionally. (Solved by Automatic Reinforcements below)These are able to be mitigated however. The complexity can be overcome via training videos, and better, learning from the existing community. The loss of logistics can be looked at as a disadvantage only because of its potential to be trolled. Limiting the number of reinforcements per vehicle to a reasonable amount limits the amount of damage done, and this person is then easily banned. Variations: Radios are used to call Automatic Reinforcements: Under the pretense that Fully-manual Reinforcement Logistics would be an excessive burden, a suggestion for automating it while still making it a player triggered element, contingent upon the stability of disruptable supply lines, and local fortification stability. Complex Game Mechanics Do Not Mean Complex Interactions: Like comparing chess to checkers, a more complex rule-set, does not necessarily mean an overly complex interaction, but the difference in capable strategies is very well acknowledged, providing a game that anyone can play, but that leaves headroom for excellence. Prerequisites: Some confusion has arisen due to some elements not made sufficiently clear. There are some prerequisite concepts that would need to be in-place for this thing to work; 1 ticket = 1 life = 1 respawn. Until someone re-spawns, there is no ticket loss. This represents the activation of a limited amount of reinforcements, and it should be 1:1. People can still get points for "kill shots" even if the person is revived, but the ticket loss should be attributed to permanent loss of persons.The economy of things is completely separate Vehicles are not persons, so losing an empty truck doesnt cost you team tickets. Its still however, a significant loss, if you needed the use of that vehicle. The cost of things is something that needs its own economy, whether its a trickle in-element that appears at main or something to be spent by the commander, thats not what this thread discusses, but it does rely on them being isolated.
Make the commander the most diserable role to play! I played a lot of bf2! And it was so boring to play commander. Squads didnt follow orders and you didnt really have a big impact on the game except from eternally spotting enemies. I'm confident SL's Will follow orders (in Squad) but its not really a big adrenaline rush to have 3 otter Guys on your comms channel, and seeing Dots on a map. Solution? Make the commander awesome! Reinforcements: I suggest the commander should impact spawn timers on vehicles, it can be done in 1 of 2 ways as i see it. 1st: prioritizing respawn timer rates e.g. your 1st priority gains a 2x respawntimer boost, 2nd 1.5x and 3rd 1.2 (what ever). - If no commander boost rates could just level out on all vehicles 2nd. simply buying vehicles like building fobs. though with a maximum so you can't have 2 or 3 mainbattletanks or whatever. This way the other team wouldn't know if they are going up against an armored force or a fast-moving recontype force. - If no commander is chosen a standard picking for a balanced force is chosen. (my favorite) being in charge of reinforcements gives the commander a greater strategical impact. I think we all agree mainbattle tanks shouldnt respawn right after being destroyed. Vehicles should be cared for and valued highly. The squad should cheer when destroying enemy vehicles... knowing they wont see the fckr again for a long time. Offmap assets: Commander is in charge of all offmap assets: Artillery, UAV's (small videofeed of whats going on atm), drops and.. piloting planes! Helicopters belong on the map. Planes do not! We Will miss out on the brute force of a plane haulning over the map in 12 seconds If their speed is to fit into gameplay. I hate missing out (see the link, you can't fit this into a game where an airplane takes off and land on a 8x8 km map). Let the commander call a plane into the A.O and have him pilot or Gun it when dropping a JDAM on an enemy compound or shooting down a helicopter bugging your squads. "Air support incoming 3 minutes" Would be a nice information to relay to your squad mates. And this would give the commander some hands on experience. Even just 30 seconds, two or three times a game, not looking at your map would make a big difference for playability. making airsupport this way, would also make it a lot easier for developers I believe (not an expert on the matter). Comms: The commander should ofc talk to the SL's and not the squadmembers, to hold a chain of command. on his map he should be able to tap into one squadleader and only talk to him. He should also have direct comms to all vehicles, making vehicles a team asset, not a squad asset. Again by tapping into their comms on his map. (sidenote on vehicle kits) Maybe pilots and drivers, except humvees and the like, should not be squadkits. but instead a separate "squad" operating only under the commander. So a squad as one unit can be deployed by a team-helicopter/apc without having a member driving back to base to not lose the vehicle. This would also emphasize the importance of vehicles, and caring for them. Typical BF to drive to the front and leave your vehicle.. I dont want this. Conclusion: Offmap assets like planes and artillery should be very rare, and therefore it is important to give the commander a busy gameplay revolving around strategy and comms. since he has the role of tactical air command, artillery battalion, executive officer and if you listen to me: pilot/gunner and company commander (reinforcement wise). he SHOULD have enormous impact on gameplay, the biggest impact of the team! He should feel the resposibility of the SL tenfold. people don't go SL because it is a big responsibility - and for the same reason people wouldn't just go commander to mess around. - and YES mutiny/voting should be an option. sorry about the rant, I had so much on my mind :D what do you think?