Atheist42

Habimaru wrote: »

(Pegasuses = American; Pegasii = International English-Standard).

If you are following the Latin convention, as UK English often does, I think the plural of pegasus would be pegasi, not peagsii. Going from singular to plural, replace "us" by "i". For example, the singular syllabus gives the plural syllabi. The only cases where a double-i arises in a Latin plural is where the singular already had an "i" immediately before the "us" ending. For example, the singular radius gives the plural radii.

I think I can now claim 5 pedant points.

Hazurah wrote: »

the hardest part is measuring the dungeon changes since that huge patch

And over 2 years on from that quote, there's still not much progress on that. The thing is, since that update, playing Uladh dungeons isn't an efficient use of gaming time. When I've got time to do stuff on the wiki, I don't look for a random page that needs updating and work on it. I work on pages that I personally use or need. So, I'm altruistic enough to try to improve the wiki for the benefit of the community, but still selfish enough to only work on the bits that are also of some help to me. I suspect a lot of editors are like me. So, if you find some part of the game that's been around for many years, and it's not well documented on the wiki, chances are it's a part of the game you should consider ignoring.

If Nexon greatly increased the combat power of mobs in Uladh dungeons, so that most of us could earning experience from them and use them for completing training requirements involving strong, awful or boss mobs, then we'd probably find people would start playing Uladh dungeons more and wiki editors would start updating the relevant wiki pages.

And I don't mean to imply that being a partially selfish editor like me is a bad thing. We've all got time constraints and any accurate edit is a good thing for the wiki. Nor do I mean to imply that all wiki editors are like me. There are some truly selfless people who work on the wiki, or maybe they are obsessive compulsives who just can't stop themselves from trying to complete the wiki. Whether their efforts are due to extreme altruism or a mental health issue, I'm very grateful that they chose to work on "our" wiki!

