Haram Bae Hoovy

It took me about 3 attempts on a different server to convince people on forums that a cloaking device needed to actually cloak people, not just give them an opaque material. This is nothing new to me. If you want we can still go check out how the OD system works on other servers. It's not as bad as you made it out to be

ye this thread should be closed, ready to reopen a new one in a week or two whenever the limit runs out but this here is a shitshow

forums are notorious for people not actually reading into the concepts and dogpiling like this so I don't mind if this takes a couple attempts. Also my offer to Archer still stands.

aight whats the time limit till I can suggest it again? I've had to suggest fixes in forums for stupider things and it's taken longer so I don't mind redoing this in like a week or two in a new post that answers all the misconceptions

sure thing, how would you like it? If you want we can go check out other servers together or I can ask some of the lads from servers where this has worked to pipe in(as long as we are in agreement that this does not conflict with the no advertisement rule). I'll gladly put in the legwork for that kinda thing. I'll listen to suggestions you might have for this. already answered in very first post: since OD has no other duties than being OD they can realistically be expected to not tab out and pay attention to comms. If OD needs to leave, OD get's handed over to someone active. Any transgressions could be punished internally by battalion. could you rephrase this please? I don't quite understand what you are trying to say here. which is a cumbersome solution for a problem that wouldn't even exist if we had OD. Also there would still be conflicts if there is a disagreement between two batts of the same rank. Also realistically not everyone knows battalion ranks by heart. Even the greenest CT can understand however that one listens to OD. As said by yourself however a battalion may be tabbed out or afk. This does not happen with OD. not quite, with the current system one can expect around 0 to 3 answers. With the OD system you get precisely one answer. We already have the concept of leading batt to avoid confusion in events and it works much better than various batts giving conflicting orders mid combat. OD system is just a continuation of that train of thought.

Looking for one person with OD in their name is much quicker than having to check who outranks who and who is active rn. Also since you are just asking for OD you don't even have to know who has it. You just ask OD to grant and done. As I said before I have experienced this working on other servers and it does work better if properly implemented. Additionally Battalion all have different jobs such as doing trainings for assigned regiments or holding meetings with other battalion or regimental leadership. This will naturally lead to them not paying 100% attention to comms 100% of the time. With the OD system you have one batt devoting themselves to comms and the like and all the others can concentrate on their current tasks. This also eliminates the problem of multiple competing answers in comms since there is only one OD. I am glad that you see that my proposal can be faster. I understand that a new system can feel daunting, same as cars must have felt to a society running on horses. If a system is faster it should be attempted even if it may cause some temporary confusion while everyone get's used to it. The longterm benefits outweigh the short term costs. Why not? I believe I have demonstrated that it would be quicker and that you have acknowledged this. As stated before I have seen this work on other servers where I was battalion equivalent so if you have any more fears regarding this proposal I'd be happy to dispel them. Apprehension to new systems like this is normal but shouldn't hold us all back. Nah mate it may be tedious but I believe that with enough arguments I can convince people since I know for a fact that this system works.

and the OD system is a useful upgrade to a server. I've seen it work better than the system currently in use here which is why I want to improve the experience for everyone. Just because something works to a degree does not mean that it can't be improved and work better.

and even simpler would be check who is OD and done. This is unnecessarily long which is convoluted and could be done easier by just checking who is OD and done. The current system is way less efficient there is a mechanism granted but it can be improved.

Horses work fine as well. But if you've experienced cars you don't wanna go back to horses. The way we do this rn is slow and can be done better. I understand if something new feels weird but I encourage you to engage with concepts you are unfamiliar with.

Aight so to everyone thinking I'm tryna give myself power or some shit, that's BS. Who get's to pick OD is still the highest ranking officer. So for instance if Battalion is on it's Battalion that get's OD, if no batt is on one of the Commanders takes OD etc. If a battalion is afk a Commander takes OD etc. All this does is make the wait time from: -permission to leave Base to go training -no one answers -asks in ooc for someone to grant -a bunch of battalion all hit their binds, sometimes the same sometimes different answers -if there are different answers in comms check who was highest ranking or who voided his bind -leave base to go training (of course the above scenario doesn't always happen but we all have seen it happen and it's slow and can easily be done better) to this: -permission to leave Base to go training -OD grants or denies This just streamlines a process that rn is inefficient. Coming from a server that implements this kind of system it just really grinds my gears that this process is so slow here. OD is not a permanent rank, it switches to whoever from battalion wants to be in charge of denying/granting shit rn and can be revoked by higher ranking members of battalion anytime. It just makes it easier for everyone on the server to know who is in charge of granting shit and who's orders they need to follow in combat. This is useless as a powerplay tool since people only really get it when they would have been able to grant it anyway. In practice it falls to the highest ranking active battalion or a lower battalion rank who is in training and getting OD for that person. I appreciate the feedback but honestly so far it seems that most of the criticism has not actually understood the concept. Please ask questions about this instead of coming with criticism that just shoots right past what I am trying to propose.

it's not needed but it is a quality of life improvement. Which is super inconvenient and convoluted at times. It works but it's tedious and there are quicker ways to do this. Instead of going "who's in charge rn" every time a request is made, you could do it once and then designate the person in charge with OD in their name. This system is a quality of life improvement. It's not strictly necessary but it does streamline the way we do things rn.

oh you must have misunderstood the point of this. So basically all this does is make clear who is in charge rn. The only reason a 2nd LT is there is because I used my own name as example. Realistically OD will nearly always be Battalion or some Commander if no Batt are available. The real benefits of OD is that you always have someone who is in charge of the base and who knows they are in charge of base. So for instance you don't have to ask in ooc(someone with perms grant please) since you know who is OD and OD knows they have to pay attention to comms. It's basically just a formalised version of leading batt and I've seen it work on other servers and feel like it could improve the current server.

What your suggestion is: OD stands for "On duty" and refers to the on duty officer. OD is in charge of granting/denying shit in comms,commanding base operations and leading events. When someone takes OD they add OD to the end of their name.(For example 41st 2nd LT Hoovy becomes 41st 2nd LT Hoovy OD)Scriptfodder/workshop link: N/AAny additional information: We've all seen it happen. Someone will ask for permission to do something like leave base and be hit with either nothing or 2 "granted" binds and one "reason?" bind at once followed by a bunch of "voids" in ooc. Additionally there should be a better way of finding out which battalion is leading an event than having to ask in comms or ooc whenever you join. This is why I suggest the OD system that I have seen work well on other servers. It is pretty straightforward and makes sure that the chain of command is always clear. Even in hectic combat situations it is immediately apparent who is in charge and will eliminate confusion in the case of multiple battalion or other high ranking officers talking in comms at the same time. The rules regarding OD are simple -Anyone with a higher rank may take OD off of a lower rank. -OD may never go afk and must hand over OD to someone else before going afk. -OD may give orders to higher ranking officers (but of course can have OD taken off at any point by higher ranks) -Any change of OD must be announced in comms (2 binds necessary for this:"I am now OD!";"I am no longer OD!") -Whenever feasible there must be an OD (so when no battalion are available, one of the regimental officers takes OD) This ensures there is always a proper chain of command. With regards to OD outranking every other officer I have seen servers where there were rules like OD is only equivalent to a certain battalion rank so wont outrank admirals or the like. If a specific battalion rank is to be picked as OD equivalent I leave the specifics for battalion to decide. The same goes for rules regarding when Jedi can take OD and when they have to listen to OD.