Jump to content

twostars

Administrators
  • Content count

    1457
  • Joined

  • Last visited

Everything posted by twostars

  1. twostars

    bad buy ordeas help me plz

    Also: character name?
  2. twostars

    BUG + BUG-ABUSE

    It's just the infiltration quest. They can't attack anything. There's no bug abuse here.
  3. twostars

    Achive

    Those rewards were intentionally removed.
  4. twostars

    Resetting my seal password?

    PM me a new unique e-mail address to change it to.
  5. twostars

    Is there any way to relinquish kingship?

    It is active.
  6. twostars

    [Daily] Taming the beast mission

    I've just hotfixed this. Should work now.
  7. twostars

    DewilInsTinCMugii IS A SCAMMER

    Enough. None of that is relevant to this thread. Consider yourselves warned.
  8. twostars

    NP transfer (WrYomaneR)

    Dealt with. Thanks for the report.
  9. twostars

    El Morad Commanding Officer mission(s)

    This is predominantly an english forum. Most of the staff don't speak Turkish, so please don't expect us to translate every single one of our forum posts for your sake. Use google translate or something if you have to.
  10. twostars

    El Morad Commanding Officer mission(s)

    Hm. The change was intended for loot rewards mostly, but yes you're right, that's how it works. In terms of loot, you're wanting to be there regardless because there is still a range on it (even just the technical lootbox spawn range, i.e. it won't spawn if you're not there). For quests this is indeed less important, but you're also not going to be put in combat anymore until you're there. Hm. Will think about that one. Some cases, like this one, I feel like it should behave differently (e.g. for this, reward the entire invading/defending nation). For most others, I think this behaviour makes more sense. Edit: Might be better to just bring back putting the entire party in combat... but limit the range, so it's not abusable as it was before. That way if you're anywhere near the monument when someone in your party hits it, you'll be put in combat and get quest credit.
  11. twostars

    TÜRK YETKİLİ KONUYA BAKA BİLİRMİ..

    No. Push your luck and keep asking and I'll change my mind... and IP ban you instead. The old one isn't being unbanned. Stop asking.
  12. twostars

    El Morad Commanding Officer mission(s)

    The quest you have, does it specifically say Linate, Bellua on it? I'm wondering if it's a bug with opposing nation quests.
  13. twostars

    TÜRK YETKİLİ KONUYA BAKA BİLİRMİ..

    You can create a new account/character. Note that we don't support account sharing. Your old character will never be unbanned though.
  14. twostars

    FIX WARRIOR DMG WHAT IS GOING ON HERE ???????

    Y'all are getting off-topic. On the topic of warrior damage, we've reverted a couple of nerfs:
  15. twostars

    Patch notes (20/04/2018)

    Changelog [Hotfix] Warrior's Cry Echo is now correctly dealing 300% damage + 200 bonus damage again. [Hotfix] Warrior's Berserk Echo is now correctly dealing 300% damage again. [Hotfix] Changed scaling on the Plwitoon stuck in lava to account for the fact only ranged can deal damage to it Fixed a bug causing skill bars (Chaos Dungeon & regular) to not correctly save sometimes. [Hotfix] Cleaned up daily/weekly/monthly quests some more. This should fix them not correctly resetting data. These previously worked such that the quest data shown to the client was different to that reset/tracked by the server. It behaved like this for 2 reasons: 1. So that we were able to easily identify these types of quests (and reset them on access, because unfortunately there was no better way). 2. So players could still see the quest in the NPC's menu after it was completed. In this case it would error saying something like "You have already completed this for the week". This behaviour was very error-prone (particularly with things like week identification on completion; this doesn't play nicely with being able to turn in the previous week's quest and take it again for the following week), and in general just a mess, so now weekly/monthly quests behave like all other quests: when a quest is completed, the NPC does not show it anymore until it's reset. NOTE: As this caused weekly quests from last week to not reset correctly (causing players to not be able to take them this week), we've hotfixed these to reset as of today. That means these have all reset a couple of days later than they should (potentially causing loss of progress to those who did still have it). This was unavoidable, sorry. Certain quests (for now, only applicable daily/weekly/monthly quests) will now be transferred when you Nation Transfer. Previously, transferring meant you'd have both copies of certain quests (one per nation), which were tracked independently. Now, for the quests we've allowed for, you will only ever have the 1 quest -- and your progress will transfer over to the other nation's variant of that quest when you transfer. This makes quests like [Monthly] A small challenge more attainable as players will retain existing quest progress after transferring. Existing quest progress will not be merged; only the credit for your current nation will count. This only applies to quest progress going forward from the patch. Fix a bug with quest progress not being reset correctly on login. In other news, this week we've been getting back into our client source project. Since it's been a while we're still getting reacquainted with the sourcebase so progress is a little slow, but we've: Implemented name change support. Updated resistance logic and implemented the newer stun rate algorithm. Implemented skillbar saving/loading, with future support for Chaos Dungeon skillbars (when that's eventually implemented). Updated warp list logic & implemented all various warp list (and some other) errors as of current 2.1xx clients. Updated quest support & implemented existing quest UIs [quest tab+quest info popup & level guide]. Mostly implemented stealth/lupine skill behaviour (still a work-in-progress). Client now correctly supports even newer effect files. Implemented support for unpacking/using newer client files. Still a lot of work to go before it's in a usable state, but it's getting there. With larger things like transformations (soon!) out of the way we can probably start working on a newer client version and the systems involved with that (e.g. 1.534, letter system, new event & quest systems, etc).
  16. twostars

    FIX WARRIOR DMG WHAT IS GOING ON HERE ???????

    We're not restoring the +15 STR. Sorry, but that was always a bug. It's really not even worth suggesting at this point, unless USKO happens to do so (which I doubt), it's not coming back. It existed primarily because we assumed their data was wrong. But it wasn't; it intentionally didn't give that STR, so we removed it. Complaining about it is silly. As Aesteris said, it makes very little difference in damage output, the only reason it's so overblown is because it was a 'nerf' (if you can even call it that) to warriors, and "OMG WTF GM WARRIOR NERF WTF". Considering OP is in general complaining about a larger damage disparity, this 15 STR doesn't help solve the OP's alleged problem... so again: complaining about it is silly. It's not being changed back, so you can stop trying to blow that small change completely out of proportion and just deal with it.
  17. The party system in the client source code doesn't yet support drop-down menus, let alone party leader promotions so this behaviour doesn't exist yet. We'll have to be careful to avoid repeating mgame's mistakes when we implement it.
  18. twostars

    Party interface commands bug

    The party system in the client source code doesn't yet support drop-down menus, so this behaviour doesn't exist yet. We'll have to be careful to avoid repeating mgame's mistakes when we implement it.
  19. twostars

    "Tab" doesn't work in the letter menu

    Letters (and ROFD+ behaviour) aren't implemented in the source yet, so we'll have to bear this in mind when we implement this and ensure we don't repeat mgame's mistakes.
  20. twostars

    This Tag boss Active thing is broken

    Going to assume the problem is resolved.
  21. As reported here:
  22. twostars

    Chaos Dungeon skill bar is not saving

    This will be fixed after the next restart.
  23. twostars

    Skill bar not saving on my main character

    This will be fixed after the next restart.
  24. twostars

    Power over player at war

    So we could go a few ways with this. 1. We could outright disable it, because it's a useless feature primarily being used for trolling. 2. We could further limit it at a target level (at the moment the cooldown exists for the commander that used it, so multiple war commanders can use it at the same time). 3. We could exclude players currently casting from being affected by it (I'd ideally like to push it further to only those that aren't in combat, but that's something we're still looking into in and of itself). Thoughts on these?
  25. twostars

    ItzTOOLATENOW cry after he get npt :D

    These threads are never productive. Stop trying to cause drama.
×