Additional clarity around scripting requirements
One of the things I really liked about Achaea was how much scripting was required. Now before everyone lynches me, please hear me out. 
Early in Achaea, the minimal viable product to be effective in PVP was an immense undertaking and players who adopted Vadi's system (a curing system that was once available for purchase, now free) had a significant advantage against those who didn't have it. Now that server-side curing has been fully implemented this is much less of a concern, though still quite complex.
The fun part was the strategy around all of these curing elements. For example, if I know the Blademaster had my legs and arms prepped, and broke both of my arms, I could apply to my legs preemptively to minimize potential prone time. This is a risk that can open me up to serious counterplay, but against the typical opponent or in the arena it was a devastating defense manoeuvre. This is a piece that was not built in to the default curing system. This only one of many examples, and part of the game was understanding how different people cure in different situations, and then abusing those openings.
My concern around the comments that "Less scripting will be required and wetwiring will handle everything!" is because there was a lot of room for creativity within both the curing and offensive tools we were given as players.
With the above in mind, I suppose my question could be summed up to the following:
Note for those not familiar with Blademaster PVP: The most common Blademaster win is by preparing various sets of of limbs (head/torso/arms/legs) to one strike from breaking, then break arms/head+torso to force a curing application that had a long cooldown, then prone them at the same time as breaking their legs while this cooldown was in effect to keep them prone, impale them, cause lots of bleed by twisting the sword in their gut, and finally insta-kill (the instant kill required high bleed). If I applied to my legs the moment my arms were broken, and the blademaster followed up with a leg break after breaking arms, my cooldown would've been used to get out of the prone instead of curing arms. The broken arms could then be taken advantage of by a skilled Blademaster by transitioning in to a different win condition.
Early in Achaea, the minimal viable product to be effective in PVP was an immense undertaking and players who adopted Vadi's system (a curing system that was once available for purchase, now free) had a significant advantage against those who didn't have it. Now that server-side curing has been fully implemented this is much less of a concern, though still quite complex.
The fun part was the strategy around all of these curing elements. For example, if I know the Blademaster had my legs and arms prepped, and broke both of my arms, I could apply to my legs preemptively to minimize potential prone time. This is a risk that can open me up to serious counterplay, but against the typical opponent or in the arena it was a devastating defense manoeuvre. This is a piece that was not built in to the default curing system. This only one of many examples, and part of the game was understanding how different people cure in different situations, and then abusing those openings.
My concern around the comments that "Less scripting will be required and wetwiring will handle everything!" is because there was a lot of room for creativity within both the curing and offensive tools we were given as players.
With the above in mind, I suppose my question could be summed up to the following:
- Will there be a significant amount room for creativity in regards to PVP strategy?
Note for those not familiar with Blademaster PVP: The most common Blademaster win is by preparing various sets of of limbs (head/torso/arms/legs) to one strike from breaking, then break arms/head+torso to force a curing application that had a long cooldown, then prone them at the same time as breaking their legs while this cooldown was in effect to keep them prone, impale them, cause lots of bleed by twisting the sword in their gut, and finally insta-kill (the instant kill required high bleed). If I applied to my legs the moment my arms were broken, and the blademaster followed up with a leg break after breaking arms, my cooldown would've been used to get out of the prone instead of curing arms. The broken arms could then be taken advantage of by a skilled Blademaster by transitioning in to a different win condition.
0
Comments
I've got no clue how complex the offensive side will be for PvP, but even on the more simple classes in other games there was plenty of room for scripting on that side of things to help give you the best information.
My hope is that even if we have wetwiring, we have the ability to tweak how it does what it does.
(Scatterhome): You say, "Which by my calculations, it's your turn to pay."
(Scatterhome): Brantar says, "That's what my calculations have come to."
(Scatterhome): Paavo says, "My math adds up to that, yeah."
(Scatterhome): Cal says, "Bastards."
Others, myself included, have bad memories attached to the scripting systems. I was strongly discouraged as the entry to PvP required an insane amount of out-of-the-game activities, related more to mastering LUA/JavaScript than mastering the game mechanics.
I've been poking around Discord and this forum for a while now, and I do hope that Starmourn will be able to satisfy both of those needs: it will reward ingenuity and effort put into mastering the game, but will not rely on programming skills as a base requirement to even enter competitive PvP.
https://countingdownto.com/?c=2341194
MUD gaming in general does not have enough of a player base at this point to make yet another difficult to play effectively game. We need to move in a direction that is friendly enough that we can pull in players that wouldn't normally enjoy a game like this. I've tried to bring in dozens of friends and acquaintances to MUDing over the last decade I've played and very few have stayed because of the entry requirements.
Besides the fact that in order to be fully equipped with the skills you need to survive in top-tier place you have to put money into the game, you also had to pay someone to be able to cure yourself effectively. That's insane. For most people this is hobby not something they want to sink hours of work into just to play. I get that some people like the challenge but that's tiny percentage of the folks that would enjoy the game if it weren't so damn complex.
Nailed it 100%! I'm not asking for the scripting elements to be hard, I also agree that the barrier to entry is immense for the uninitiated.
I'm asking for the depth and creativity to be available. "Easy to learn but hard to master" is what I would hope for, and if the devs are able to strike that balance they'll have a winning product in my eyes.
If everyone is a top tier combatant in a simplistic PVP system, then no one is, and the PVP is why I play.
And so, clearly, there can never be a system in which automation can't provide some advantage unless it's literally even more basic than tic-tac-toe. Rock-paper-scissors? Good automated systems (with the benefit of data from lots of past games played against humans) beat people even there. There's no point in trying to make a MUD where automation -can't- provide an advantage, unless the entire thing relies on free-form conversation between players or something similar.
A good compromise that also works for people like @Minion or @Quean (I'm part of this category too) is to still have that high skill ceiling, but have low barriers of entry. With concepts like wetwiring being a core part of the game's design, I am optimistic about Starmourn hitting that sweet spot. The most important part, then, is having enough people actively participating in lowbie PvP of this kind. We might not have a great chance against somebody who has spent hours perfecting their systems, but we will be competent enough to have good, exciting fights against each other.
Essentially, each character would have a sheet of skills. You'd have attributes, then the skills beneath. I believe it was a D20 system. So if my attribute, strength, was 3D+1, all related skills would start at 3D+1 (like a kick, for instance). It was significantly more costly to raise attributes versus skills, but it could be a good strategy depending on your goals.
Anyway, so you'd get into a fight. I'd roll for my kick (3D+1). That would roll to a particular channel and show the output only to me (the actual die value, but others in the area would see the level) and judges (volunteers who would judge combat situations). I'd get the roll return, which would break it up by number into levels (Very easy, Easy, Normal, Hard, Very Hard, etc.). Based on that, I'd then RP taking a kick.
The next person might roll for their attribute of perception. Based on that, they either see the kick or not. Then they can roll for block, or evade, or parry, all depending on their skills, strategy, and items (they'd need a sword equipped for parry, as an example). So let's say they block, that means it will hit (versus an evade, which would seek to avoid it all together).
So they roll block and it's higher than my kick, meaning, successful block. But let's say it's lower and my kick connects past the block. Then I get to roll my strength attribute to determine the force of the kick. They do the same to counter the force of my kick, taking into account any armor or mitigating factors, and the damage is then determined.
It's a MUSH, so we didn't have HP per se, but if they RPed kicking me in the knee and it connects with a VERY HARD strength roll, and the reciprocating strength roll was a weak, you can basically assume that person is going down and likely has some kind of injury.
I'm sure some aspects of this are already incorporated into the combat system for this MUD, but I really miss the RP elements of fighting where it wasn't just emotes and outputs scrolling by in a fraction of a second, where you're just wailing away until someone or something dies. I liked the story part where every experience was truly unique as you worked out the story with those present (using the judge as needed to arbitrate/mediate). It'd be fun to try and make a framework tight enough to where a judge would be almost unnecessary and the rest could be worked out as you go with other people.
Honestly, I think the majority of people that want to get into PVP in a MUD do not want to have to code. They'll put in the time and effort to learn how to manually build strategies and teach themselves muscle memory. Over the last decade I've played, I was able to do this with no coding ability and without any automation. I was not "top-tier" but I was effective where I wanted to be.
I don't understand how it is enjoyable to play a game by pushing one button and letting your computer do the rest. I get that it takes skill to code an offense but I just don't see how it's fun to play a game against people that way. Honestly, I think I represent the majority of people who play games in general. We play to challenge our own understanding of things and test the limits of our perception and skill. Feel free to play "push-one-button-to-win" games but realize you're going to get lonely real quick.
Also, being honest, the main reason I'd consider it personally is the overload of combat, I think I've seen comments about windows in the span of like... seconds, which does lead to stuff like macros that check the targets vitals and make you act based on that (like if you have a 50% health insta-kill, sending that command rather than an attack).
Oh also like... thinks that are dull/monotonous or crucial to get right will end up scripted, Lusternian examples being demesnes where you need to cast stuff at specific intervals for stuff to work right or like the Wiccans who have a large entourage that you can sync up with a relatively simple script which gives a slight edge in that you can make them all attack at once when you send the attack command. (Rather than ticking separately and you could be waiting a little while for the first tick.)
https://countingdownto.com/?c=2341194
Venom coating: basic aliases
The coding requirements to get into combat really aren't as bad as everyone says they are.
https://countingdownto.com/?c=2341194
I wouldn't be surprised if there had been something for Moondancers in Lusternia a few years back, mostly because the strat was something like... launch fae, throw these hexes x seconds after the first command to time them with the fae, at this point they should be stuck in sleep, start draining mana, toad, stomp, done. But that's mostly cause it's, in theory, just linking like two macros together.
I feel like the most common scripts would probably be auto-bashers and the separate chat-window one for non-nexus clients.
Note that I didn't know LUA when I started playing Achaea, some 8 years ago, but I wanted to learn it and got to a point where I can do anything I want with it. No classes, no daily coding drills, no other coding history. Just have to want to do it. I didn't even get in to combat until about 4 years ago.
To answer a question I saw somewhere; the fun part is tinkering, some people like pulling an engine apart to polish the ports and the carbs for that extra bit of oomph. Getting to that point requires intimate knowledge of whatever it is you're working on and the tools that you have at your disposal, and that's the fun part. You then get to see your machine push that through. Even things like creating a super cool GUI is a ton of work but so rewarding when it's done.
Doesn't mean I'm going to run around and autodestroy everyone, I'm not claiming to be the best at coding or PVP, but when people get frisky I get to whip out the infinity chancla.
If there is less benefit to automating everything, then it doesn't matter if some people still do it: you'll still have a fair chance at winning.
With combat speed is reduced to 3 second rounds and curing not being millisecond-dependant, you'll have time to choose your attacks and occasionally press one of the 5 keys for mending.
You'll still need some scripting, but it is hopefully mostly related to presenting information (modifying the prompt, gauges in the UI, highlighting important lines etc) . If combat rounds really are ~3s and opponent affliction tracking is not more accurate by script than by eye, then both types of player will be on even footing.
As someone who's used plenty of automation and scripting in the past, it always annoyed me when players would give up or refuse to fight someone because they had settings. If someone puts in the time and effort to improve their gameplay and have an advantage over other players, then more power to them. They studied their shit and are reaping the rewards.
"In all chaos there is a cosmos, in all disorder a secret order."
I don't think anyone expects to be able to run telnet.exe and compete; but being able to choose every attack I make with a keybind, and select which wetwiring mend to use, and when, with a keybind, while still competing on a level playing ground? That my ideal, but some of the IRE games require full automation (specifically the one I have invested the most into, of course
https://countingdownto.com/?c=2341194