What this is:
-A thread for suggesting changes to be made later in the Overhaul. That is to say: not changes that need to be made immediately, or changes to afflictions, or critiques of how the overhaul in general is being conducted. There's other threads for that.
-An attempt to make game mechanics easier new players to use. Lots of Lusternian mechanics are difficult or unpleasant to use without aliases/triggers/scripting to substitute more a user friendly interface or to automate some aspect of the game.
-A compilation of the above ideas. For the sake of the Admins not having to go through the entire thread, I'll be editing the suggestions into the OP as they come and sorting them by mechanic/class.
What this is not:
-An effort to "dumb down" combat. The objective is to remove technical/scripting/conceptual hurdles for new players getting into the game, not reducing the skill required.
-A way to improve your skills and ruin your enemies! For the sake of avoiding bias, please try to avoid suggesting things that significantly alter game balance.
-An envoy report. There's no reason to use the envoy format or to pester the admins for a "special report". I'm certainly not doing it with this thread and you shouldn't either.
-A bug report. If something is bugged, use the BUG command. This is for features that work as intended, but which could be made to work better.
Things that I would prefer not be discussed:
-The following obnoxious envoyisms: "Misfeature", "The Plan", "The Vision", "Nerf", "Buff".
-The following highly flammable topics: accusations that X guild was ruined by a special/envoy report, envoy reports in general, statues, totems, Angkrag and who has more/less active gods/orders/leaders/combatants.
-Arguments along the lines of "Your system can/should do that for you." or "You can write an easy alias/trigger/script for that." New players probably don't have a system and most players do not personally know how to code. The idea here is to suggest changes that minimize the amount of client side coding required to play Lusternia.
-Speculation into how easy/hard a feature would be to code. Players are notoriously bad at guessing this, so leave the question of whether a feature is worth coding to the game's actual coders!
Without further preamble:
General Requests:
-A prompt option for current moves left before "hasty" messages start.
-Combine the CURIO and CURIOS commands, or put a reference to the other at the bottom of each.
-Add a LAST modifier for library commands, which starts you at the bottom of the list rather than the top.
-Allow DISCERN in discernment to also display everything CONTEMPLATE does.
Mapper/Autowalking Requests:
-A command which returns the current room number (as used in MAP and PATH WALK <room>) of the player but not the visual map. Map does this for most rooms, but it does not display for all mapped rooms and not all rooms are mapped.
-Optional addition to the above: Also area name (as seen on MAP LIST ie. tutotophet, zvoltz_temple, ethglom) and XYZ map coordinates.
-Optional addition to the above: A map config option to display the above command (in either version) on movement instead of/in addition to the visual map.
-Change Scry, Scent, Window, Astrogaze, Bond Look, etc. to report the room numbers of unique rooms as well as their names. The ability to pursue a target this way is vital to Lusternian combat and should not be an ability exclusive to people with access to a system's proprietary map database.
-Optionally: Report the room number even for non-unique rooms (ie, seas, elemental planes, etc.). The Map of Mystery artifact already includes this feature for mapped rooms; it's simply a question of if it should remain artifact exclusive or not.
Bard Specific Requests:
-Replace song duration with mana/ego drain. Instead of scaling duration up with skill, scale drain down. Currently, bards NEED an automatic refrain trigger to be any good at being a bard. That's silly. Refrain repeats the current stanza, but does nothing special to drain.
-At a prompt config listing the player's current stanza as either 1-9 (for stanzas 1-9) 0 (for no song) or s for sustained.
-Change MajorSixth to work more like Teleport, such that the bard does PLAY MAJORSIXTH RAZINES instead of PLAY MAJORSIXTH 29640. Guild milestones can be targeted using GUILD or by the name of the guild, personal milestones using PERSONAL and bonus compass milestones using COMPASS.
0
Comments
You have received a new honour! Congratulations! On this day, you have shown your willingness to ensure a bug-free Lusternia for everyone to enjoy. The face of Iosai the Anomaly unfolds before you, and within you grows the knowledge that you have earned the elusive and rare honour of membership in Her Order.
Curio Exchange - A website to help with the trading of curio pieces in Lusternia.
I'm not sure how it'd be useless, considering you can use PATH WALK <vnum> to get to the number indicated by the scry, removing the need for a mapping/walking script.
Contemplate?
E: As for scent, people with autowalkers can already do that. Lots of people make room name to room number databases and match scent results to autowalk directions. The ability to do it is already out there - all this would do is level the playing field so that everyone with scent can do it, not just everyone with scent and a good system.
I can definitely see the case for not having this be usable when there are duplicate room names though. I guess the big question is how costly that will be in terms of development and runtime... It wouldn't exactly be a trivial thing to check every other room in the world (or even area) to see if any of them have a duplicate name.
Honestly, I'd love if discern could be the all in one enemy status checker. Configurable to show one or more of health, mana, ego, wounds, time warp, temporary insanity and power. In fact, might just pop this over to "simple" ideas
@Ssaliss: This isn't a dichotomy, those are not the only two options and I don't think framing the discussion like that is particularly useful. That said, my preferences are currently, from best to worst:
1. Display room numbers only for rooms with distinct room names. Determine the distinctiveness of a room based on individual room names in some runtime cheap way.
2. Display room numbers for all rooms, except those in the following areas: Elemental Planes, Illwater, Inner Sea, Sea of Despair, Undersea, Iceburn, Crystal Meadows.
3. Display all room numbers everywhere.
4. Display no room numbers anywhere.
Some of these are great ideas! However, none of them realy fall within the framework of the overhaul in that the overhaul is strictly about PK mechanics. Many of them would make great envoy reports though.
The only two that really caught my eye as non starters the scry reporting room numbers and removing refrain.
I have some personal reservations about making auto trackers, many of which already exceed the allowed limits of the "afk/automation" rules in my opinion, more available to the masses. That being said, given the current state of things, I don't see it causing any particular issues. However, I don't know how possible it is to do this for all the rooms except for those that are duplicates, as imagine that will involve a substantial amount of work to find and flag each room that is a duplicate. Ieptix would have better insight into this, but I suspect it is unrealistic to expect this to come to fruition.
I don't see any issues with refrain, but I do see issues with passives that do not time out and have only a marginal upkeep cost. This would be akin to making demesne effects never time out. I think we need to be realistic in that true newbies that are not capable of making a simple echo timer probably don't need their songs up perpetually to function.
(I got your joke @Rivius!)
* Expand the artisinal & bardic competitions to include guides and general info on the game. When I first started playing I got a lot of incorrect information on many topics, it would have been great to have a source that was vetted as correct. Also, it was often the case that I just didn't know I should be doing something because it wasn't written down anywhere.
* Offer an NPC dummy to face in the arena. Masochism has its limits and the population is too small to expect others to be on hand when a newbie wants to try out their shiny new abilities.
* Expand the scope of the newbie channel or offer another basin wide source for answers IG.