Let the hero only know that is morning / afternoon / etc until he picks up a watch.

@gabriel200899 O que tu achas? Relógios de pulso é um pouco futurístico, mas eu acho que é uma ótima ideia (plagiada do CDDA).

@gabriel200899, um pedido:
acredito que no futuro a "campanha" será gerada por um algoritmo que, inicialmente, apenas distribuirá Locations predefinidas.

Querias que tu fizesses algumas e deixasses nessa issue (eu arrumo como quiser depois, mas tu provavelmente programa-las-ás).

Por exemplo:

 F = Forest
 D = Desert

Como não temos múltiplas cores, é necessário utilizar um letra diferente para cada location.

Isso é uma contribuição importante, leva a sério. Podes já definir o que deve spawnar em cada location também (permittivity e toda a porcaria que tu conseguir imaginar). Essa issue não será fechada e servirá de referência futura.

Implement a simple but fully operational in-game wiki.

@gabriel200899 Termina pra mim.

Using "sw" walks south because the implementation may only check for the first character.
It should check for the abbreviation or the full name of a direction.

As it has been done to "kill", make "pick" work without arguments when there is no ambiguity. A more generic checkIfEmptyKillIsUnambiguous is likely the right way to do this.

Design

• Create a Command class (to encapsulate the commands entered by the user).
• AchievementBuilder class.
• Load hints from resource files.
• Store aliases independently and let the player add and remove aliases.
• Tagging system for locations. So special behavior could be added by appending a String to a set.
• Tags for "N", "E", "S" and "W" (accessible by North, East, South and West, respectively).
• Implement a type for the possible commands, create an instance for every command and iterate through a list instead of using a big if-then-else chain.

Features & Content

• Hero must also be able to critically hit with his bare hands.
• 20 achievements.
• Rivers.
• Bridges.
• Maps (a map command that prints an ASCII map of the locations the player already visited).
• Creature will have an bloodAlcoholContent double variable (% by volume).
• AttackAlgorithms will account for insobriety.
• Pocket Watch and Wrist Watch instead of clock.
• Implement a third coordinate to Point (z).
• Implement dungeons (in z = -1).
• Implement healing during sleep.

Changes

• Remove the leveling system.
• Make less-than-enough-for-a-full-bite heal less than enough-for-a-full-bite would.

A message "Invalid input." appears when it should not.

Implement magical items that have colored name and that modify your spells (a factor by which magic damage or healing is multiplied).

This is a bug with the wiki search method.

Write a tutorial and a tutorial command.
Suggest the tutorial if the game launches without any saved games.

Create a type such as CauseOfDeath and use it in BattleStatistics.

This type would contain:

• A value of an enumerated type such as TypeOfCauseOfDeath that defined what was the type of the killing hit (such as poisoning, weapon, magic, etc.).
• The ID of what killed the target.

Suggestions

• Warlock could be an achievement for killing five creatures with magical attacks.

The road not taken
Two roads diverged in a yellow wood,
And sorry I could not travel both
And be one traveler, long I stood
And looked down one as far as I could
To where it bent in the undergrowth;
Then took the other, as just as fair,
And having perhaps the better claim,
Because it was grassy and wanted wear
Though as for that the passing there
Had worn them really about the same,
And both that morning equally lay
In leaves no step had trodden black.
Oh, I kept the first for another day!
Yet knowing how way leads onto way,
I doubted if I should ever come back.
I shall be telling this with a sigh
Somewhere ages and ages hence;
Two roads diverged in a wood, and I
I took the one less traveled by,
And that hás made all the difference.
ROBERT FROST, 1916

Colocar esse poema no jogo.

"poem" pode ser o comando dele.

@gabriel200899
Assim como o player não deve saber até os segundos, acho que não é legal saber que uma arma está com 21/100 (por exemplo).

Deveria ser algo como: broken, damaged, ...

Sugestão

<nome>
slightly damaged <nome>
damaged <nome>
severely damaged <nome>
broken <nome>

