Brian-Limmon

Name: Brian Limmond Who helped (If applicable): Luther Link to Event/Encounter Document (optional): N/A Description of event/encounter (required if no document provided): Transport ships started leaving geonosis to get past the venator, they then engaged in battle to try to stop them but after a failed boarding attempt the Viceroy Nute Gunray escaped aboard the fleeing ships Did any Bounty Hunters Participate: N/A

Name: Brian Limmond Who helped (If applicable): Cubby Link to Event/Encounter Document (optional): https://docs.google.com/document/d/1r_MbuFgdodWMyU0Mz_HDKGcjqwRAr1UnTWggbC96GfI/edit?usp=sharing Description of event/encounter (required if no document provided): The event server portion of the Attack of the Clones lore event, recreating the first battle of Geonosis as seen in the Attack of the clones movie. Did any Bounty Hunters Participate: N/A

less than a day until the event, looking like a rip :(((

Name: Brian Limmond Who helped (If applicable): Luther, Deathtiger Link to Event/Encounter Document (optional): N/A Description of event/encounter (required if no document provided): The 212th were sent to an underground district or Taris where they had to investigate the dissapearance of clone patrols over the years, they interacted with the locals and figured out there were secret separatist facilities in the sector which they dealt with until they found the missing clones who had been turned into zombies and took over the district, forcing the 212th to evac. Did any Bounty Hunters Participate: N/A

So do they have potential to crash the server or bring performance way down significantly or do they just have a general negative contribution to overall performance like basically everything else you can spawn on the server?

Name: Brian Limmond RP Rank: SPC Suggestion: Add witcher gates to the main server Implementation: Now that they have been changed on the event server to not allow props to go through them, a lot of the potential lag is no longer an issue and they are much more viable to be used on main for events, they would make for a much smoother process when it comes to things like boardable ships that have interiors separate from their exteriors, so players can just walk through the portal to them without having to each be TPed individually. Lore: Portal 2

Name: Supply drops Who helped (If applicable): Otter, Omalic Link to Event/Encounter Document (optional): N/A Description of event/encounter (required if no document provided): Big CIS supply ship started deploying units to the anaxes base in an attempt to capture it, it failed and got boarded before being blown from within. Did any Bounty Hunters Participate: N/A

Question: Why can't we have the option to disable hud? Comments/Concerns: Not sure that it would cause lag, have any negative effects or be overly complicated to develop since there is already a console command to do so that is just locked to super admin privellaged on the server so I'm wondering why we can't have it Staff Member you're asking: @Jad Additional info:

Spiderman 3 just because everyone else seems to hate it and idgaf :middle_finger: :middle_finger: :middle_finger: :middle_finger: :middle_finger: :middle_finger:

Name: Brian Limmond Who helped (If applicable): N/A Link to Event/Encounter Document (optional): N/A Description of event/encounter (required if no document provided): At first I wanted an excuse to squish palpatine with a rock so made a quick encounter out of it but ended up waiting half an hour for people to do something with the rocks once they collected them lol, the matriarch came once they blew up and all the bugs were killed Did any Bounty Hunters Participate: N/A

yes pls, also let us hide chat, can't record things cleanly with all the unremovable hud atm

Name: Brian Limmond Who helped (If applicable): Perssongi, Xboxtchanka, Ghosty, Misfit Link to Event/Encounter Document (optional): N/A Description of event/encounter (required if no document provided): 501st got sent to a remote planet where a wanted scientist was hiding out with CIS backing, they fought through some droids, found some lost clones and got to the scientists base of operations before he unleashed some near indestructable zombies on them which they had to fight through to the landing zone for evac Did any Bounty Hunters Participate: N/A

Contrary to popular belief, Willy is the senate +1

Fuck Russias leaders*****

This is a very closed mindset. Noone ever said that an event was ruined by not having setspawns because noone has designed their events with that command in mind. Just because you never personally had any ideas or ambitions for events that would only work/be made a lot easier by setspawns doesn't mean there aren't others on the GM team who even just considering this as a possibility for the first time can think of some ways they would like to utilise it.

This is literally the year 1984

Also just thinking about this again, if spawns are able to be set by anyone then it cancels out the issue of them being permanently set on a map because people can just set them to wherever they want to again. The only time it would conceivably be an issue is if a GM for whatever reason doesn't realise where they spawn in and knows a maps default spawn point OFF BY HEART and only realises once people connect... which even then only creates a tiny issue where they have to TP some people after correctly setting the spawn. Honestly even allowing the tool we already have to be used by SA+ would still work considering this. (Also there's already a "set all spawns" option so missing out a single job would also not be an issue

You assume wrong I live in Albania Greece and spain

Yeah I peeped at the replies yesterday and ngl I was very confused why people were actually critiquing the ambitious member goal lmao, I get critiquing the lack of ideas to reach the goal but to just straight up say 21st will never have it and essentially implying it isn't good enough to is like ????? Anyway, from an objective standpoint, it really isn't hard to see why people are very skeptical about how you'll do in this position with the way you worded your emotions, obviously it's good to be honest and open about it. Usually in an app when you openly admit to a flaw of yours that could be cause for concern, you need to use the *BUT* part to sell yourself again and prove to people that it won't be an issue or that it won't affect your ability to live up to the responsibilities of the position, which you haven't really done in that part of the app or the replies. Honestly if you replied with a breif rundown on this rather than just the "I'm keeping it real" thing I'd be comfortable with +1ing since, regardless of the obvious shortcomings of the app that have been pointed out, you *have* made your way up to XO in the battalion and you obviously didn't get there by cowering in fear at every promo and having no goals within the battalion, so I think it's safe to say you would be fit for the position regardless of whether or not your app sells you on it.

Yoda be Katy could think I am yes, hmm? +1

The one after this friday, so when the next venator swap would normally happen

The doc could use a bit of work in the sense that it could go more in depth with how the whole enslaving players thing would be carried out as it seems pretty ambitious but you've been GH of the week like twice now and I'm sure you have what it takes to make a good GM by this point, +1 (also i like that formating lol)

First part is sad but fair enough. I'm mainly talking about us getting an actual command developed so that things like spawns being saved between maps isn't an issue as other servers have already figured out. Also I used the flatgrass thing as an example of how default spawns are really limiting in events, flatgrass events essentially just cannot use the default spawn so people don't consider it in designing their events which leads to a lot more creative freedom taken by GMs in their dupe designs, but people often don't take the freedoms they could be just because of the default spawn thing, they often centre their entire map designs around it which sucks. And the issue with changing spawns when using tacs isn't the pacing of the event or anything like that, it's just the sheer fact that there will be people who don't listen to it and can't participate in the event without GMs having to shift their focus solely onto them in the middle of doing something else, and while you could say it is their own fault just leave them out, it would still be a shame that people have a worse experience with an event just because they were being dumb, weren't listening or even just went afk at the time, so the system we have now takes away from player enjoyment and the ease of running events by comparison to the command system on other servers

All of these problems are just from assuming it will function in a very oddly specific way. Spawns don't have to be set job by job, other servers have no issue categorizing the player jobs into "setspawnrepublic" and the EJ jobs as "setspawncis", these are extremely specific issues that can easily be fixed just by coding the command in a certain way and I don't see why they should take away from the utility of the command overall. And as I've already said, they shouldn't be permenant, they probably even couldn't be permenant between map changes as different maps have different scales and having the same spawn between maps could result in people just spawning in the void, so I'm not sure why it would ever be coded that way. Also you're *really* underestimating the utility that this would have, you're saying most maps default spawns are good as if GMs always just use a map the way it comes, which is far from the case, often times there is an obscene amount of building that can completely transform the layout of a map to where it is unrecognizable from its default state, just look at any of the flatgrass deployments there have been, you can't really just have a "pretty good" default spawn with how massively changeable map layouts can be. And this would eliminate a lot of unnecessary work as already stated earlier with the whole tac process which never goes smoothely and often has to be revisited mid event.