Howdy, Stranger!
Categories
- 6.2K All Categories
- 3.1K Everything Achaea
- 1.5K North of Thera
- 26 Archives of the Terraformer
- 257 The Matsuhama Arena
- 885 The Golden Dais of Creation
- 299 The Scarlattan Theatre
- 149 The Blank Canvas
- 2K Getting Help
- 412 General Questions
- 258 Quick Class Questions
- 1.3K Tech Support
- 313 Client Help
- 486 Curing Systems and Scripts
- 841 Off-Topic
- 255 The Wander Inn
- 586 The Universal Membrane
- 298 Class Discussions
- 298 Individual Class Sections
- 20 Alchemist
- 9 Apostate
- 30 Blademaster
- 9 Depthswalker
- 14 Druid
- 4 Infernal
- 20 Jester
- 19 Magi
- 34 Monk
- 11 Occultist
- 8 Paladin
- 7 Priest
- 29 Runewarden
- 18 Sentinel
- 26 Serpent
- 20 Shaman
- 9 Sylvan
Comments
Just as a small note: it's already rather easy to "abuse" server-side curing functionalities to illusion-proof a client-side system, by making use of the CURING PREDICT command, which effectively tells you if you have an affliction or not (unless the affliction was given in a masked form).
→My Mudlet Scripts
So what you're saying is that I could do CURING PREDICT affliction x 25ish for every affliction, then gag the output everytime I get afflicted, and it'd be the same thing as them giving us a gmcp output.
That sounds like a pretty glaring loophole that should either be solved by changing the curing predict feedback message, or just giving us the gmcp thing.
I'd hardly call it abuse at this point, since the serpent class was effectively overhauled to balance the "loss" of illusion. That's a really neat trick though.
@Santar no, you only have to "predict" afflictions that you are hit with (real or illusioned). It wouldn't work on any type of masked affliction, so there'd be no point in "predicting" afflictions you haven't seen being hit with. You also can't "re-predict" an affliction until it has been determined that you don't have it (via diagnose or a blank herb being eaten). Thus, if you spammed it, it wouldn't really work like you're describing. It'd have to basically eat one of each herb and apply a salve to every body part, etc, before it'd be ready for another "use".
It does kindof give us the GMCP message we've all been asking for though. More on this tomorrow after I code it in
I didn't say it did.
What I said was that it replicated a GMCP known afflictions output. Which, it does. That's something that should be rectified
Curing disabled.
You sink your fangs into yourself, injecting just the proper amount of curare.
Paralysis Gained!+
There is no need to predict that affliction - you know you have it already.
Technically, I guess so, but I was thinking more of using it as a basic illusion check. I.e. you see a paralysis line, have your system send "curing predict paralysis" and see based on the result if it was real. Of course, you'd still suffer a time loss from the additional check, but it wouldn't affect people with a very good ping all too much.
→My Mudlet Scripts
With server-side curing disabled, this would essentially mean that you'd only get one shot at using this until you diagnosed to "reset" your "known cures" list which you filled up with incorrect predictions.
The second use would just give you 25 of this message: You have already predicted that you have that affliction.
Either way, regardless of what people are using it for, it should be fixed. Either obfuscate the message or just give us the GMCP afflictions.
Nope, you can unpredict the afflictions as soon as you predict them.
Oh, that's fun. Let the spam begin!
1/2 of your explanation is taking illusions into account. If illusions are to be removed from the game, then nothing you just said would be valid.
If the current server-side latency is 125ms (250ms rtt), then my client perceives it as ~7x slower than my average latency of 30ms.
People with bad ping have an incentive to switch to server-side curing, but are still at a disadvantage if they want to benefit from it for anything beyond 'basic' or 'average' curing capability (because they still need 100's of affliction triggers and supporting logic).
People with good ping would have the same emulated latency with the obvious difference being that their supporting client-side code will be able to react faster than a high-pinger's would. That would essentially negate the purpose of having server-side curing at all because it does uneven the playing field slightly. But what is the difference between this and pre-server-side curing when a low pinger fights a high pinger? The high pinger was already at a disadvantage.
That being said, putting known afflictions in GMCP would allow client-side scripts to react at the same latency of server-side curing regardless of their ping, thus evening the reaction times between low- and high-pingers. Nothing is going to prevent low-pingers from gaining an edge by using triggers instead if they wish put in the effort to keep the lines up to date.
As a player fortunate enough to have great ping, I would switch to server-side curing and accept the additional latency if it meant my curing was on a somewhat even level with those of higher pings because it's not fun for either person when there is a big difference in latency. Being lol-illusion-proof isn't even on my list of incentives for switching.
Edit: All of this kind of made me question the emulated latency in general. If it were able to scale based on average latency of each client, then yes... things would definitely be even.
If the server-side curing delay was a static 50ms, and we had a gmcp/hard-coded output, all of these problems would be solved.
Best part is: They're both super easy to implement!
Not something we're looking at changing at the moment. If your natural ping is faster, and you're comfortable using a client-side system, use a client-side system. If you you don't, then don't - it's a series of personal tradeoffs.
Unless it's rare for systems (SVO, Omni, private systems) to include that. That was one of the first things I built in mine though. :x
We already provide means to check the status of what afflictions you have - DIAGNOSE.
Maybe the additional gmcp information is too taxing on the sever? Make it a bitfield then.
That's not quite correct. There's no need to reset your list. If you use CURING PREDICT and have the affliction, you get the line "There is no need to predict that affliction - you know you have it already." regardless of whether you already predicted it before or not. You only get "You have already predicted that you have that affliction." when you have predicted it AND you don't actually have it.
→My Mudlet Scripts
There's still use for illusions for rp and events. As well as a few illusions that make you think that a JITB or a Death tarot or monk deliverance or whatever is coming when it isn't. Tumble illusions, there's a whole lot more. It just won't be focussed on curing system breaking anymore.
Just want to say this is a pretty ridiculous statement. I have no idea how gmcp works or even what it is. I'm twice the combatant you are, and I still use diagnose cause it's available. AND I can make simple highlights off of it to better see it.
Every true newbie I meet in this game has little to know programming knowledge. I think you're assuming too much on how necessary this is.
In short, shut up and diagnose.
I think @Nim is referring to pre-Physiology diagnose, which is like a 4 second balance or something ridiculous.
Without trans survival, it is stupid slow. I forget where they've moved the upgrade to, so maybe it's super early now, but I know from playing an alt that the slowdown is still there.
How do you measure combatants? If its by knowledge, unless I'm mistaken, I have you beat 2-0. I know how GMCP works fairly well, AND I know about newbie diagnosing being slow. Also, who even cares who the better combatant is when a primary target audience is combat newbies?
ETA: If the aff tracker's built into HTML5 like other GMCP things are, newbies wouldn't even need programming skills to use it. That was my intent and hope, but I am just as OK with a prompt option.
No idea where you're getting 2-0. Unless you're talking about when I was letting you test stuff on me because you were complaining about not being to kill people. Now if you want to go back further we can bring up the track recorded of me destroying you back when I wasn't very good either. And I'm not even gonna get into combat knowledge with you after watching stumble around as minister of war knowing barely any of the other classes skills.
If I remember right (been a long time) you get Physiology at like 100ish lessons in the skill. Give or take like 50. It comes before tumble and you shouldn't be fighting without tumble or you'll pretty much die to everyone.
I apologize for going Ernam on you, but a lot of your posts just always jab one of my nerves. I have no idea why, and I'm already having a bad day so yeah, my bad.
The only things I have complained about are veils and flimsy roleplaying, the latter because I am a roleplayer before anything else and the former because #deleteveils2014thesaxaphonesolotheminiseries. I keep the latter to myself since I recognise not everyone cares about roleplaying as much as I do, and the former I don't because #deleteveils2014thepointandclickadventuregame.
Also what, exactly, is wrong with a newbie fighting before they meet some expected set of abilities? That reasoning is dumb because it's easy to include stuff like trans avoidance, a lv3 dirk/band, the eq. reducing thingy (ace combatant right here folks), trans miniskill resistances, dragon, lv3 con bonus, wings, buckawns, a veil, an extra veil just to troll @Nim, etc.
I say pvp right from level bloody five, if you're even remotely interested. You'll learn a lot, and transing your first skill to get that instakill or whatever will be that much sweeter, and you'll have fun with other people while doing it, too. Probably should stay in the arena but whatever works works~
as one would expect from someone with my enormous capacity for thoughtful maturity, I blame @Wessux entirely. I crunched the numbers and found none of it to be my fault. I remain amazing. :3
I think everyone including IRE is missing the point here. We're not asking for balanceless diagnose. We're asking for server-side curing to show us known afflictions via GMCP so:
1.) the supporting client-side code doesn't have to maintain 100's of triggers and supporting logic regarding more complex curing scenarios.
2.) even "newbie combatants" would benefit from this once the hard work is done by the more experienced coders.
Diagnose would still have to be used as intended to discover masked/unknown afflictions/things that might occur during blackout/etc.
Without adding it to GMCP, it could just be made to send server-side echos of "You have gained the paralysis affliction" or "Your paralysis has been cured" along with the respective lines.