Mitchell

If you guys dislike Mas having RCMD perms feel free to either make a suggestion about it or talk with the @ Directorabout possibly changing it. Leaving this here for anyone else with similar sentiments about the position

Name: Mitchell Staff Rank: HA SteamID: On roster. Length of LOA/ROA (Please specify date if possible): Should be 2 weeks. Reason: Prepping for school, dealing with ALOT of IRL stuff that was dumped on me. I also need to spend time with my GF before heading up to school etc. Do you understand that if you go LOA/ROA on a named Jedi Character for more than two weeks, go on LOA/ROA on any RC character, or go LOA/ROA while being clone commander, you will be removed from that position: Yes Do you understand that if you are going on LOA/ROA for more than two weeks you may lose your leadership position?: Yes

Congratulations! You have been ACCEPTED into the CWRP staff team! // LOCKED // MOVED TO STAFF APPLICATIONS - ACCEPTED

Your LOA has been logged as COMPLETED. If this is an error and you require more time, please contact a Head Admin or a Director immediately. // LOCKED // MOVED TO LOA - COMPLETED LOA'S

Show them this.

Your LOA has period has been APPROVED and LOGGED. Please notify us if your LOA is to end early, by tagging me here with an @. If you have not requested an extension to your LOA before the original date then you will be assumed to be off LOA after the LOA period is complete.

Name: Mitchell Who helped (If applicable): N/A Event/Encounter Name: Winter Assault Link to Event/Encounter Document (optional): Description of event/encounter (required if no document provided): Spec was deployed to lay siege to several enemy compounds within a sector. They utilized orbital bombardments in order to break the rayshields in order to take the facilities and were successful in doing so.

Name: Mitchell Staff Rank: HA SteamID: on the roster Length of LOA/ROA (Please specify date if possible): 1 week. Reason: I need a break. Dealing with personal stuff. Do you understand that if you go LOA/ROA on a named Jedi Character for more than two weeks, go on LOA/ROA on any RC character, or go LOA/ROA while being clone commander, you will be removed from that position: yes Do you understand that if you are going on LOA/ROA for more than two weeks you may lose your leadership position?: yes

o7 my dude.

With the media player being used quite alot, felt like I would drop my playlist of music that I use for events along with a few highlighted tracks. ^ above is the link to the playlist in full, currently 30 songs but I will be adding more. Few highlighted songs. ^ 26 seconds in is the best fucking music I've heard in along time. If yall post any music below I may add it to the playlist.

I don't think the steamworkshop would let you even upload a file that size LOL

@Woeny

Before anyone asks, yes, I didn't include Foxtrot. They're in hell along with 101st.

Man there is so much wrong in this. 327th wasn't removed 3 times, it was removed twice. The first time I can't speak about much but the second time had nothing to do with anything you have said. It wasn't directly at fault of the battalion, it had more to do with the server environment along with the fact that the founders decided to make a public poll where people got to send who ever they wanted to the gallows, tanking what ever PR battalions had and pretty much dooming them cause no one wanted to join us. You say dead on launch yet during the times they had actually good BCMDs they were the most active battalion on the server? Back when Poe was BCMD they regularly were the most populated battalion. This continued until legacy infighting caused things to turn to shit. Cannon (the banned one) probably was the single reason why the battalion would end up being removed. The amount of issues he cause for the battalion was so damn high, from trying to get tripolli removed to trying to block people from getting leadership positions who could of helped the battalion. While yes the 327th HC should of removed all of them from the discord, the Directors should of stepped in eventually to remove that problem. We had a steady presence throughout the entire time we were on the sever, of course we became inactive at times but every battalion's activity ebbs and flows. You're judging your perception of 327th based off of the tail end, which saw the reduced activity, but you also ignore the fact that we were turning things around by the time we got removed with us having 15 active members who would be on throughout the day, not crazy numbers but still was a solid core of people. The only thing I can somewhat agree with is that we do need to stabilize the current battalions before we add more to the server.

Congratulations! You have been ACCEPTED into the CWRP staff team! // LOCKED // MOVED TO STAFF APPLICATIONS - ACCEPTED

IMO PVP oriented BVBs only brings toxicity to the server, if we do bring them back (which there are some ideas for) it would require us to come up with fun activities that people can enjoy that isn't sweaty GMOD gunfights. Ultimately, it comes down to certain groups having a much higher competitiveness to the point where it becomes a detriment to others on the server who just want to have fun. If we do PVP stuff I'd just kick people out of the tournament that are turning things toxic or keep things alot more low key instead of trying to hype it up into this big thing that people need to win so they can brag to everyone that they won a SWRP PVP tournament.

All battalions on this server are the same. With standardization no single battalion has anything unique outside of what vehicles they might train for, sub units, and lore characters. The expectations are 21st cause of ship boarding, and Grey RC cause they are RC.

Your LOA has been logged as COMPLETED. If this is an error and you require more time, please contact a member of High Command (MCMD+) or a Director immediately. // LOCKED // MOVED TO LOA - COMPLETED LOA'S

Your LOA has been logged as COMPLETED. If this is an error and you require more time, please contact a member of High Command (MCMD+) or a Director immediately. // LOCKED // MOVED TO LOA - COMPLETED LOA'S

Your LOA has been logged as COMPLETED. If this is an error and you require more time, please contact a member of High Command (MCMD+) or a Director immediately. // LOCKED // MOVED TO LOA - COMPLETED LOA'S

Your LOA has been logged as COMPLETED. If this is an error and you require more time, please contact a member of High Command (MCMD+) or a Director immediately. // LOCKED // MOVED TO LOA - COMPLETED LOA'S

Your LOA has been logged as COMPLETED. If this is an error and you require more time, please contact a member of High Command (MCMD+) or a Director immediately. // LOCKED // MOVED TO LOA - COMPLETED LOA'S

Your LOA has been logged as COMPLETED. If this is an error and you require more time, please contact a member of High Command (MCMD+) or a Director immediately. // LOCKED // MOVED TO LOA - COMPLETED LOA'S

Your LOA has been logged as COMPLETED. If this is an error and you require more time, please contact a member of High Command (MCMD+) or a Director immediately. // LOCKED // MOVED TO LOA - COMPLETED LOA'S