Looking for more active discussion? Join our Discord at https://discord.gg/x2s7fY6
Best Of
Re: Announce post #3176: Aegis and PK
What spirit would never coordinate issues in a web.
Ever.
Ever.
Bulrok
6
Re: Announce post #3176: Aegis and PK
I think it's silly that this has to be brought to forums to get talked about. Decision was made, move on to the next thing please.Do not the forums exist to have a reasonable discussion? Isn't that why announce are cross-posted to the forums to begin with?
edit: I'm also slightly concerned with some of the logic that is being put forth in some of these "arguments" that are being made. They also seem silly.
Saidenn
5
Re: Announce post #3176: Aegis and PK
No, Nisavi, you don’t get to try and make me out in that light. Half of the people in this thread are already up in arms over yet ‘MORE PK RULES THAT ARE SET IN STONE, OMG ORGANIC ROLEPLAY’. I know, I can read it in the discord’s I belong to as well. Your way is just that: hard-coded stances that limit PK. All that’s been done here is an effort to keep an even playing field during something that amounts to nothing more than a track and field event.
They’re saying that you shouldn’t go and spread spikes across your opponents lane before the race. They’re saying that if you do, you don’t get the opportunity to get mad when they pick them off the ground. They’re saying that if anyone gets to get their shit rocked in revenge, it’s the person spreading the spikes before the race - not the guys picking up the traps.
Naos
8
Re: Announce post #3176: Aegis and PK
No, the easiest recourse is to know when you’re trying to ply an unfair advantage during a situation with clear and concise rules of engagement. It takes a touch more common sense, I know, but I have faith.
Naos
8
Re: Announce post #3176: Aegis and PK
HI MY NAME IS NAOS. I LIKE THIS CHANGE.
You should not be allowed to set yourself up in an advantageous way for a conflict that has STRICT lines of beginning and ending. You do not have the right to feel affronted when the opposing team in this event tries to nullify the already sleazy advantage you are trying to take. YOU SHOULDN’T GET TO CLAIM CAUSE OVER SOMETHING YOU STARTED.
You should not be allowed to set yourself up in an advantageous way for a conflict that has STRICT lines of beginning and ending. You do not have the right to feel affronted when the opposing team in this event tries to nullify the already sleazy advantage you are trying to take. YOU SHOULDN’T GET TO CLAIM CAUSE OVER SOMETHING YOU STARTED.
Naos
9
Re: Announce post #3176: Aegis and PK
This feels like another nail into the coffin of any kind of world conflict outside aura-sanctioned encounters. Aegis are unique, I agree with that point, but they are property and, as it stands, labyrinths on aegis exist as the primary method of forcing an encounter or controlling an encounter that Shadow has currently.
Even more, shadow cannot remove traps that can be set at any time along these same hunting areas. Are we now allowed to attack someone for hitting a trap they left because reasons, especially as we can't see them unless we're specifically looking for them? Will there be an ability to remove them or possibly attempt to remove them? Will that be considered a reason enough to defend while I am trying to remove those from the pathways? What of glyphs?
I can understand the frustration that may come with having an area prepped for an upcoming conflict, but prep is not unique to Aegis, and is not unique to Shadow either. I also feel that if you engage in an aggressive action, you accept the consequences that come with that action. Shrine defiling gives you a hefty aura that lasts after and leaves you open to PK, and you're allowed to set those up in areas and are used aggressively - will there be a limiter on that next, too?
I think this is going in the wrong direction and setting a terrible precedent. World conflict is already non-existent outside sanctioned events (foci, orrery, sect, vortex/fracture/HG), and this only limits it more. And if anything, it just creates a situation where it is now encouraged to bring an entire group to defend an aegis or attack an aegis, as once the aegis is down, it doesn't matter anyhow - you're off scot free.
Add in some removal options of Traps, please, or else this feels like a double-standard aimed specifically at labyrinth @Tiur.
Edit: As an additional note, this feels like it goes against the spirit of a single death not being issuable for the most part. A single act of aggression is answered with a single act of revenge if it can be completed in a reasonable time. I try to avoid hyperbole, but feels like a bit of a slippery slope heading toward PK lawyering.
Even more, shadow cannot remove traps that can be set at any time along these same hunting areas. Are we now allowed to attack someone for hitting a trap they left because reasons, especially as we can't see them unless we're specifically looking for them? Will there be an ability to remove them or possibly attempt to remove them? Will that be considered a reason enough to defend while I am trying to remove those from the pathways? What of glyphs?
I can understand the frustration that may come with having an area prepped for an upcoming conflict, but prep is not unique to Aegis, and is not unique to Shadow either. I also feel that if you engage in an aggressive action, you accept the consequences that come with that action. Shrine defiling gives you a hefty aura that lasts after and leaves you open to PK, and you're allowed to set those up in areas and are used aggressively - will there be a limiter on that next, too?
I think this is going in the wrong direction and setting a terrible precedent. World conflict is already non-existent outside sanctioned events (foci, orrery, sect, vortex/fracture/HG), and this only limits it more. And if anything, it just creates a situation where it is now encouraged to bring an entire group to defend an aegis or attack an aegis, as once the aegis is down, it doesn't matter anyhow - you're off scot free.
Add in some removal options of Traps, please, or else this feels like a double-standard aimed specifically at labyrinth @Tiur.
Edit: As an additional note, this feels like it goes against the spirit of a single death not being issuable for the most part. A single act of aggression is answered with a single act of revenge if it can be completed in a reasonable time. I try to avoid hyperbole, but feels like a bit of a slippery slope heading toward PK lawyering.
Saidenn
5
Re: Announce post #3176: Aegis and PK
They're meant to be sorta vague, because I hate enumerated PK rules. We have a small enough playerbase that we can take issues as they come and figure it out. We also expect players to be adults (I know, I know) and use basic common sense. I'm just not going to discuss hyperbolic attempts to drag 'hotspot' out to mean the whole world.
The word REVENGE is very specifically used here. Revenge is PK for something past tense. Showing up to defend the aegis you put down during someone's attempt to destroy it is not revenge, the act is still ongoing. If they use a group, and you bring a group, neat, it's a group fight. If you go find them hours after it's gone, no.
Essentially: The Aegis are not meant to passively sit there and generate you PK cause. The core to understand is that it's not you building something and it deserves to exist; it's that you are putting something like a preemptory attack out in the world and waiting. When it hits, YOU STARTED THE FIGHT.
If you weren't there to defend it, you don't get revenge for losing the fight you started. There is some leeway left for things like making trap rooms, or tricking people into them as active combat methods. Hence only really caring about hotspot locations. Essentially, I should approve every single issue where your Aegis hits someone you have no cause on.
Ask yourself "Do I have cause against X?" Because an aegis is like an attack on a loooooong timer.
In cases where no one is hit, or it's destroyed while you're gone, we're saying that to claim revenge (pk at a later date) it needs to either have been somewhere you have a reasonable reason to pk people over or somewhere you own and were protecting. Again, think of it like a delayed attack. It is unreasonable to think you deserve cause on someone later because you started a fight and they fought back. If it's at NoT, even if it doesn't hit the person who destroyed it, it's like you left an attack waiting to hit them at any time, it's silly to give you cause for them removing it.
The aegis is aggressive. Justify its aggression, not how people respond to it.
E:
I missed the bit about single deaths. That's meant to handle people putting up silly issues, death is not that big of a deal, whatever. But if someone treats it like "I get one free pk causeless kill on every player" I'll end up punishing you because the larger picture matters more than the time saving "don't waste our time" rules.
The word REVENGE is very specifically used here. Revenge is PK for something past tense. Showing up to defend the aegis you put down during someone's attempt to destroy it is not revenge, the act is still ongoing. If they use a group, and you bring a group, neat, it's a group fight. If you go find them hours after it's gone, no.
Essentially: The Aegis are not meant to passively sit there and generate you PK cause. The core to understand is that it's not you building something and it deserves to exist; it's that you are putting something like a preemptory attack out in the world and waiting. When it hits, YOU STARTED THE FIGHT.
If you weren't there to defend it, you don't get revenge for losing the fight you started. There is some leeway left for things like making trap rooms, or tricking people into them as active combat methods. Hence only really caring about hotspot locations. Essentially, I should approve every single issue where your Aegis hits someone you have no cause on.
Ask yourself "Do I have cause against X?" Because an aegis is like an attack on a loooooong timer.
In cases where no one is hit, or it's destroyed while you're gone, we're saying that to claim revenge (pk at a later date) it needs to either have been somewhere you have a reasonable reason to pk people over or somewhere you own and were protecting. Again, think of it like a delayed attack. It is unreasonable to think you deserve cause on someone later because you started a fight and they fought back. If it's at NoT, even if it doesn't hit the person who destroyed it, it's like you left an attack waiting to hit them at any time, it's silly to give you cause for them removing it.
The aegis is aggressive. Justify its aggression, not how people respond to it.
E:
I missed the bit about single deaths. That's meant to handle people putting up silly issues, death is not that big of a deal, whatever. But if someone treats it like "I get one free pk causeless kill on every player" I'll end up punishing you because the larger picture matters more than the time saving "don't waste our time" rules.
Tiur
9
Aetolia After Dark: A new, immersive Aetolia UI meant to make your game more exciting
Hello! One of my pet projects/hobbies is making GUIs in Mudlet, and a few weeks ago I started a project with one goal: make Mudlet as pretty as possible. Something I always hated about using mudclients over, say, Nexus (even way back in the day of javaclient) was how much better Nexus looked compared to even the most hardcore coded systems by the most awesome people that play the game. And there's just something about that harsh black background that I find unimersive. I loved how Nexus thematically fits the MUD you're playing. So I said "screw it" and set out to make a UI that would match Nexus toe-for-toe when it came to aesthetics and immersion-building, and what I got was Aetolia After Dark:
This system builds on some ideas @Lin gave me from his system, mainly the utilization of Pulse events, which are fairly central to the structure of this system. I also just straight-up stole his map code. I think it looks pretty good, if I do say so myself. Anyway, here's what you'll get:
Gold/Exp-per-hour dot/line graphs:
A character sheet:
TERMS OF USE:
You might have noticed that most of the assets are modifications from the video game Diablo. I did this without any legal concerns because I was just making it for myself, but now that I'm giving it to y'all, you probalby shouldn't be trying to profit from its distribution or you'll get destroyed legally. Otherwise, use is completely free. Modify at your own risk, I'm offering minimal support, if any. There's also a folder of fonts you'll want to install before running it.
THINGS TO BE AWARE OF:
At the very top there's a "GUI Options" script that's pretty small. This is something you'll want to take a look at upon opening, as it is how the WHO list is populated. I could have automated it, but that would've been a lot harder. In order to customized it to your character, you'll have to follow the instructions in the file. And if you have the death location relic for deathsight, there's an option to enable that in the deathsight window display. edit: lol of course because I added this last minute, it's slightly broken. If you want to turn it on, you have to navigate to Template ->GUI->Right Panel Stuff->deathsight and delete the "local" before "death_location". That should fix it.
READ THE README
You'll want to run "startup config" upon installation to get your configs right, and the system does require one (1) restart in order to make sure all the colors and fonts are working correctly.
I may update this UI with more features in the future (like clicky noises when buttons are clicked), but at the moment this is the release, bugs and all (though I've done my very best to make it as class/character agnostic as possible.) For the more visually-inclined, here's a video featuring some more of the features in action:
SPECIAL NOTES:
This system builds on some ideas @Lin gave me from his system, mainly the utilization of Pulse events, which are fairly central to the structure of this system. I also just straight-up stole his map code. I think it looks pretty good, if I do say so myself. Anyway, here's what you'll get:
- A fully-fuctional information display with hp, mana, willpower, endurance, and ylem reserves.
- dps, exp/hour, gold/hour, and commands-per-second display
- dynamic "who" list
- individualized comm channels that greatly reduce mistell risk
- a barely-useful inventory display
- something pretty to look at for once
- anything combat-related aside from a combat feed
- a defense list
- automated def-ups. I do have defups written for me, but it was well-outside the scope of this project for me to write dynamic defup code for every class
- target calling/following
- any autobashing
- The world's most efficient system. I'm a creative coder, but not the best. There's definitely things that could be optimized I'm sure.
Gold/Exp-per-hour dot/line graphs:
A character sheet:
TERMS OF USE:
You might have noticed that most of the assets are modifications from the video game Diablo. I did this without any legal concerns because I was just making it for myself, but now that I'm giving it to y'all, you probalby shouldn't be trying to profit from its distribution or you'll get destroyed legally. Otherwise, use is completely free. Modify at your own risk, I'm offering minimal support, if any. There's also a folder of fonts you'll want to install before running it.
THINGS TO BE AWARE OF:
At the very top there's a "GUI Options" script that's pretty small. This is something you'll want to take a look at upon opening, as it is how the WHO list is populated. I could have automated it, but that would've been a lot harder. In order to customized it to your character, you'll have to follow the instructions in the file. And if you have the death location relic for deathsight, there's an option to enable that in the deathsight window display. edit: lol of course because I added this last minute, it's slightly broken. If you want to turn it on, you have to navigate to Template ->GUI->Right Panel Stuff->deathsight and delete the "local" before "death_location". That should fix it.
READ THE README
You'll want to run "startup config" upon installation to get your configs right, and the system does require one (1) restart in order to make sure all the colors and fonts are working correctly.
I may update this UI with more features in the future (like clicky noises when buttons are clicked), but at the moment this is the release, bugs and all (though I've done my very best to make it as class/character agnostic as possible.) For the more visually-inclined, here's a video featuring some more of the features in action:
SPECIAL NOTES:
- You MUST have Mudlet 4.11.2 or higher installed for it to work. It uses several features exclusive to this version and higher. If you do not update Mudlet, it'll freak the heck out.
- the UI scales fairly well to most layout sizes, but will only really optimally work if your monitor dimension are at least 1650x750 if you hide the Main Toolbar. Also it's not been tested fullscreen on a 4k monitor, some of the borders may not like that.
Tetchta
17
Changelog post #1865: Audit addition + Revenant fixes
4/7/2021 at 6:12
Razmael, the Synthesist
Everyone
Audit addition + Revenant fixes
With these fixes, we no longer have any Revenant skill bugs filed in the system. If you know of a bug you don't see fixed here, please file a bug because it means nobody else already did.
Game additions:
- You can now AUDIT MAXHEALTH and AUDIT MAXMANA to see how those are being calculated.
Revenant fixes:
- Lurk now works.
- Duskosa does shadow damage now.
- Wasi correctly destroys rebounding auras now.
- Hemoclysm works now.
- Extirpate works now.
Revenant typo fixes:
- Fixed Congeal having an extra period after its newline.
- Fixed Phantasms showing messages to wrong person when used in conjunction with Shade.
- Fixed the AB files for Chirography/Manifestation missing the headers and lessons/learned field.
- Fixed Separate's messages.
- Fixed Riving Fell having a space before its ending period.
- Fixed Lawid's message showing numbers instead of names.
- Fixed Doyfo's message showing numbers instead of names.
- Fixed Owinta's message showing numbers instead of names.
- Fixed Jumpcut not having a witness message in some cases.
- Fixed Dirne's message uppercasing the weapon mid sentence.
- Fixed Retrieve's messages being around the wrong way.
- Updated several messages to use lowercase 's' for 'shadow', as we use uppercase to refer to the plane and lowercase for the actual element.
- Fixed the middle Eclipse message to show the target's name.
- Fixed some typos in Eclipse's messages and made some tweaks.
Templar fixes:
- Inline empowering works again.
Templar typo fixes:
- Defend was proccing the Riving version messages and has been fixed.
- Fixed Deliverance's messages being around the wrong way.
Both classes:
- Removed weapon charge colouring from the combat message (it was previously unintentionally affecting only half of the message).
I removed combat messages from some abilities that I noticed didn't originally have them, as this was an intentional design decision. We generally avoid putting combat messages on passive effects. Affected skills:
- Defend/Juxtapose
- Pestilence/Choke
- Purity/Claw
- Redemption/Symbiosis
I didn't go hunting too hard for these, so if there's other passive abilities within Templar/Revenants that now have combat messages attached to their passive effects and didn't before, please let me know.
Penned by my hand on Closday, the 13th of Midsummer, in the year 494 MA.
Razmael, the Synthesist
Everyone
Audit addition + Revenant fixes
With these fixes, we no longer have any Revenant skill bugs filed in the system. If you know of a bug you don't see fixed here, please file a bug because it means nobody else already did.
Game additions:
- You can now AUDIT MAXHEALTH and AUDIT MAXMANA to see how those are being calculated.
Revenant fixes:
- Lurk now works.
- Duskosa does shadow damage now.
- Wasi correctly destroys rebounding auras now.
- Hemoclysm works now.
- Extirpate works now.
Revenant typo fixes:
- Fixed Congeal having an extra period after its newline.
- Fixed Phantasms showing messages to wrong person when used in conjunction with Shade.
- Fixed the AB files for Chirography/Manifestation missing the headers and lessons/learned field.
- Fixed Separate's messages.
- Fixed Riving Fell having a space before its ending period.
- Fixed Lawid's message showing numbers instead of names.
- Fixed Doyfo's message showing numbers instead of names.
- Fixed Owinta's message showing numbers instead of names.
- Fixed Jumpcut not having a witness message in some cases.
- Fixed Dirne's message uppercasing the weapon mid sentence.
- Fixed Retrieve's messages being around the wrong way.
- Updated several messages to use lowercase 's' for 'shadow', as we use uppercase to refer to the plane and lowercase for the actual element.
- Fixed the middle Eclipse message to show the target's name.
- Fixed some typos in Eclipse's messages and made some tweaks.
Templar fixes:
- Inline empowering works again.
Templar typo fixes:
- Defend was proccing the Riving version messages and has been fixed.
- Fixed Deliverance's messages being around the wrong way.
Both classes:
- Removed weapon charge colouring from the combat message (it was previously unintentionally affecting only half of the message).
I removed combat messages from some abilities that I noticed didn't originally have them, as this was an intentional design decision. We generally avoid putting combat messages on passive effects. Affected skills:
- Defend/Juxtapose
- Pestilence/Choke
- Purity/Claw
- Redemption/Symbiosis
I didn't go hunting too hard for these, so if there's other passive abilities within Templar/Revenants that now have combat messages attached to their passive effects and didn't before, please let me know.
Penned by my hand on Closday, the 13th of Midsummer, in the year 494 MA.
Autoposter
10
Re: Announce post #3171: Where's Mining and Mirrors?
When will the new classes be added to style scrolls?Learn message catchup is my first priority, then styles right after that. I'd like to (hopefully) get all of the blanks filled in where we're missing them. I'll be chipping away at those as I've got time between wedding planning (help me)
Brax
6