Jump to content

Wolf

PC Member
  • Posts

    26
  • Joined

  • Last visited

Posts posted by Wolf

  1. 6 hours ago, [DE]Rebecca said:

    If you're not an active participant in the Clan / Dojo system, a lot of this will go over your head. But if you've noticed a discrepancy in your Clan's Dojo XP since the release of Update 25, we have found the issue and have a full breakdown here.

    The issue:
    Upon researching the Update 25 Clan weapons, some Clans / Dojos had a loss of Clan XP. On the surface this seems like a pretty straight forward problem, but it has turned out to be a bit more complicated. Your "Clan Profile' page showed research and Pigment XP gains, but there was a whole bunch of invisible XP messing with values especially if you deleted a decoration or room, and finished weapon research (namely, from Operation Trophies)!

    The solution:
    - All trophies are now exempt from Clan XP and will not reward it.
    - The Trading Post and Treasury will supply their intended XP.
    - Room XP will be left alone (get your XP on first build), just exposed so you can see it.

    Next steps:
    As we release eligible content, you can re-rank your Clan over time. We have record keeping of your rank, so you won't re-trigger the rank up rewards.

    Sorry for the confusion!

     

    Just to be clear, will all clan XP values be retroactively "fixed"? (So that every clan with the same amount of research will be on an even playing field)
    I noticed my clan lost some XP after a certain update and I assumed it was one of the weapons giving a negative amount.


  2. As we can see in this video (provided by the lovely @Faber), these specific dojo decorations have a weird texture bug since (the last mainline?)! I hope this could be fixed as it messes up some of our dojo decorations!

  3.  

    44 minutes ago, [DE]Rebecca said:

    Client-Authoritative Changes:
    We have made some much requested changes to the responsiveness of two things in Warframe: Weapon swapping and automatic doors. Right now in Warframe, if you are connected as a client you may have experienced delays in responsiveness of either of these essential things! The changes should result in a much smoother experience:

    - Swapping weapons as a Client will now feel more responsive because we've made it Client-Authoritative.
    - Automatic Doors have been made Client-Authoritative. Previously there were cases of door not opening in tandem with the Host if any latency was experienced. This is likely going to ship, but in the event it's too risky we will polish and roll out later.

     Switching to operator should also be Client-Authoritative

    • Like 1
  4. On 2019-02-05 at 5:26 AM, WhiteMarker said:

    Judging by the thread title, this can't be useful/valid feedback.

    Funnily enough the OP does contain plenty of useful/valid game bug feedback.
    Perhaps next time you comment on a thread you should read it first?
     

    On 2019-02-05 at 5:26 AM, WhiteMarker said:

    Such long runs have nothing to do with the game. This whole run was cheese and nothing else.

    On the contrary, if such a long run is possible (which it is clearly) then it does have something to do with the game.
    It's a challenge for players to theory-craft for and physically endure as players. If a player doesn't want to engage in such game-play, then they just don't. However the players that do want to participate in such an activity should be able to do so.

     

    On 2019-02-05 at 5:26 AM, WhiteMarker said:

    You don't want to give feedback. You just want to brag that you have nothing else to do with your time.

    The players that engage in this type of game-play have every right to give feedback to the developers on it. And also have the right to tell other people that they did such a run.

  5. If the current founding warlord of a clan has been offline for over 30 days you can submit a support ticket to have it transfer for whichever other clan member has been in the clan for the longest.
    Instead of writing a support ticket about this problem you have, try waiting for the guy to go offline for 30 days and then writing a support ticket along those lines @MXXVI

    I can provide an example of such a ticket if you wish.

    • Like 2
×
×
  • Create New...