I think there should be a right for a CL to give auth to Mass mail their hitters, because then it'll save time and you could send every hitter a mail regarding emergencies. This can only be given by a CL and it has to be HSL and CL can take it away, and everything. Post ideas or comments on why it's either a bad idea or a good idea.

This can save a whole bunch of time and save Hitters in the family, it should be just like the LHM part just Mass Mailing that's it.

If the only coded benefit to this proposed 'HSL position' is being able to mass mail members, it's not needed tbh. A HSL can easily have lists done up of hitters (with subsets made for trusted hitters, bg shooters, pro'ers, etc etc depending how they want to run their wars) to slot straight into a mail and send it out just as fast as any hard coded version of the same (with many more options available to them).

That said, I've previously suggested having options available to provide certain hq rights to members other than the rhm/lhm, so I've technically no issues with it in theory. I also do see the flip side, by not having these options, that make the choice of rhm/lhm far more important given only they have certain rights. If they all happen to be on at a similiar time each day, with no upper structure around the rest of the time, it's a risk a family are taking and live by the consequences. So pro's and con's to any potential change here.

So your saying that, its because it'll make RHM and LHM look like they're not a big deal?

Sorry, just curious of your comment ;)

I could be wrong.. but isn't this where IRC comes in handy? it's much quicker and easier in my honest opinion.

Yeah you're right but, its hard to get them on :)

I'm not, at all. I've no idea where you inferred anything of the sort.

I said that:

1) the reason you've given for this to be hardcoded, based simply on mass mailing, isn't a reason in my opinion. It can be done manually with a tiny ammount of work. If a HSL isn't willing/capable of doing it, they ARE the wrong person for the job. I'm not saying it can't/shouldn't be done, but personally I'm fine with someone, outside of the lhm/rhm having to put in some work to do it, so am personally not keen on the idea. It's a subjective matter, so simply giving my opinion on it.

2) If the suggestion was extended to allow for further rights to be given to a member in this role or members in general (though the addition of the new sponsor role has gone some lenghts to introduce this, but with large benefits [in theory at least, in practise it depends on the sponsor in question] in terms of training to outweigh the negatives), it begins to remove one of the logistical challenges of picking the right cl/rhm/lhm team. I'm not suggesting it makes the RHM/LHM 'not a big deal', it's simply removing one of the challenges of ensuring you've got the right people by being able to spread/dilute the workload/responsibilities furhter.

More wars have been started due to the words/actions/mistakes/decisions of upper structure members than I care to remember. If you believe they need some artifical ego boost to feel power in their role, as I assume you must if you take that from something I say when it was in fact never suggested or implied, then I believe you greatly underestimate the responsibilty the role comes with. My issue isn't with making it look any less important with this suggestion, it's simply with making the choice of these important roles easier by reducing the impact of time online/activity/dovetailing of hours on the selection of people for this role (along with the more important aspects of trust/loyalty/knowledge/experience/intelligence/motivation/dedication/etc etc etc etc).

It can, the suggestion can have more rights, I just put in some ideas and I wanted people to give it more rights and ideas so it can be an improved suggestion, and yeah I agree with your comment, the HSL should work and have all those qualities you named on them, and then they can earn the privllage of Mass Mail. The HSL shouldn't be the lazy unworking type of course, they should be always willing to do the work, without that why call them "Leader" of a HitSquad.

Yeah I agree with you, and I hope to see more thoughts and arguements in this thread it'll help the idea grow :)

There is a very simple way for a HSL to massmail the members of his squad. TO: NAME,NAME,NAME,NAME

Any good HSL should be able to recall the in game names of his hitters. It is very simple to type their names in separated by commas and click send. There is no need for the HSL to have his own section.

I made a suggestion a loooong time ago along the lines of CL Delegation (http://mafiareturns.com/comm/thread/18186). Most of it's now in existence, but the HSL part isn't. I still think there's room for a dedicated "HSL" assignable role (not publicly published of course). Mass mailing isn't reason enough to add it since there's a simple work around, but they could have other privileges delegated if their CL so desired. For example, the ability to remove guns, hand out a gun, deal with auth/perm auth requests and anything else that's relevant to the role.

What is the "HSL" role that we've created?

I really do not see the need for it to be hard coded at all. The LHM position is vastly under utilised, with the majority of them being low ranked and deemed rather unimportant in the scheme of things. I'm not tarring them all by this brush as I'm sure lots of capable people have this title at the moment, but the point is that the actual features they are assigned makes them just a weaker form of RHM. They can't HQ wack, they can't promote, they've really only got the benefit of the crew page and invite feature. Therefore in terms of capacity this would make them a good choice for your "HSL" or "enforcer" rather than "Consigliere".

The LHM position is vastly under utilised

Definitely agree there, to the point that it's almost a glorified sponsor in terms of the privileges (not in terms of their boss's assessment of them).

Note: I realise the LH plays a role in interactions with other families/cities, I'm referring to functionality only.