New Pushing System

Discussion in 'Headquarters Archive' started by Juturna, Nov 19, 2013.

Dear forum reader,

if you’d like to actively participate on the forum by joining discussions or starting your own threads or topics, please log into the game first. If you do not have a game account, you will need to register for one. We look forward to your next visit! CLICK HERE
Thread Status:
Not open for further replies.
  1. Juturna

    Juturna User

    Hello Space Pilots,

    With the bots out of the way we feel confident that we can change the way our pushing system works. Instead of retroactively sanctioning players once a month for excessive pushing we will now use a diminishing returns system.

    The honour and experience received from killing a same player will be slowly reduced for each new kill after the third, until reaching 0.

    So, after tomorrow’s weekly update, attacking weaker players will not be worth it for a long time, and the good pilots will have to look for new challenges to get more honour and experience.

    -Nyx-


    ______________________



    This is how the new system works:
    • If a player receives honor points or experience points from the kill of the same player more than 3 times in one day (being one day from 00:00 until 23:59 hours, sever time) the amount of honor and ep received is reduced for every new kill of the same player.
    • After the third kill, each new kill will perform a reduction of a 15% over the basic honor and experience. So, if a basic value received from the kill of a player was 100, with the fourth kill of the same player the value won will be 85, with the fifth kill 70 and so on till reach the value 0.
    • When the Honor rewarded for killing a player reaches zero, this player will also stop adding Kill Points for further kills.
    • When the server time reaches the 00:00:00 hours the kill counter will be reset to zero.
    I hope that helps. Looking forward to your feedback.


    RickDekard


    Originally posted 05.09.13
     
    OldHandGA1 likes this.
Thread Status:
Not open for further replies.