PK Discussion From Rage (Split, Not a Rage Thread)



  • MoireanMoirean Chairmander Portland
    You still need to code offense...
  • Malok said:
    When Whyte released mudbot curing to Imperian, a lot of people whined. I think it improved the game there by leaps and bounds.
    I agree with this completely, and I have longed for such a thing to happen on Aetolia so that you can actually see who the most clever combatants are, and not who know how to code best are.
    To be honest, I don't think coding ability correlates that much with combat ability/knowledge. I've seen excellent coders who never break out from mid tier, and top tier combatants with so-so coding ability, far more than those who are both brilliant at coding and combat.

    You need to know basic code. It is a threshold requirement. But from there, combat ability is very quickly determined by combat knowledge, rather than technical knowhow.
  • Moirean said:

    You still need to code offense...

    Which is much, much easier than programming 200+ afflictions or whatever we're up to now.

    "Hell hath no hold on a warrior’s mind, see how the snow has made each of us blind. Vibrant colors spray from new dead, staining the earth such a beautiful red."
  • SerriceSerrice the Black Fox
    edited January 2015
    Technical knowledge is useful. Motivation, know-how, and an understanding of mechanics and player behavior is far more important.

    I have a BS in computer science. The entirety of the classes that might conceivably apply in day to day maintenance of my system were my software engineering class (which was less about coding and more about how to formulate, design, and plan out software projects), my undergraduate data structures class (hashes, linked lists, stacks, queues), and the introduction to computer science class that every body had to take (logic, print "Hello world!\n").

    It's really basic stuff. You can get away with appalling inefficiencies in code as long as it does what it's supposed to do. But far more important is knowing for example, the theory behind venom stacking, nuances of afflictions, the capabilities of each class, etc. Do you, for example, raze spend 1.5s to raze a shield and do 10% limb damage, or do you just spend 1.0s to raze the shield and then do 20% limb damage later? When is the best time to shoot off a paresis bolt? Where should loneliness go in mentis stack? What kind of optimizations and changes to your stat distribution do you need to make when pursuing a damage strat as opposed to something else? Does it take time to build up that experience? Yes. Does it also take time to build up the coding know how to implement some of these things? Yes, but arguably, not as much.

    Having a good technical ability without combat experience will put you solidly into the mid-tier. The inverse can keep you fighting amongst the best assuming you understand you will have a little more difficulty handling/using certain offensive/defensive routes and adjust your strategy accordingly.

    Also, programming an offense is a lot harder than loading in afflictions and coming up with a basic curing system. Dhuriv initial/followup/orders, Templar double weapon nonsense, mentis when you had to keep track of what you were whispering instead of having combat messages, rebounding/dodge, dealing with multilines or using states, yeah, no thanks.
  • Sorry but I have been laughing at people saying coding an offense is much easier then curing, Maybe a few month ago, or even a year or so ago.. but with the whole QUEUING all you really need to know now on how to code a curing system is a simple for k, v in pairs(herbs) do script..

    Offenses and knowining when to hit someone with certain affs like @Serrice‌ mentioned above is much harder..

    Sorry but its true when it comes to Mudlet Id happy tell someone the easiest way to make a curing system well the basics.. But as mentioned in another topic, no one asks stuff on KLL no more.. or even in the topics on here .. So only so much that some people can do to help others.
    Mudlet Bashing System for sale. Message if interested
  • @‌nalor
    There is a lot more to coding an offense than simply picking the next 1-3 affs from a list that the target doesn't have. That's like - a 4 line function (assuming you're already tracking the target's affs).

    Trying to code in the stuff Serrice touched on is a hell of a logic puzzle.
  • HavenHaven World Burner Flight School
    Draiman said:
    WTB meaningful conflict system.
    I think they call it RP but I could be wrong idk
    I get what you're saying, I do but RP can only go so far because it's an open ended thing typically. I ask for a system because it'll outline a clear, unquestionable start and end point. Clear goals. Clear successes and failures. But above all real and meaningful consequences. Flavor & mini-games are all well and good but ya still need the meat. The main course. Whatever you wanna call it. Aetolia has always excelled at providing distractions and ya know side content but over the years it has felt that the actual game itself was stripped away piece by piece until only the inconsequential side stuff was left. I firmly believe that implementing a solid main conflict engine into the game again alongside a competitive basic curing system would fix a lot of these issues. Give Aetolia back some of its meat, bone and all. Take what I say with a grain of salt though. (This is not to say no one upstairs isn't aware or isn't working on these issues. No idea what's happening behind the scenes or what they're working on. Just saying that's my take on the game as is and it's overall trend.)
    ¤ Si vis pacem, para bellum. ¤
    Someone powerful says, "We're going to have to delete you."
  • AshmerAshmer Barefoot Adventurer Life
    @Nalor is saying that offenses are much harder to code than curing - that curing is just a pick-a-next-aff-off-the-priority thing.

    Honestly, and @Lim can attest to this, we're moving into a meta where the quality of your curing is really important, and it'll take more than a four-line function to cure intelligently versus a lot of what people are capable of putting out. But that's a separate issue.

    The important thing about coding an offense is to start small and build out from there. Coding knowledge isn't helpful so much as system knowledge, like @Serrice pointed out. For example, you first build a function to parse a table and check it against the target's afflictions and pick two (or three) afflictions they don't have.

    For some classes, like Templar and Syssin, that's almost everything you need for like dsk/dstab. Two afflictions on a priority, and go.

    Now, let's say you're Sentinel. Now you need to define your afflictions by what can be done in the first attack and what can be done in the second attack, so you work that in to your existing ipairs() functions. Great, that's done. Now you need to get the engine to recognize the attack names, so each affliction entry in the main table gets an atk = { sentinel = "dhuriv heartbreaker" } type entry, so that in your kill_them_so_unicorns_dead() function it goes like send(lib[tmp.aff_one].atk[class] .. " " ..

    As an example. It's a slow process at first, but once you've built the infrastructure you can tweak it very very easily. Like right now, I've built a basic set of switches and manipulations into my offense infrastructure that I can do 99% of the things I'll ever want to do to a priority list almost on the fly.

    Anyway, at some point I'll get around to writing a tutorial for it. Once you understand ipairs(), tables, and basic if statements you're golden. The rest is as @Lim said; learning actual Aetolian mechanics and slowly (I mean like maybe 15-20 minutes out of the time you spend playing) tweaking and adjusting your stuff.

    Granted, this is if you didn't code your whole system from scratch and you're building offenses for every class in the game. This is like you've got Entropy, or Oasis or Tripwire or Mayhem or whatever you have and you're building something onto it.

    the way she tells me I'm hers and she is mine

    open hand or closed fist would be fine

    blood as rare and sweet as cherry wine

  • Draiman said:

    I would gladly do that if I knew what exactly people needed help with or where they were. I'm not sure what you run into but all I ever see is "it's hard". What's hard? What exactly do you not understand? Some of it, most of it, none of it?

    Mine would be, 'This is what I do, do you have a better suggestion?"

    That kind of request is intimidating, understandably.
    I mean, you know, an amount.

  • LimLim
    edited January 2015
    We can't compare apples to oranges; don't compare simplistic curing to complex offences. Yes, it is easy to come up with a basic curing priority list, where you cure one affliction above the other. It is also just as possible to create a basic offence script, where you afflict one affliction after the other. Each can be linear if you want, but the end result is that you become rigid, and won't be able to compete at higher levels. I don't agree at all that offence and curing are linear, where there is a fixed and easy set of answers, where the only differentiator is coding ability. That's only true at the basic level.

    Combat theory is harder than coding. This is what Serrice means when she describes theory underlying the code. I echo what she says about getting away with a lot of coding inefficiencies. I actually found that it's much easier to use sets of if-then commands to code an offence, rather than using complex tables that reference and check against one another. If you compare my scripts with Trager or Edain, you'll find that I write hundreds of lines more. It is primitive. I personally feel it is more flexible because even though it is long and tedious, it reads more like English.

    Define your first attack. Define your second attack, ensuring it doesn't clash with your first attack. Define your third attack, ensuring it doesn't clash with your first and second attack. Compile. Send.

    It is harder to come up with good curing than a good offence, but both are equally important. A good offence requires mostly an intimate knowledge of the class you're using at the time; a good curing system requires intimate knowledge of all the different classes you potentially face and how they work. When I said earlier that an offence is easier to code, I actually just meant that an offence has fewer moving parts. For curing, you need to have data tables, and incorporate 254 afflictions and their effects. For an offence, you just need to know the afflictions of your own class and how to deliver them.

    The exception might be Shaman, though. Because of the strong passives/active random cures, there is less of a need to think about what aff to cure before the next. Just cure when they get too many/you pick up a crucial affliction that needs to be shrugged off.
  • MoireanMoirean Chairmander Portland
    You misunderstand. The "linear" comment is about curing. In Aetolia, end of the day, it's linear. X thing cures Y affliction, and Z affliction cures predictably before Y. Now that this is all non-randomized and easily tracked via discernment, we've entered the age of the AI.

    Essentially the discussion you are having boils down to the nuances to the current combat system we have, but I, at least (and perhaps others) am saying that it's this system that I dislike and don't find super engaging. Combat didn't used to be all about curing priority and precise affliction delivery, with a hair-thin margin of error. That's why we have AI and why systems are as mandatory as they are. Making the coding aspect seem more friendly isn't going to change the fact that some of us just don't want to sit and code - we used to be able to slap together some stuff and fight on the fly and try out a range of tactics. Part of this was, yes, because coding in general was more crude. But there were also a wider range of tactics available. Aetolia's tactics never were as exciting as some games (Avalon's PK used to be incredible), but there definitely used to be more of them.

    End of the day, the game is what admin want it to be, so I'm not saying "The current PK game is wrong or bad" but rather just expressing why I am not engaged, since the question was raised, and I used to PK quite a lot. A lot of people seem to be getting hung up on "coding is hard" when it's not really about that. It's about the fact that coding has become mandatory, due to shifts in combat design. I can code fine, but even when I invest the time to do it, it's just not as fun to PK anymore.
  • Oops - I apparently read the opposite of what Nalor meant, when I read his post.
    Sorry @nalor

  • edited January 2015
    Zsadist said:

    Lifer: Top: Valingar, Dato (sometimes), Benedicto, Trager, Rashar, Conner, Aishia (rare fighter), Edain
    Mid: Jami (sometimes), Cronides (sometimes)
    Low: Kendri (need to start 1v1ing :))

    Darkie: Top: Ezalor (sometimes), Lim, Rammus, Ashmer, Ilyon (when he fights)
    Mid: Riluo, Zsadist, Yarel (sometimes), Draiman, Daegon

    Because @Aishia skerrs me a little (not) and because she won't let it go and because she asked nicely.... I'll amend my statement previous statement and added in a few names and where I think they stand.
    (Oasis): Benedicto says, "There was like 0.5 seconds between "Oh hey, they're in area. That was quick." and "OMFG THEY'RE IN THE AREA STAHP STAHP!""

  • AishiaAishia Queen Bee
    I never asked!!! But yes I like being on lists so I will let it pass.
  • Zsadist said:

    Low: Kendri (need to start 1v1ing :))

    I can't for the life of me figure out how to get anywhere 1v1, trying to sneak in faster then someone's salve balance doesn't seem to work. (for me)

    Sparring against someone 35% of my might and like level 80, I just end of bleeding them to death with jugular.

  • IshinIshin Retired Lurker Virginia
    edited January 2015
    Kendri said:

    Zsadist said:

    Low: Kendri (need to start 1v1ing :))

    I can't for the life of me figure out how to get anywhere 1v1, trying to sneak in faster then someone's salve balance doesn't seem to work. (for me)

    Sparring against someone 35% of my might and like level 80, I just end of bleeding them to death with jugular.

    Lycan is actually really tough. Unlike monk, who mostly loses out on damage and a little resto-pressure, lycans miss one attack/get it parried and it's like fffff. Usually if you're rolling your attacks right, you'll get ahead eventually, especially if you're running the proper howls.

    Edit: Something to consider, too - don't mangle on the first restore/pre-restore. Use the opportunity to break more limbs and add more salve pressure, -then- capitalize on it.
    Tell me and I forget, teach me and
    I remember, involve me and I
    -Benjamin Franklin
  • SerriceSerrice the Black Fox
  • TragerTrager Raiding your underwear drawer.
    Is this rage thread? I think this rage thread rite?
    Indoran'i is back baby. It's go-... Oh.

  • Trager said:

    Is this rage thread? I think this rage thread rite?

    No, this is not intended to be a rage thread. Discussion, yes. Just raging, no. Just want to make sure to point that out for others. It was simply split off of the rage thread so people had a place for constructive discussion concerning something that was in the main rage thread.
  • TragerTrager Raiding your underwear drawer.
    @Dristin: I realized that, actually. That was me being facetious.
    Indoran'i is back baby. It's go-... Oh.

  • Trager said:

    @Dristin: I realized that, actually. That was me being facetious.

    Works for me - but you NEVER KNOW.
Sign In or Register to comment.