or maybe it's the weakest link, or who knows, but those people do not join the game automatically.

Luck can affect:

• critical hits
• chance to get skills modified
• increased chance for events to happen
• chance of being missed (instead of deflect)

because otherwise it's unfair.

consequently, if players are super underleveled, then they should be able to gain a lot more XP

messages should have more types, like battle, event, etc. and be broken up into more parts.

Events should have: eventText, player, item, oldVal, newVal, valStat (where applicable)

Battles should have: attacker, defender, item, hp, mp, special, and probably more, where applicable.

Most things that are using MessageCreator.genericMessage need to be changed accordingly, to use a new way and to allow the IRC messages to be colored.

This idea needs to be fleshed out, but so far, the idea is that players should be able to gain rapport with each other (or the opposite) in certain circumstances, ie:

• join a player in a party means relationship++
• fight alongside a player means relationship++
• fight a player in combat means relationship--

there should be able to be a boss on a map, and it summons nearby players (maybe +- 50 spaces) to help fight the boss.

bosses have special weapons that can be picked up upon beating them, which are defined per boss.

all boss items should be elevated to the highest tier of items (even if their score does not fit that categorization), no matter their status.

there should be 2 personalities that come with this: ignore boss items, and never unequip boss items. the former would make it so you never equip boss items, and the latter would make it so you never unequip a boss item.

if a player can equip a boss item in normal parameters, they should always do so no matter what (excepting personalities listed above)

when spells are added to player.affecting, there should be a setting to allow them to refresh the existing spell as well as push a new instance into it, for stacking intensity and stacking refresh.

%person% would be a random person from any team, %person team:1% would pick a random person from one team, %team% would pick any random team.

the only implementation difference is that it should be $person team:1$.

these methods can be added in MessageCreator.doStringReplace

because why not

Because of the broken whois functionality in node-irc, we have to use nick-based authentication for now. When this is no longer an issue, it needs to go back to nickserv.

structure it the way items are structured

then make it importable via ComponentDatabase

canAct will search through all of the affectingSpells and see if any of them are blocking the next turn.

This should pass in the player to the score, and do a personalityReduce on them for some specific calc method. Maybe intScoreValue or something, passing you the base value and you can modify it. This means fighters could remove int values from an item for example, and say that con should be valued twice as much.

[15:17.46] @kr So basically you want any event to be able to result in any effect, letting it mix-and-match randomly.
[15:18.00] @kr Sure, I guess.

this works for items, but not events. there may need to be a bit more data organization happening, ie, putting item-related things into an items folder, events in an events folder, etc.

When the bot joins the channel, it needs to get a +m, and a topic based on Constants.channelTopic.

PlayerStatistics should keep track of all of the miscellaneous statistics available to a player.

When achieving a certain threshold for the statistics, personalities should unlock to the player.

There should be a left and a right for party name generation, all of which are picked randomly when a party is formed. So, I could have:

.. Or any combination thereof.

Perhaps also have some names that are single, maybe like an item is generated, so instead, there would be a left, middle, and a right of party names. This would allow for names like Singularity, Band of Singularity, or Band of Singularity for Great Justice, or Singularity for Great Justice.

Some players should not be able to battle other players. Perhaps there should be total score threshold between the two.

So if there's a party of 2, then someone leaves, it should disband it.

There should be an event that can enchant an item, either by adding a new adjective to it, or adding a +1 to it. It is not yet determined what the +s will do.

this way they can be persisted.

This happens when a user quits while logged in.

one way to implement this:

example stats:
icePercent: 5
ice: 100
fire: 10

percent / value works like stats, so the total fire damage in this example is 10, and the total ice damage is 105 (ice + ice*icePercent).

So, supposing you roll 50 base physical damage, on top of that you will have 10 fire damage, and 105 ice damage, for a total of 165 damage. Enemies can counteract this with their elemental resistances.

Elemental damage will be calculated with:

• finger
• hands
• mainhand
• offhand
• charm

Elemental resistance will be calculated with:

• body
• feet
• head
• legs
• neck

This needs to calculate based on the players stats, as well as the personality modifications for each. Also, the other stats need to be factored in somehow.

There will need to eventually be a second condition in the dodge clause that a target will have to roll to successfully dodge, so dodges don't happen too often. This is pending the future being terrible with everyones stats, so we'll see.

This will be a 1-100 roll, and items can increase the percent change to succeed. The base % is probably going to be 1.

Things that go in this database:

• party names
• mad lib nouns / adjectives / verbs

It should, maybe 5% of the time, add a new stat (one that is currently 0) and set it to 5. Otherwise it should only modify an existing stat.

Otherwise this could be forked into a new enchantEvent, a la #39, and it could serve those purposes.

This way players can get an actual gender based on their Kurea setting.

Use destructuring:

{@name, @fire, ...} = options

maybe?

There should be an event that flips a random stat (ie, -7 -> 7, 500 -> -500) on a random item for a random person.

This could also exchange two stats on an item, so the STR becomes the INT or something.

if a player is significantly weaker than the opponent but somehow got into battle, they should flee.

also, fleeing should happen occasionally if you're lower than 10% HP. to do this, a new reduction will have to be added called Character.calc.fleePercent that determines the percent chance a player will flee. By default, this will probably be 0%.

Classes will be able to modify this, and most classes that do will modify it by saying that there's maybe a 20% chance to flee if you have 10% health, 50% chance at 5%, 100% chance at 1%, etc.

Fleeing will incur no XP loss, but you can not be brought back onto your team (as opposed to dying, where you could be resurrected).

adding world News to fill the blanks in between events and to make the world seem more alive. and make those news semi random so the world feels like its evolving.

example:
Weather forecast,
Important people dying,
someone is born,
a Criminal is arrested.
....

Here is a list of all of the cataclysms and what they do.

idk

Party names should not be allowed to be duplicated.

this should be a thing. the following events should also happen: critical, criticalled

this will probably also have to roll a 1/(allplayerstats) chance to get a critical, so it doesn't happen too often. Of course, that will be unbalanced as time goes on so there will have to be some normalization. I'm not sure specifically what the normalization would be.

On the map, it should be possible for ??? to force events to happen (like findItem, forsakeItem, etc). What I would do is open up the map, add some Question mark events to the map (throw them in an Event category), and give them a property called forceEvent. When a player steps on this in their move function, check for the existence of this property, and if it exists, directly call that function with the player.

Currently players are chosen randomly to act, but this should be changed so they each get a turn.

This is handled currently in the IRC module so it is an easy fix.

player stat calculations do not account for percentages

These percentages should always be applied after the actual stat themselves. This can be added in Character.calc.stat to just personalityReduce myStatPercent, take that number, turn it into a percent, multiply it by the stat value, and add that back to the stat value.

For instance, in a snowy area, there might be special snow-related events that can happen, such as falling in the snow, getting frostbite, making a snowman.

There could also be areas which have a large impact on the game, such as an enchantment fountain where positively enchanting items happens very frequently for the duration that the player is inside of the fountain.

Currently it just shows the new item score, like [25].

It should probably show like this: [itemScore: 5 -> 25 | +20]

Or something.

Such as:

Fighting Foxes
Band of Warriors

there should be an API command, as well as a Game function to update. All it really has to do is a git stash and a git pull, and a system.exit, but it would help immensely.

since I've seen parties with size, like, 6. or more. it's crazy.

it should be possible for players to earn money in combat, as well as items, or steal items, or other things that are TBD. when they are decided this issue will likely be split into a number of them.

Ideas: Renovatio: betting gold - maybe a random two people will bet on the outcome of a battle.