Thanks Sena, that gives me motivation to try for something better!
I'm trying to figure out how to get that +2 in one and +1 in the other but it's proving to be a bit difficult.
And I love too Be still, my indelible friend That love soon might end You are unbreaking And be known in its aching Though quaking Shown in this shaking Though crazy Lately of my wasteland, baby That's just wasteland, baby
Actually, let me add a question onto my previous, because I noticed something and I think it might be a bug, but I'm not sure.
So base stats for scalemail is 28/25. Here are two sets I did, same exact descriptors for both, when weaponprobed:
It offers the following defences:
Physical cutting: 29%
Physical blunt: 26%
It is exceptionally well crafted, and offers a very slight bonus to cutting defence and a very
slight bonus to blunt defence.
An exquisite suit of western scale mail has no venoms or magical effects on it.
Since these are both +1, it makes sense to think very slight is then +1. But then we look at the second set...
It offers the following defences:
Physical cutting: 29%
Physical blunt: 26%
It is exceptionally well crafted, and offers a slight bonus to cutting defence and a very slight
bonus to blunt defence.
An exquisite suit of western scale mail has no venoms or magical effects on it.
So the cutting on the second has a 'better' bonus, but it has the same exact stats.
@Makarios, is this a bug, or just overly ambiguous language? Should I bug it in-game?
Edit: I realize a bit belatedly these are %s (whoops) so maybe the jump from very slight to slight isn't physically seen, but is still present. Is that maybe the case instead?
And I love too Be still, my indelible friend That love soon might end You are unbreaking And be known in its aching Though quaking Shown in this shaking Though crazy Lately of my wasteland, baby That's just wasteland, baby
I think it's just a result of the displayed stats being different from the true, behind-the-scenes stats.
Base scale stats are 50/45, multiplied by 4/7 for the displayed stats of 28/25. With +1 to each, that's 51/46, reduced to 29/26. Another +1 to cutting for a total of 52 still reduces to 29.
Man I hate how armour stats have become that vague, but okay, that does make sense. It's probably safe to assume that slight is indeed +2 then, and everything is how it should be (but feel free to confirm if you catch this, Makarios). You're a star, Sena!
And I love too Be still, my indelible friend That love soon might end You are unbreaking And be known in its aching Though quaking Shown in this shaking Though crazy Lately of my wasteland, baby That's just wasteland, baby
@Skye can correct me if I'm wrong here, but I believe the cleaver way out-performs the mill in terms of usefulness, as it just produces extra reagents with no fuss, where with the mill you have to mill each ink individually to really take advantage of the bonus.
And I love too Be still, my indelible friend That love soon might end You are unbreaking And be known in its aching Though quaking Shown in this shaking Though crazy Lately of my wasteland, baby That's just wasteland, baby
@Skye can correct me if I'm wrong here, but I believe the cleaver way out-performs the mill in terms of usefulness, as it just produces extra reagents with no fuss, where with the mill you have to mill each ink individually to really take advantage of the bonus.
That was my assumption since it also boosts the none-meat things.
As far as I know, it isn't. You might try emailing artefacts@achaea.com (not sure that's the best email to use, but it seems more appropriate than the others; maybe customisations instead?) and working something out, if you're willing to spend a lot of credits on it. You can often get custom, not-normally-available things like that (as long as they don't give any real advantage) for enough credits, people have added things like special exits and fireplaces (before they were available as a room upgrade) to their house before.
I thought the talisman training dummies worked differently than ordinary resetting, having a specific timer that starts when they're dropped. So it may not be possible to change at all (or may not be allowed if it is).
I'm one of those people that has issues with Mudlet dc'ing after a few minutes if I don't do anything, regardless of how high my timeout might be. I've been doing the following every minute to avoid the timeout:
sendGMCP("Core.KeepAlive")
send("", false)
but it ends up preventing me from naturally timing out as well.
Is it the gmcp or the blank send that is preventing the natural timeout? Does anyone know a way to make sure the connection is still in use without making Achaea think I'm active and reset my IG timeout?
@Vessil What you describe is a very common problem people have with Mudlet. It's not normally Achaea or Mudlet but a router setting. If you're not entering commands to Mudlet after a certain period of time many routers will declare the connection idle and close it in order to preserve bandwidth efficiency. This can be changed in your router's settings.
@Vessil What you describe is a very common problem people have with Mudlet. It's not normally Achaea or Mudlet but a router setting. If you're not entering commands to Mudlet after a certain period of time many routers will declare the connection idle and close it in order to preserve bandwidth efficiency. This can be changed in your router's settings.
I get this all the time when I'm wireless.. could never figure it out.. I'll look into router settings now
I might dig around and see if I can find that particular setting then. Although, I don't think I've tested to see if I have the same problem when routing Mudlet through Mudbot, so I'll see if that fixes it by itself.
I have that dc'ing issue too and I don't use Mudlet. I'll look at router settings and report back.
Yeah it's not exclusive to mudlet. It happens to me on mush and other clients I've used in the past.
I get around it by just sending the core.keepalive(sic) on a timer, mine is set to 15 seconds which I found keeps my connection "100" without me feeling greedy about looping commands to the server. That will keep my connection alive and reactive for...ever, really (as has been mentioned already).
That also works well, for me, with setting my timeout to 3 minutes. If something happens to my machine or connection or power or whatever, it brings a nice piece of mind knowing I'm not sitting there completely vulnerable and unable to respond for very long.
I feel like that's at least part of its intended purpose. If not, it sure kicks ass at it.
That router stuff is interesting though and I've heard it mentioned in the past. Probably time for me to just set it, even though I don't really have this problem anymore.
Is there any information on how long, exactly, an Achaean day is and how the day is divided up and each phase (morning, dawn, early afternoon, midday, etc.) take?
Comments
I'm trying to figure out how to get that +2 in one and +1 in the other but it's proving to be a bit difficult.
That love soon might end You are unbreaking
And be known in its aching Though quaking
Shown in this shaking Though crazy
Lately of my wasteland, baby That's just wasteland, baby
So base stats for scalemail is 28/25. Here are two sets I did, same exact descriptors for both, when weaponprobed:
Since these are both +1, it makes sense to think very slight is then +1. But then we look at the second set...
So the cutting on the second has a 'better' bonus, but it has the same exact stats.
@Makarios, is this a bug, or just overly ambiguous language? Should I bug it in-game?
Edit: I realize a bit belatedly these are %s (whoops) so maybe the jump from very slight to slight isn't physically seen, but is still present. Is that maybe the case instead?
That love soon might end You are unbreaking
And be known in its aching Though quaking
Shown in this shaking Though crazy
Lately of my wasteland, baby That's just wasteland, baby
Base scale stats are 50/45, multiplied by 4/7 for the displayed stats of 28/25. With +1 to each, that's 51/46, reduced to 29/26. Another +1 to cutting for a total of 52 still reduces to 29.
That love soon might end You are unbreaking
And be known in its aching Though quaking
Shown in this shaking Though crazy
Lately of my wasteland, baby That's just wasteland, baby
got gud
That love soon might end You are unbreaking
And be known in its aching Though quaking
Shown in this shaking Though crazy
Lately of my wasteland, baby That's just wasteland, baby
Results of disembowel testing | Knight limb counter | GMCP AB files
got gud
got gud
Anaidiana did that with our family ship, it has an artie ax that resets into the cabin if it leaves the ship so... yeah.
sendGMCP("Core.KeepAlive")
send("", false)
but it ends up preventing me from naturally timing out as well.
Is it the gmcp or the blank send that is preventing the natural timeout? Does anyone know a way to make sure the connection is still in use without making Achaea think I'm active and reset my IG timeout?
I'm thinking Serpent if we don't count the Dexterity rework / Monk if we do.
Yeah it's not exclusive to mudlet. It happens to me on mush and other clients I've used in the past.
I get around it by just sending the core.keepalive(sic) on a timer, mine is set to 15 seconds which I found keeps my connection "100" without me feeling greedy about looping commands to the server. That will keep my connection alive and reactive for...ever, really (as has been mentioned already).
That also works well, for me, with setting my timeout to 3 minutes. If something happens to my machine or connection or power or whatever, it brings a nice piece of mind knowing I'm not sitting there completely vulnerable and unable to respond for very long.
I feel like that's at least part of its intended purpose. If not, it sure kicks ass at it.
That router stuff is interesting though and I've heard it mentioned in the past. Probably time for me to just set it, even though I don't really have this problem anymore.
Currently available: Abs, Cnote, Keepalive, Lootpet, Mapmod