Leaderboard

-1. Several reasons. 1. Roles would get confusing as fuck. - You need to have roles for CMD, BCMD and each individual battalion, subunit, branch, sub branch, training etc. 2. Discord permissions! - Discord permissions are not the same across discords. Each CMD+ or BCMD+ would need permissions to edit the server itself, which would lead to huge security issues and weak infrastructure in the turnout of a bad player getting one of these positions. Not to mention setting them all up and adjusting them as needed would be a NIGHTMARE. 3. Automated Rosters. - Currently We use Bots set up by dedicated members of the community to monitor discords and role assignments/recruits etc to automatically log them on the roster. Consolidating to one discord would cause a plethora of issues as there is currently two bots in use, Jovanovic's bot and Satan's bot. I'm not sure both could work in one discord simultaneously. These bots function on changes of tags, or bot commands. Combining them in the discord would mean having the bot work for 8 battalions, monitoring several different tags and a lot more stuff that i wont mention here which will increase error rate and ruin a decent part of the infrastructure each battalion has. 4. Freedom. - It is within a BCMDs right to create channels as they see fit, For Officers, OOC reasons or documents, Consolidating all these into one discord would cause loading issues and lag when scrolling through discord. Your average discord per battalion or faction has 40+ channels, many sections, NSFW channels, etc. These are harder to maintain and standardize, and take away battalion freedoms. This also allows people to leave all the other discords while still staying in touch with JUST that battalion. A lot of people leave the Community Discord due to general pings or messages and then stay in the couple of discords they're legacy in. This just takes that freedom away and forces them to stay in a bloated discord. 5. Privacy. - While BCMDs and CMDs always have Server Leadership in their discords, there is a degree of privacy given. Having all these put into one discord would cause issues on the privacy front, NSFW channels exist in some discords, Private VCs or tags for Game Night tie back into the Permissions/Freedoms mentioned above. 6. Every battalion does things different. - When creating discord roles, its impossible to have them all on the same level. If BCMD Fox is above BCMD Bacara and they have the same permissions, it now means BCMD Fox can assign all the BCMD roles below him or other tags etc. While there is tricky workarounds to fixing this, its not worth it. Having separate discords allows for even tag assignment, no power struggles etc. 7. Discipline. - People are removed from discords based on blacklists that may or may not be permanent. This is 10x harder to keep track of in just 1 discord as you cannot theoretically ban people from the discord for their issues in 1 battalion as it would lock them out from the server as a WHOLE. 8. Confusion in general? - The most obvious one is, Why would Naval, Jedi, Civilian, 21st, 41st, 104th, 212th, 501st, CG, RANCOR, SOBDE, Leadership and High Staff share a discord? Like.. you didn't give a reason. Just how to go about it and that you think it would help. The server has been around for 7 years and operated quite well on this system, as have many other servers. This would revoke permissions from Legacy members per battalion, Former BCMD tags, fun discord bots setup by the BCMD, Its just confusing and there is generally no reason to do this. We already merged a lot into the main discord with the Training Hub and Some of Leadership being pushed into the Community Discord, battalions weren't done this way for a reason. I, Alongside @Rohan, @Tetraand @Finn do a LOT of the Server's Intel work. Tetra being a big mentor and running 41st, Finn taking care of 501st, 212th and CG, Rohan keeping High Staff automated and helping them create trackers, and myself with 21st RANCOR, (up until recently 104th) and Jedi, We have all fucked with discord permissions, built documents and had YEARS of conversations in these separate discords. Some of these discords have people from years ago who stay in and talk, but nowhere else. Taking away these discords would kill server history and ruin old friendships. I also don't think @Wosyand @Woenywant to go through all the effort of organizing and setting this up. Its a lot of wasted time for those two pivotal members of the community. EDIT: Also there is a role cap on discord roles! Let me show some issues here :P This is the role count in the THREE discords i manage, Jedi Order 21st Nova Corps RANCOR Battalion This is together 304 roles just between these 3 discords. You can at most have 250 roles and maybe a small boost if you're a registered discord partner (don't quote me on this) This is not including the 2 largest battalions on Server, 212th and 501st. It would be ABYSMAL putting effort into this.

Name: Bro RP Rank: Captain of the Guard Suggestion: Replace the current Senate Guard models with these new Senate Commando models Implementation: Remove the current models on the slot and add all of the models from the pack Lore: https://starwars.fandom.com/wiki/Senate_Commando Workshop content if applicable: https://steamcommunity.com/sharedfiles/filedetails/?id=3018120774 (If no workshop content, suggest a developer or put "Require Development") Other: Here are some pics

+1 I gave @Bro set goals before pushing this out dude hit those goals and ran with them.

+1 There are already a lot of people interested in SG, with this change I am sure that ppl will have interest in the long run for SG because they see that SG is getting some love aswell from the dev team

+1 The Senate Guard have been really showing out recently and deserve these new models

