Server wide message for Domain Invasion?

[Alhanelem]

Thank you. I really don't understand the logic behind some of the comments, especially seeing as some of them claim to be coders. It seems like they are suggesting something similar to going around and around in circles when it just takes one step forward.

The logic here doesnt even have anything to do with coding. The logic is, we already have the feature being requested and people are making excuses why it isn't good enough just to do so. If people used all of the unities instead of just one because it supposedly has the best trust (i've not used it once myself), they would all have these messages without issue.

Damn, SE's management must love the English side of these forums. Everything gets shot down by some naysayer every single time anyone posts anything.

We're not here just naysaying because it's fun to shoot people's ideas down. It's not and that's not why I'm here. But there is very limited time and resources available for development now, and from a purely logistical standpoint, it really doesn't make much sense to give development time to a feature that already exists on the sole basis that it isn't quite convenient enough when there are a lot of more important issues that the time could be spent on.

2. Join another unity and throw all known strategies out of the window

What strategies? For what content? There are other trusts that can fill the roles of the one or two unity trusts that people care about. None of the unity trusts are so gamebreaking that there is content you can't beat without them. If there is, please let me know so I can try it and either prove you wrong or right. Maybe I don't know what I've been missing all these years of not using that unity, but I doubt it.

If any change needs to be made, my opinion is that it should be making these trusts unlockable like any other and then you don't need to be in a particular unity just for the trust associated with it. Because my point was and is that we already have a system that sends you messages when domain invasions are happening, which is what this topic is asking for. That system has a flaw, yes, but it's a flaw that could be addressed rather than creating a new system to do something that already exists.