Redwall MMORPG 3D gameplay / dev environment

The two game systems of Dread and Hope make up the unique and revolutionary death penalty in the Lord of the Rings Online (LOTRO). In short, dread is the negative effects on your character when you are defeated (there is no dying, per se, in LOTRO) and hope is beneficial [1] that can be granted to your character. How exactly these systems work together is not clear from the tutorial, so it is the purpose of this guide to explain how they operate.

The cumulative effects of Dread and Hope
Both game systems concern three things: maximum morale, healing effectiveness and damage received. The latter two are self explanatory but the former may not be; it is LOTRO's version of hit points or health bars. Obviously, if these stats are more in your favour then you will fair much better; that is why we need an understanding of what each and hope do to affect those stats.

When you start the game and have no hope or dread, those statistics remain at 100%. As you acquire hope or dread the numbers change. In the case of hope, the more you gain the higher your morale and healing effectiveness will be, while your damage received will decrease. Alternatively, if you accrue dread, your morale and healing effectiveness will decrease and damage received will increase. These effects at both ends of the spectrum – either extreme hope or dread – carry very significant boons or banes.

In addition to the negative effects of death that dread causes, when you are defeated and choose retreat now (you may wait for up to 600 seconds for a resurrect) you will return to the graveyard and your equipment will take damage and may need repair (especially after many defeats). Also, it is said that a dread count of five (the maximum anyone can obtain) renders combat nigh impossible for the afflicted combatant. So how does one accumulate either dread or hope?

How do I accumulate Dread?
The primary method of acquiring dread is being defeated in battle. There is no difference in the amount of dread that is accumulated based on how many members you have in your fellowship (if any at all) or what kind of monster you are fighting; you will gain one dread point (out of a maximum of five) when defeat finally comes. When this occurs, the aforementioned stats will be affected by a few percentile points; certainly increased deaths will be a severe hindrance to your character.

How do I eliminate my Dread?
There are some situations where dread will be on you at all times (more on this later in the guide) but if you acquire dread via a death then it can be ‘killed off’ so to speak. This kind of dread is put on a ten minute timer and is viewable as an active debuff beneath your character window; once the countdown has expired the dread will go away. Alternatively, if you acquire hope then those points will off-shoot the dread, effectively eliminating it.

How do I gain Hope, then?
There are a few ways to gain hope. The first is simply being in a tavern, where much merry-making is to be had. You can also gain hope by listening to other players play on their instruments inside these very taverns. Also, being in the presence of particular NPCs – Tom Bombadil and Aragorn for instance – may fill your character with hope as well. Using an Edhelharn Token<s> or blowing a horn such as the Horn of the Dwarrowdelf<s> will also restore some hope.

There are also some spots throughout the world where the influence of the Valar is still felt. There is no visible marker to identify these places but when you pass through one you will see a pillar of light grow around you momentarily. This will increase your hope and can even banish dread instantly. Some of these places are stronger than others and bestow the Blessing of the Valar. You can recognize this as an effect icon in your Beneficial Effects or by the border around the minimap, which will become a slightly-metallic blue.
Lastly, there are some higher end options to accumulate hope as well, but it certainly is easier to accrue dread than hope. It is best then to use caution and avoid defeat at all times.

Situational Dread
There are some situations in LotRO where dread is inevitable, whether you are defeated are no; these are called situational dread effects. They are most common during the main epic quest line when you are faced against a great evil, be it a Nâzgul, Great Barrow-Wights or perhaps even the Witch-king himself! During these situations you (and your fellowship) will be afflicted with dread, perhaps up to three points! If you ever find yourself under these situations, be sure to have as little dread as possible; the cumulative effect could be world-ending for your fellowship. This situational dread, however, diminishes once your fellowship has defeated the great evil.

Tips and Hints to avoiding 'dread'-ful situations
The dread and hope systems are designed to be a lenient death penalty to players, while punishing those who attempt vain efforts with the same strategy that defeated them moments earlier. So if you find yourself accumulating too much dread, the following tips should be of help:

If you can't defeat that bear in the Old Forest once, twice, do not attempt a third time! Chances are you will be defeated and be overwhelmed with dread, and owe considerable coin to the local merchant.
If in the course of your adventures you find yourself defeated and return to the local graveyard, take the time to turn in quests and sell your loot. If you do this, chances are, by the time you get back to where you were before defeat, your dread will have expired.
Do not attempt any instanced fellowship quests while you or anyone else has dread; you will likely face one or more opponents that inflict situational dread effects.
Best of luck avoiding situations full of dread!
Converted from Guides
Created: 2007-02-12 09:01:15
Last Changed: 2007-02-17 07:16:43
Author: Magi
Category: Game Systems

IP Address Information
IP Address: 83.187.180.2
Hostname: m83-187-180-2.cust.tele2.se
ISP: Tele2 Sverige AB
Connection Speed: (DSL) Broadband/Cable/Fiber
City: Goeteborg
Country: Sweden
State: Vastra Gotalands lan
Latitude: 57.70716
Longitude: 11.96679
Time Zone: UTC +01:00
Local Time: 13 Feb, 2022 10:35 PM
Proxy: No
Proxy Provider: -
Address Type: (U) Unicast
ZIP Code: 41879
Area Code: 031
IDD Code: 46
Weather Station: Molndal (SWXX0021)
Usage Type: (ISP) Fixed Line ISP
Domain Name: tele2.com [WHOIS tele2.com]
Mobile MNC: 10
Mobile MCC: 240
Mobile Brand: Spring Mobil
Elevation: 4 meters
ASN Number: 1257
ASN Name: Tele2 Sverige AB
Category: (IAB19-18) Internet Technology

blendyard
A collection of tools to make it easier to create content for O3DE using Blender.

Node based Coding

Also known as flow based programming.
medium.com/@umarkhandev/node-based-coding-7433424fa4b0

A node-based interface to mostly create gameplay elements. As with many common scripting languages, it is used to define object-oriented (OO) classes or objects in the engine. Under the hood these are just C++ functions. Most developers will use this ‘library’ of sort and add their own custom built functions to push it to the next level. Theres lots of games that are made without a single line of code using this.

Object Wiring
www.zdnet.com/article/object-wiring-an-observer-observable-pattern/
While designing software applications, you’ll encounter situations in which you need scalable communication among objects within and outside an application’s periphery. When certain states or conditions occur within an object, you need to notify other objects, and vice versa. This process is often called object wiring—tying objects together so that they can communicate with each other. In this article, we’ll create a pattern (for the .NET framework) for achieving object wiring in a scalable manner.

Event Subscription
docs.microsoft.com/en-us/dynamics-nav/subscribing-to-events

Event subscribers determine what actions to take in response to an event that has been raised. An event subscriber is a C/AL function that subscribes to, or listens for, a specific event that is declared by an event publisher function.

Representation of Conditions
www.ibm.com/docs/en/zos/2.1.0?topic=applications-condition-representation

Conditions can be defined in many ways. Some examples are hardware- or software-detected events (which might or might not be critical for the application to run properly), asynchronous events, or the completion of a unit of work (successfully or unsuccessfully).

Systems communicate information about conditions in a variety of ways. Return and condition codes are examples of condition information.