+1, the RP opportunities with these models are wide. It opens a lot of doors, and solves the problem of the SG's current insufficient body groupers. 2 birds with 1 stone with the addition of ceremonials.

+1 Like the models more than the current ones. (Bring back Doom's Unit and replace it for 41st)

+1

+1 those models are fucking sick.

+1 JUST BECAUSE I LIKE BRO

I asked a prior dev from that time why it was denied, it had been stated that the Senate Guard wasn't really a thing, and denied for not adding any value. I am suggesting it now, that the Senate Guard are official, in good standing, and have a bright future in both its development and positive interactions with the server. In my opinion and of others, I feel confident in saying that it is a "thing".

Name: Clone For 99 Crosshair RP Rank: Warrant Officer Suggestion: Remove the server rule where you are not allowed return fire upon CT's or any other minge that decides to shoot you. Since I joined Synergy, I always thought this rule was kind of... to be blunt it's dumb. I never cared to try and change it until recently an incident happened and it was brought to my attention. If a minge CT comes onto the server to RDM or MRDM and you are shot or currently being killed, you should be able to defend yourself. It's outrageous how someone can be shot on this server and still be punished and receive consequence for "defending" themself. Yes, it becomes an RDM and Staff situation if you allow them to fully kill the required number of players for it to be a ban. But minges and trolls who actually have a brain will do the bare minimum when it comes to RDM to ensure they are not banned. I personally think it's very dumb that you cannot defend yourself when you're being gunned down by a random CT troll. For instance, 104th is running a tryout with 5 CTs and 1 minge comes in and begins killing them all. The entire tryout has to be reset and everything needs to be restarted all because none of the 7 people there could put down the troll. I personally think this rule should change and I think most of the community would agree. Implementation: Rules Lore: N/A Workshop content if applicable: (If no workshop content, suggest a developer or put "Require Development")

Unfortunately, this suggestion has been DENIED. If the same suggestion is submitted again within 60 DAYS of this post it will be automatically denied. // LOCKED // MOVED TO [CW] SERVER SUGGESTIONS - DENIED

Name: Spectre RP Rank: PFC Suggestion: Consolidate all existing Synergy Discord servers used for Jedi, battalions, and other groups into a single, unified hub server. This will lead to better networking, increased efficiency, and an improved user experience. Implementation: The implementation of this proposal will be carried out in several phases to ensure a smooth transition for all members. During the planning phase, feedback will be collected from leaders and members of different groups to understand their needs and preferences for the new hub server. This feedback will inform the design of the server structure, including the setup of channels, categories, and roles to support efficient communication and collaboration. In the development phase, the new hub server will be created, and the initial channels and categories will be set up. This includes general channels for announcements, discussions, and support, as well as specific channels for each group, such as Jedi and battalions. Roles for all groups and certifications will be defined and created, encompassing battalion tags, certification tags, and any other relevant roles. The migration phase will involve a manual role request system where users can request their battalion and certification tags through the Synergy Staff team. A dedicated channel will be established for users to submit their role requests using a provided template. The Synergy Staff team will review these requests and manually assign the appropriate roles, making the corresponding categories and channels visible to the users. Clear communication about the migration plan will be provided through announcements and pinned messages, and support channels will be set up to assist members during the transition. The migration will be conducted in phases, starting with a pilot group to test the new server setup and make any necessary adjustments before moving all members. Finally, in the completion phase, the old servers will be gradually deactivated once the majority of members have transitioned to the new server and all critical information and communication have been successfully migrated. Continuous improvement will be ensured by regularly soliciting feedback from members to identify areas for enhancement and making necessary updates and adjustments to the server based on this feedback. Add/Change Add: Unified Hub Server - Description: Create a single, unified hub server for all Synergy groups to improve networking, efficiency, and user experience. Change: Role Assignment Process - Description: Replace the current multiple-server setup with a unified hub where roles are manually assigned by the Synergy Staff team based on user requests. Add: Feedback Loop - Description: Regularly solicit feedback from members to identify areas for improvement and make necessary updates and adjustments to the server. Add: Request Channel - Description: Set up a dedicated channel where users can submit their role requests using a provided template. Add: Communication and Support - Description: Use announcements and pinned messages to inform members about the new server, the role request process, and how to get help if needed. Set up support channels where members can ask questions and receive assistance during the transition. Add: Gradual Transition - Description: Migrate members in phases to ensure a smooth transition, starting with a pilot group to test the new server setup before moving all members. Add: Deactivation of Old Servers - Description: Once the majority of members have transitioned to the new server, gradually deactivate the old servers after ensuring all critical information and communication have been successfully migrated. I understand that as a PFC, my word might not hold much weight, but I believe this proposal could be a step forward for the server. It aims to improve communication and enhance the community experience for all users. Any feedback would be greatly appreciated so I can refine this suggestion. Thank you, and I apologize for any inconvenience this post may have caused. - Spectre