New usage

Do not use spells during combat.

Syntax

cast [spell name] on [target name]

Where target is any Entity.

Using an aggressive spell (such as Fireball) should initiate a combat.

New spells

Add healing spells.

Achievements

Spell based achievements will require hit killing.

In order to reduce the size of the saved games - that likely will become an issue as the game gets more and more content - Locations far from the player could lose some data. A swamp should stay a swamp forever, but after the player is (say) 100 locations away, the creatures, (common) items and spawners of that location could be erased and regenerated when needed.

Let the character equip different bags and backpacks that work as his or hers inventory. A character could also drop the backpack and pick it up later on to recover all items that were inside it.

Someone must finish the tool.

Fox........................................2
Rat........................................3

is ugly. I plan something closer to

You see two foxes and three rats.

However, to make this possible, I need to provide multiple names for monsters and items.

Additionally, article should become a field. So that the game gets a fox and an ogre straight.

A few improvements are necessary in order to further develop the game.

• Lists (e.g.: SKILLS: FIREBALL | FROST_BOLT)
  | looks like a good separator for elements. It is very unlikely that text, however big, will contain |.
• Different line breaks (e.g.: \ and \\)
  Currently \ is replaced with \n, whilst there should be a line break (for bigger passages) that would be converted to a mere space.
  Reuse the following table in CONTRIBUTING.md if implemented

• Creature will become an abstract class.
• Critter, Beast and Hero will be concrete subclasses of Creature.

@gabriel200899

• 12 locations.
• 15 achievements.

• debug achievements command that shows all not yet unlocked achievements.
• debug spawn [creature_id_1, creature_id_2, ...] command.
• Sometimes Seth does not sleep enough - fix this as soon as possible.
• When it is too dark, let Seth see some things, just not everything.
• Let debug exploration use a Table.

• Abstract Achievement class [with isUnlocked() and update(Hero)]
• BattleLog class
• BattleAchievement class
• ExplorationAchievement class
• Hero.visitedLocations (CounterMap) // counts how many times the player visited a location
• Hero should have a 5% critical hit chance (through his attack algorithm)
• Help strings loaded from a file
• Luminosity (ParOfDay attribute)
• LightPermittivity // a location-specific attribute that defines how much light penetrates a give location

Also rename MAX_HEALTH to HEALTH and let the preset use setHealth.

Self-descriptive.

@gabriel200899 I choose you!

- [ ] Benchmark how fast it is to generate game data from resource files.
- [ ] Benchmark how fast it is to load game data from binary files.
- [ ] Benchmark how fast it is to generate a SHA-1 from the resource files.
- [ ] Evaluate if it is better to reload just when something changes.
- [ ] Implement serialization / deserialization of game resources to improve starting performance.

Notas para meu futuro eu:

Considere criar uma linguagem de script que será utilizada em todo o jogo (SQLite parece exagero).

Comentários, texto de ajuda, localizações, monstros e items, inicialmente, seriam definidos por esses scripts.

// Define Ghoul
# Linhas iniciadas por "//" ou "#" são ignoradas.

// ID e TYPE são strings e o jogo terá alguns HashMaps carregados na memória para dinamicamente
// acessar o conteúdo que foi lido dos scripts.
ID: GHOUL
TYPE: UNDEAD
NAME: Ghoul
ATTACK: 12
ATTACK_ALGORITHM_ID: UNDEAD

Debug command to wait until the specified part of day.

Replace all

a = container.get(b); container.remove(b);

with

a = container.remove(b).

As soon as we get more than one location preset, we can start to think about regions.

Initially, I am thinking about implementing simple blobs of similar locations.

For instance, this would be a "decent map":

FFFFDD
FFFDDD
FFFFDD
FFFFDD
FFFFFF
F = forest
D = desert

