Jump to content


  • Content count

  • Joined

  • Last visited

Everything posted by twostars

  1. twostars

    OTP problem

    Please send me a PM with your account name & seal password and I'll take a look for you. Thanks
  2. twostars

    Patch notes (23/02/2017)

    Changelog Potions no longer break stealth. Fixed a bug with some projectile skills breaking (e.g. Styx) as of the last patch. Projectiles no longer care about whether the player teleported, only if they died or are no longer in range. Smokescreen now works as it does officially: it now also blinds friendly targets (including yourself), but unlike official, only in attackable areas (e.g. arenas, PVP zones). Kurian "Pull" skill no longer temporarily visually bugs out monsters (as caused by the last patch).
  3. twostars

    Patch notes (21/02/2017)

    Changelog Fixed a bug with the Bifrost draw timer causing it to effectively not be a thing. Bifrost should now behave correctly in this regard now. Kurian "Pull" skill no longer affects NPCs/artifacts, as this tended to cause things to break. It still works on monsters (which is unofficial behaviour, but intended here). Mage guard summons are now stationary. Fixed a bug with teleport skills (including things like Kurian's Pull/Dash skills) causing them to not respect certain logic and bug out the affected player/monster. Update: Fixed an issue that arose from this which broke some teleports. Projectiles should no longer affect players that have teleported / /town'd / died (they will still follow, but will no longer do any damage). Maestro potions are now included as potions by the Diet curse. Fixed a bug with transformations via curses; they should now be reverted correctly. Players affected by skills (e.g. debuffs) that teleport away at roughly the same time as the cast will now still be visibly affected by it. CSW crystal healing has been nerfed to 20% of the effective healing. Loot range has been increased for ranged classes that were previously on the outskirts and have their loot "stolen" by someone who is still in range. Ranged attacks no longer trigger lightning/fire/ice armour buffs. No longer credit the caster of the undead curse for the kill; as per official, these are now considered suicides. Fixed a potential cause for players to get 'stuck' in-game. Please remember to report any issue you experience with the patch. Thankyou
  4. twostars

    bombastic cursed bug

    This should be fixed as of the next restart.
  5. twostars

    Debuffs dont always show.

    This should be resolved as of the next restart.
  6. The part about it crediting the caster of the curse or it (apparently?) not applying to potions/heals cast by the cursed player? The former was always intentional behaviour. We decided on working it like that a long time ago, but I've changed it in the next patch to be more in line with official behaviour. Is the other part of that actually a thing? I didn't experience that; was solely testing with myself.
  7. twostars

    Possible Bug? Need help regarding that

    If resending/canceling & running it again doesn't actually work, I can activate it for you manually. Looking at it however, the request was made last year (2016-07-10)... so that does indeed look like it's expired.
  8. twostars

    Some curse (i'm guessing sweetkiss) deletes scrolls

    Our testing hasn't confirmed this theory; this curse behaves exactly the same as things like malice, so there's no reason it should be causing this. Unfortunately that doesn't leave us with a lot to go on in regards to finding out as to what is actually causing it. >_<
  9. twostars

    Focus bug

    Could this be related to our party frame changes? i.e. click someone in the party and it will target them correctly (or click them in world and it will target the frame).I don't recall which was originally not behaving as such, but it should be doing that now.I'm not entirely sure what else could have any influence on this behaviour.
  10. twostars

    How many fire rain windforces +11 in server?

    It'll apply to maestro pots on the next restart.
  11. twostars

    Event reject bug

    This only happens to Juraid, correct?
  12. twostars

    About Archers

    The only thing that directly matters in terms of cancelling a skill is the rate of the skill being cancelled. The only reason archers cancel more is because each arrow has a chance to cancel, so essentially with arrow shower that's 5x the chance of cancelling a skill.
  13. twostars

    Bugs after patch

    Closing this as they were fixed.
  14. twostars

    Ally and Clan Bug Fixed Please

    Closing this as it was fixed.
  15. twostars

    Ally and Clan Bug Fixed Please

    Can't join an alliance or the royal clan's cape won't be assigned to them? The latter will be fixed after the next restart.
  16. twostars

    Suggestions/minor problems.

    I mean... hell yeah they are! Yeah, we've known of the issue for a while but only vaguely in terms of the cape simply 'reverting at random', which we could never reproduce. Hate that it took this long to get on top of it, but better late than never, right? Thanks. I think that's where the mix-up is then; here, accredited clans are assumed they'll get/use their own capes & colours. Rather, it should just be the alliance's base cape regardless & their own colouring (the latter of which should already be fine, by the looks of it). I've tweaked that for the next restart. Thanks.
  17. twostars

    Suggestions/minor problems.

    Mind giving me a quick rundown of how capes in general work on USKO at the moment? I feel like the issue here's something subtle (like possibly accidentally overriding accredited clans' capes because they're assigned basic capes?), because as far as I can tell this is how it's implemented already. But it's been a while since we implemented this stuff, so I don't quite recall how that particular system is intended to work. It'd be much appreciated, thanks. Edit: Also, how's priest cancelling feeling at the moment? I believe the main reason for this being so high was fixed already, so I'm not sure if that particular issue still applies.
  18. twostars

    Bugs after patch

    We can't reproduce the stealth issue. Is there anything more to that?
  19. twostars

    Bugs after patch

    This isn't a new issue; this is actually a design flaw that's existed since these skills did. The reason this happened is because Forgotten Temple, like Moradon, is a neutral zone. A warrior of the opposite nation in your party used Battle Cry, and at the moment (and officially) it works such that Cry Echo requires a specific skill ID (which differs depending on nation & class) for you to use it. Since they're from a different nation... neither the client [aka mgame] nor the server [aka us] consider you to have it active. This is entirely a design flaw with their skills. I'll look into hackily fixing that behaviour. Edit: Fixed this, pending the next restart. Will look into the stealth issue.
  20. twostars

    Melee passion

    The problem here was actually just a bug caused by us when fixing the range to match the client. The AoE radius ended up being somewhat larger than it was configured for (and is official). This is fixed now, sorry for all the trouble. :-)
  21. This doesn't always happen. Something seems to trip it setting the main chat as focused edit control, I think.The question is what.
  22. Alright, for this stuff, DirectInput applies. DirectInput, unlike regular windows messages, has separate scancodes for enter & numpad enter. In the old client source at least, I'm seeing some UIs handle both and others just handle the regular enter key. I'm assuming this inconsistent behaviour is causing some things to not be handled correctly. There is, however, a huge amount that would need to check for it so it's probably better it's handled a little more generically.Probably most viable to go all the way up the chain and just say it's always the regular enter key in place of num pad enter. I don't see any reason for any UI logic to require num pad's enter specifically. This was fixed.
  23. twostars

    "Tab" doesn't work in the letter menu

    This works fine now. I assume mgame fixed it at some point.
  24. This is odd. I was inclined to say it's just the UI losing focus, but behaviour seems to vary depending on how you go about, for instance, changing zones (or well, areas in a zone). I noticed that when I'm using num pad enter to "OK" the zone change:1. No matter how many times I press num pad enter again, it won't re-enter the UI. 2. If I press regular enter a *couple* of times (once to regain focus?), it will fix itself. When I use enter OR the mouse to "OK" the zone change:1. Num pad enter works fine. 2. Regular enter works fine also. I need to look into how their logic works for that.
  25. twostars

    Melee passion

    This is mentioned a lot in this thread, so I'd like to clarify what our intentions are here. Essentially, we want to keep things behaving as closely to USKO as possible, unless there's a good reason why they shouldn't. There's a great number of things we've strayed from accurate behaviour for which have only improved things. USKO is a buggy mess. Obviously ApexKO has its issues (which we're cutting down on every day), but for the most part I that feel the server's in a much better state than official. So basically, like USKO, but better. That's the plan. Anyway, with regards to the actual issue at hand, you've all provided some useful insight and your own perspectives on it -- whether you agree that it should be changed or not. And we appreciate that. That's what this thread is for; getting the community's insight on the issues that affect you. The general consensus really is that it should be changed, and well, as Aesteris mentioned earlier, this is something we agree with, so we'll be making changes to it and determining what works and what doesn't. To those arguing against it: as Manhattan mentioned, it's really not that big of a deal to revert if things go sideways. We obviously don't intend to make the class unplayable, or anything of the sort. So we appreciate you sticking around while we work on tweaking it. Again, we appreciate all of your feedback (good and bad) & support. Thanks.