Do Not Suggest: Anti Sniper Great Building Charges

[J.R.]

Sniping of other GBs is a very big part of this game- but to remain relevant it is good to sometimes push back on preconceived 'Holy Grails'- ie sniping.

What if there was a GB that had as one of its benefits a limited charge (like Kraken, Blue Galaxy, Himeji, etc) that could deter a player from adding FPs to your building that wasn't from your guild or friends list?

So there would be a small chance that it could be re-directed- instead of ending up on your GB, it went to your fp bank.

Two players (Player 'A' & Player 'B') are in the same hood.
Player 'A' snipes Player 'B' for 50fps.
The Anti Snipe charge works & 50fps go straight to Player 'B's forge bank as opposed to on their GB.
Player 'A' fumes.

Similar to how the GT works- but with modest % increments & small, limited charges.

Would make sniping a bit more risk/reward.

Russian Roulette.

 

[Forwandert]

There's already risk of clashing with another player (which gives the gb owner a free fully paid level) or the player going inactive and taking 1000s of fps with them. Or simply deleting the gb or not finishing the level.

 

[J.R.]

There's already risk of clashing with another player (which gives the gb owner a free fully paid level) or the player going inactive and taking 1000s of fps with them. Or simply deleting the gb or not finishing the level.

The idea here is that an GB/event build has charges that have a small chance to counteract when an unknown player (so not your guild or friends list) putting unwanted fps on your GB (ie, sniping) instead loses & those fps go straight to your fp bank....so essentially a snipe protection charge....

 

[Forwandert]

The idea here is that an GB/event build has charges that have a small chance to counteract when an unknown player (so not your guild or friends list) putting unwanted fps on your GB (ie, sniping) instead loses & those fps go straight to your fp bank....so essentially a snipe protection charge....

You can't generally get sniped unless you leave gbs available for snipe. You can lock levels and only open when you have players ready or calculate the positions and leave them at 1.9

You posted it as adding a bit more risk but there are already risks. Those are actual risks too as you can prevent the actual snipes as a gb owner.

Sniping isn't someone unwanted adding fps to your gb, you know that right?

 

[Emberguard]

This would be impossible to program on the basis of a snipe unless you can define it in exact terms; people can’t even do that after 11 years of discussion. What exactly are you determining as a snipe for the purpose of such a Great Building?

Conflict of interest is not programmable. Intent of the contribution is not programmable. Player A and Player B would be indistinguishable in the code aside from one contributed first

Are we talking someone overtaking another contributors contribution? Are we talking someone levelling up the building? Are we talking a contribution less than a subjective amount (that is in constant flux)? Are we talking anything contributed at all?

Personally I think it’s a bad idea even if you manage to define it.

The idea here is that an GB/event build has charges that have a small chance to counteract when an unknown player (so not your guild or friends list) putting unwanted fps on your GB (ie, sniping) instead loses & those fps go straight to your fp bank....so essentially a snipe protection charge....

Unknown people are already automatically unable to contribute unless the current level already has a contribution from them.

So your definition would result in a building that is either impossible to activate, or only activates in the instance of someone contributing on a open level, dropping out of your social circle, then continues to contribute on the same level

 

[Knight of ICE]

Apart from the fact that there have been suggestions regarding sniping before, this is on the DNS list.

https://forum.en.forgeofempires.com/index.php?threads/do-not-suggest.37648/

* Suggestions for new Great Buildings