This will not, however, be achieved by randomly picking locations, so I think that we will need an algorithm that, after picking a random location preset, generates a "blob" of that location. Maybe a blobSize variable should be part of the location preset, so that we don't get hundreds of ponds or a single forest location in the middle of the desert.

Sample use case for the first version of the quest system

1. Player issues talk [npc_name].

2.a) If the player does not currently have the NPC's quest, it will be added to his journal.

2.b) If the player already has the quest, the NPC will ask the player to finish it.

3. After the player finishes the quest, talk [npc_name] transfers the quest items to the NPC and gives the character his reward.

Observations

• The player can access the Journal at any time through the journal command.
• All quests will be based on collecting items and returning them.

• Three different locations for the demo campaign.
• Five different achievements.
• Custom save name.

Os mobs são printados assim:
Bat
Bat
Bat
Bat
Rabbit
Rabbit
Será feito algo para que eles sejam printados assim:
Bat(4)
Rabbiter(2)
Caso sim, antes da release ?

Dungeon will get a new, clean, repository at version 1.0.0.

This issue will be used as a tracker for all the improvements needed to get to the version 1.0.0.

Feel free to add your request / modification.

• Start a release goals list.
• Spawns.
• Remove all TODOs (finishing them along the way, obviously) from the code.
• Abstract Achievement class [with isUnlocked() and update(Hero)].
• BattleLog class.
• BattleAchievement class.
• Critical hits for the hero.
• Hero must also be able to critically hit with his bare hands.
• Implement better printing so that output avoids cutting words in the middle due to too long strings.
• ExplorationAchievement class.
• Hero.visitedLocations (CounterMap) // counts how many times the player visited a location.
• Hero should have a 5% critical hit chance (through his attack algorithm).
• Help strings loaded from a file.
• Luminosity (ParOfDay attribute).
• LightPermittivity // a location-specific attribute that defines how much light penetrates a give location.
• Issue #40
• Inventory size increases with leveling.
• Perfect the existing time system.
• Campaign has 20 achievements.
• Creature will have an bloodAlcoholContent double variable (% by volume).
• AttackAlgorithms will account for insobriety.
• Implement the Fibonacci sequence.
• Pocket Watch and Wrist Watch instead of clock.
• Load hints from resource files.

If there is a fruit bat and a bat in the same location, kill bat does not work.
Maybe the selection should use the same algorithm that the wiki search does.

"A sketch of the spawners."

Description.

• After a creature dies, its corpse will lay on the ground and all the items it had in its inventory will be dropped.
• Milk command to get milk from cows. MILKABLE tag.
• Readable items with actual text (letters, journals etc). READABLE tag.

This release implements the inventory system (currently, a prototype).

• Create the Inventory class.
• Hero has-a Inventory.
• Inventory size increases with levelling.

Additionally, this release will also implement foods and world (in-game) time system.

• Perfect the existing time system.
• Resting only replenishes your health up to 60%.
• Eating replenishes your health up to 100%.

Even further, this release also does the following:

• Campaign has 20 achievements.

Initially, consider a system that only randomly changes the weather and we limit ourselves to writing out the weather to the output of look.

After that, the weather system should keep a log of the weather and then refresh calls could take that into account. This way an item may evaluate how much it has deteriorated since its last refresh and update its status. Also, implement funnels that collect rain water into barrels or something similar.

In the bottom of the window, using a whitespaces with a colored background make two bars.

Bonus: centered, write "HP: x/y" and "EXP: x/y" for extra nothing.

Generate an object from the user input.

Discuss: a feedback command that allows the player to send feedback (to whom?) in the game.

A first simple version could send an e-mail to me ([email protected]) but that does not look right. Having a server that could get these messages and update a static page with them would be neat.

Upon death, after reloading the game, the command history is problematic.

The cursor is still at your last before-death command and your new commands just overwrite older ones (they do not get added to the end).

Add to Help.java all commands and their respective infos.

Magical poisons that may be added to weapons to inflict extra damage.

Initially, just more damage. Later on special effects may be added.