(But seriously, if it is an obsessive compulsive thing for you, try to take some time away from the wiki and go talk to your doctor about it. I appreciate your work on the wiki, but I'd be happier if the wiki has a few gaps but you get healthy.)

When the pet is first summoned, it appears to be unconscious. However, phoenix feathers have no effect on the parrot. That is, it seems the parrot is no more! He has ceased to be! 'E's expired and gone to meet 'is maker! 'E's a stiff! Bereft of life, 'e rests in peace! If he wasn't nailed to the perch 'e'd be pushing up the daisies! 'Is metabolic processes are now 'istory! 'E's off the twig! 'E's kicked the bucket, 'e's shuffled off 'is mortal coil, run down the curtain and joined the bleedin' choir invisible!! THIS IS AN EX-PARROT!!

The pet's skill window shows it has the special skill "Pining for the fjords." Since it is not possible to revive the parrot, it is not clear what this skill does.

To compensate in some small measure for the parrot's inactivity, it has a 10x10 inventory.

On 2nd thoughts, there may be copyright issues with this pet. I withdraw the suggestion.

Consider the 10 pages required for the "Book on Fireball". Some pages are rare. Some are so common that people don't even bother collecting them when they drop. So how about we create a new Synthesis Recipe. Combine any three Fireball pages. If the synthesis is successful, we get a different Fireball page. That is, if we successfully combine 3 copies of page 1, we get a random selection from pages 2 to 10. If we successfully combine pages 1, 2 and 3, we get a random selection from pages from 4 to 10. This would give some incentive to pick up the common pages when they drop.

The same idea can be applied to all skill collection books: Fireball, Ice Spear, Thunder, Arrow Revolver and Shock.

It could also apply to other collections such as Dorcha Crystals. The Second Dorcha Crystal seems way more common than all the others. It would be nice to be able to get rid of my worthless multiple copies of the Second Dorcha Crystal by combining them for a chance to get one of the rarer Dorcha Crystals.

The idea can also apply to armor sets with bonus stats.

As an example, consider the Female Bohemian Armor Set. There's armor, hat, glove (band) and shoes. Each contributes 0 to 3 points to Magnum Shot Enhancement and 0 to 3 points to Support Shot Enhancement. However, you need to accumulate at least 10 points to an Enhancement before it has effect. So if we get Bohemian Shoes with bonus stats of 0 and 3, (0 on Magnum Shot and 3 on support shot), they're not very useful, since even if we get 3 points for Magnum Shot from each of the armor, gloves and hat, we'll still don't reach the minimum of 10 points. My experience is that we should should sell these shoes to an NPC, since we're unlikely to be able to sell them for a better price in the Auction House. In fact, it even seems to be a waste of time to try sell shoes with 1 point for either stat, since they only generate a bonus if they are worn with 3 other pieces each of which has the maximum of 3 points. No one seems to want to buy anything with less than 2 points on both stats.

So my proposal is that we can synthesis 3 pairs of Bohemian Shoes. If successful, the bonus stats are the sum of the stats on the 3 combined pairs of shoes. This can give higher stats than currently available maximum of 3 points.

For example, consider 3 pairs of Bohemian Shoes with stats of (0 and 3), (3 and 0), (1 and 2). Currently I'd sell these to the nearest NPC since they're near to worthless. Under what I'm proposing, if I successfully combine these with Synthesis, I get Bohemian Shoes with stats of 4 and 5.

The "Rescue the Scout" shadow mission has 17 waves of enemies occurring at 1 minute intervals.

The problem is that if you are in a reasonably powerful party, then it can take about 5 seconds to kill all the enemies in a wave, and then you have to wait 55 seconds for the next wave. A game that forces you to spend most of your time waiting is not fun. If you provide a method to accelerate the spawn rate so that we can deal with the 17 waves more quickly and complete the mission faster, then we can spend more time on the parts of the game that are fun.

Suggested solution: Add a switch in the middle of the playing area. While there are enemies alive, the switch is inactive. When all the enemies in the current wave are dead, the switch lights up, and then hitting the switch makes the next wave spawn immediately. If no one hits the switch, because say they're healing the 3 NPCs or collecting drops, then the next wave spawns 1 minute after the previous spawn, as occurs currently. That is, if your party is playing near the limits of their ability, they can still take over 17 minutes to complete the mission, but if you are in a strong party, you can get it over with in a couple of minutes.

Of course, this might now mean that a couple of strong humans might be able to knock off all 17 waves of enemies in a single spell of Final Hit. Personally, I don't have a big problem with that, but if the game designers want to avoid that, they could modify the above suggestion to also include a minimum period of say 15 seconds between waves. But I think a better solution would be to improve the enemies' AI. Currently the enemies are all pretty stupid when it comes to reacting to what players are doing. If the enemies see their colleagues being wiped out by a player using Final Hit, any sensible enemy would load counterattack. (OK - not all the enemies in this mission have counterattack, but enough do to make a difference.)

I've made this suggestion with respect to "Rescue the Scout" since that's an easy one to explain. But if you do implement this suggestion, you can then also think about adding it to the other shadow mission that can have tedious periods of waiting if you are in a strong party: Taillteann Defensive Battle. It's a little messier to implement there, because you have enemies spawning at 3 different gates, so you need 3 different switches operating independently. That is, if the pair operating at the South Gate decide to hit their switch to bring forward the next spawn, it should NOT also immediately spawn a new wave of mobs for someone struggling at the East gate. There's also the issue that if the players at one gate fail to keep up with their spawns, the spawn location then moves to a new position nearer the centre of town. So then you need to decide whether to move their switch to the new spawn location. My opinion: It would be nice if the switch moved, but if they've failed to keep up with the spawns at the first location, they are probably not going to want to accelerate the spawns at the next location, so providing a switch that doesn't move is not a big problem. It would still be an improvement over the current scenario of no switch at all.

Anyway, I suggest implementing the suggestion for the simpler case of Rescue the Scout first, and making sure that works properly, before worrying about how to fix Taillteann Defensive Battle.