Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by twostars

  1. twostars

    Resetting my seal password?

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

    Is there any way to relinquish kingship?

    It is active.
  3. twostars

    DewilInsTinCMugii IS A SCAMMER

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

    NP transfer (WrYomaneR)

    Dealt with. Thanks for the report.
  5. twostars


    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.
  6. twostars


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


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


    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.
  9. 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.
  10. 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.
  11. 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.
  12. twostars

    This Tag boss Active thing is broken

    Going to assume the problem is resolved.
  13. As reported here:
  14. twostars

    Chaos Dungeon skill bar is not saving

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

    Skill bar not saving on my main character

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

    ItzTOOLATENOW cry after he get npt :D

    These threads are never productive. Stop trying to cause drama.
  17. twostars

    server of ? 离线 NIEAKTYWNY

    Server's usually online, so hypothetically it's online right now.
  18. twostars

    server of ? 离线 NIEAKTYWNY

    Looks fine to me.
  19. twostars

    NP Scroll mysteriously disappeared again?

    No, and I refunded you earlier.
  20. twostars

    Orcs left bdw, we lost.

    Are you suggesting they left to let you win while they themselves received nothing (being offline and all)? As noble as that sentiment may be, it doesn't really change any of what I said. Really, you didn't win. Neither did they. The server essentially treated it as such. Conclusion: No bug. If you're saying that nobody intentionally was trying to abuse anything, then evidently it hasn't been abused either. So: No abuse still (yet?). So I guess we're in agreement that it's probably best to just leave everything as it is then.
  21. twostars

    Orcs left bdw, we lost.

    So basically the only real proposal is to just remove it entirely so people can sit around in the event until it expires so that the losing (but still 'active') side has a chance at winning. Increasing the instance shutdown timer would probably help, but at the cost of making people wait around and I don't think there's ever going to be a perfect time for that. Forcing the remaining side to win makes the event far more sabotageable than it already is, and as-is situations like this can be abused to deny the party that probably would have won the chance at it. As for "not being stupid", I don't see how you can say that -- they got literally nothing out of the event. Nothing. You guys at least got rewarded for losing. I'm not saying they would have won, but they completely wasted their own time just to prevent you from winning... and got nothing out of it in the process. That sounds stupid to me.
  22. twostars

    Be careful fake char

    FYI, Hizliresim doesn't seem too happy with people not in Turkey. Since this is an English forum, most of us aren't going to be able to see anything posted there, so I suggest not using it.
  23. twostars

    Orcs left bdw, we lost.

    I suspected this scenario may occur when I implemented this, however since it's not in their best interests to leave (forfeiting any rewards) we figured it probably wouldn't matter too much. This may just be my sleep-deprived self talking here, but are people really that stupid as to forfeit their reward and waste their time like that? Maybe it's better not to answer that... I mean, if they were still rewarded, obviously it would be abusable in that they could guarantee a win and then just dip. But if they're not there to be rewarded, they get nothing. And since you guys didn't leave, but you also didn't win, you don't get rewarded for winning (obviously). So winner prize goes to nobody. I just don't understand the motivation there. If we were to do what was proposed (and what you're suggesting) and consider the team that stayed as the winner, players would be incentivised to game the system by sabotaging events with characters on the other nation & leaving, making it an easy win for the other (their) nation, which is obviously not ideal. As far as I can tell, doing it like this isn't really abusable in any similar regard... but people are stupid and this happens? Eh.
  24. twostars

    NP Scroll mysteriously disappeared again?

    At any point during that (full) video do you check how long's left on it? Or is it perhaps used during that? (maybe you applied it at the same time as the other buffs, but either way I'd be curious if the duration ever desynced with them) Anyway, about the video all I can really say is this: 1. The buffs themselves are removed on death. The icons for the persistent buffs are not removed visually though, so we still see those. At this point, your NP scroll is still visible (but technically it's removed, as with the others). 2. When you respawn all buffs & their icons are actually removed in the client. This is surprising and dumb behaviour, because I wanted to optimise behaviour slightly so that when you die, the persistent buffs aren't even removed at all, removing the need to be selectively saying "hey, since it's a persistent buff on death I actually don't want you to remove the icon, but y'know, everything else is fine"... which would then mean we also wouldn't need to recast these immediately afterwards on respawn... Alas, we can't do this because the client is stupid. Not without removing that from the client, and I have no idea if that would cause any unintended side-effects. For now this is not overly relevant, I'm only stating this just to break down how these are actually working (despite what it appears to do). Regarding your NP scroll, this is why this gets removed here (as does every other icon, which we don't see because of 3-). 3. Immediately after we confirm the respawn (where the client forcefully removed all icons), we recast all persistent buffs. As it's quick, from your perspective you don't even notice any change other than the NP scroll being removed. But this happened previously, because of the reset. For some reason that's yet to be established, your NP scroll didn't get recast. And more than this, it no longer persists because it either failed to apply and removed it... or it didn't bother attempting to reapply because it's no longer in the list of persistent buffs to recast. -- It's interesting, because the buff does seem to be active prior to your death, so it's not exactly silently removed server-side while still showing as existing. So it should still exist at that point. Yet on the other hand, when they fail to apply, they usually say so in the info box. It is possible there are cases where they do not, but it's a stab in the dark to figure out why that would be. Particularly considering there's nothing special about the buff in the first place, and clearly your other similar buffs were recast just fine. We'll probably just have to wait for this to reoccur, because it still doesn't really help too much with regards to actually identifying why it's not being recast. If it's failing, it'll be logged. And if it's not, all modifications to them are logged, so we should be able to see what it's doing.
  25. twostars

    Lag Problems !

    Then the traceroute you made for now isn't all that useful other than as a baseline. If you give your ISP a traceroute, it should be when the problem's occurring.