Welcome back

Pick a uniqie name and a pin number for yourself and hit "Go". This will create you a profile.

You can retrieve your existing player by entering your unique name and pin number and hit "Go".

If you didn't previously have a pin number, enter your name and a new pin. This will be saved for next time you login.

Change Log

22/01/2021
  • New: Dark theme! login to change to the dark theme. Click the button under your profile details..
19/01/2021
  • Status: Moving out of Pre-Alpha into Alpha. The games base code is working well. Thank you to all who have been testing and giving feedback.
  • Update: Updating descriptions for locations and direction of travel.
19/01/2021
  • Update: Enabling the paths to the rest of Phase 1 map. There are a total of 60 tiles in the game now. in a 10x6 grid. (Phase 2 I plan on adding another 40 tiles to make it 10x10.
18/01/2021
  • Update: Design tweaks and a few costmetic changes.
  • Update: Connecting paths to the other 60 locations on the map.
  • Add: New recipes for cooking along with new food sources.
  • Add: Bow and Arrow can be crafted to hunt with in certain areas.
  • New: Campfire burns down.
  • New: Add fuel to your camp fire.
17/01/2021
  • Update: Design tweaks to buttons, icons, mobile layout.
  • Add: Option to take a break to regain some energy. Without a shelter there was currently no method to regain energy.
  • New: If you're hunger and/or thirst are below a certain threshold you will start to lose health when doing any kind of activity.
  • New: If you're hunger and/or thirst are above a certain threshold you will start to gain health when resting.
16/01/2021
  • New: Crafting! Still experimental at the minute, but you can now craft a few objects from items found and foraged.
  • New: Recipes! Cooking and Boiling at the campfire just got a whole lot more complex. See if you can make my bread recipe!
  • Fix: Eating All of an item wasn't giving the correct stats.
  • Add: Additional items have been added to the world.
  • New: Added quick stats to bottom of the page.
  • Update: Minor tweaks to descriptions have been made, this is an ongoing task.
15/01/2021
  • Overhauled the travel system, it now includes directions for travel, North, South, East, West. This should aid you in making a map.
  • Expanded the map structure from 9 tiles to 60 tiles. Only 9 are available at the minute while I build up the environments. Each tile is hand crafted, not generated. So I need to tell each tile what can be searched for, and what can be discovered in each tile.
  • Added in energy requirements to travel to certain parts of the man, the mountains will cost more energy than walking along a road for example.
14/01/2021
  • Food and water need to be above a certain point before you will start to heal when you rest.
  • Basic health added, when food and/or water is below 5 you will start to lose health
  • There are currently 2 audio logs out in the wild to find
  • New function added for audio logs
  • Mobile layout overhaul, buttons are easier to press, UI Experience has been vastly improved.
  • Addition of the Journal to read through existing chapters of the game
  • Basic implementation of of chapters
13/01/2021
  • hunger and thirst consumption when doing actions like travelling and cooking
  • Resting at shelter regains energy, but costs thirst and hunger
  • Eat food
  • Drink water, pepso etc
  • Put out campfire
  • Abandon shelter
12/01/2021
  • Basic inventory is operational, you can search and find items, and remove them from your inventory
  • Basic search is operational, you can search and find items which get added to your inventory.
  • Added basic chance system, chance of not finding something in a search
11/01/2021
  • Added location based searches, with that location based items too. Some items can only be found in certain places.
  • Added travel, when in a location, you have options to travel to adjacent tiles.
  • A 3x3 grid map has been created. You can travel to adjacent tiles.
10/01/2021
  • Started to display data in HTML rather than raw var dumps
  • Basic API functions added
  • tested API with 2 functions, build a fire, make a shelter
09/01/2021
  • Added a basic weather system
  • Built a robust system for checking required items for objects. You can just feed a string into a function to get required items shelter.build.leanto for example.
06/01/2021
  • Added a basic html template to the site to start giving it some structure
30/10/2020
  • Some basic functions for checking if items are available in invetory to use this is the very basics of crafting started to think about skill levels for various actions
29/10/2020
  • Started with some basic objects

Stages of development

Pre-alpha

Pre-alpha refers to all activities performed during the software project before formal testing. These activities can include requirements analysis, software design, software development, and unit testing. In typical open source development, there are several types of pre-alpha versions. Milestone versions include specific sets of functions and are released as soon as the feature is complete.

Alpha

The alpha phase of the release life cycle is the first phase of software testing (alpha is the first letter of the Greek alphabet, used as the number 1). In this phase, developers generally test the software using white-box techniques. Additional validation is then performed using black-box or gray-box techniques, by another testing team. Moving to black-box testing inside the organization is known as alpha release.

Alpha software is not thoroughly tested by the developer before it is released to customers. Alpha software may contain serious errors, and any resulting instability could cause crashes or data loss. Alpha software may not contain all of the features that are planned for the final version. In general, external availability of alpha software is uncommon in proprietary software, while open source software often has publicly available alpha versions. The alpha phase usually ends with a feature freeze, indicating that no more features will be added to the software. At this time, the software is said to be feature complete. A beta test is carried out following acceptance testing at the supplier's site (alpha test) and immediately prior to general release of the software as a product.

Beta

Beta, named after the second letter of the Greek alphabet, is the software development phase following alpha. Software in the beta stage is also known as betaware. A Beta phase generally begins when the software is feature complete but likely to contain a number of known or unknown bugs. Software in the beta phase will generally have many more bugs in it than completed software, speed or performance issues, and may still cause crashes or data loss. The focus of beta testing is reducing impacts to users, often incorporating usability testing. The process of delivering a beta version to the users is called beta release and this is typically the first time that the software is available outside of the organization that developed it. Software beta releases can either be public or private, depending on whether they are openly available or only available to a limited audience. Beta version software is often useful for demonstrations and previews within an organization and to prospective customers. Some developers refer to this stage as a preview, preview release, prototype, technical preview / technology preview (TP), or early access. Since the introduction of Windows 8, Microsoft has called pre-release software a preview rather than beta. All pre-release builds released through the Windows Insider Program launched in 2014 are termed "Insider Preview builds". "beta" may also indicate something more like a release candidate, or as a form of time-limited demo, or marketing technique.

Beta testers are people who actively report issues of beta software. They are usually customers or representatives of prospective customers of the organization that develops the software. Beta testers tend to volunteer their services free of charge but often receive versions of the product they test, discounts on the release version, or other incentives.


Change Log

22/01/2021 19/01/2021 19/01/2021 18/01/2021 17/01/2021 16/01/2021 15/01/2021 14/01/2021 13/01/2021 12/01/2021 11/01/2021 10/01/2021 09/01/2021 06/01/2021 30/10/2020 29/10/2020

Stages of development

Pre-alpha

Pre-alpha refers to all activities performed during the software project before formal testing. These activities can include requirements analysis, software design, software development, and unit testing. In typical open source development, there are several types of pre-alpha versions. Milestone versions include specific sets of functions and are released as soon as the feature is complete.

Alpha

The alpha phase of the release life cycle is the first phase of software testing (alpha is the first letter of the Greek alphabet, used as the number 1). In this phase, developers generally test the software using white-box techniques. Additional validation is then performed using black-box or gray-box techniques, by another testing team. Moving to black-box testing inside the organization is known as alpha release.

Alpha software is not thoroughly tested by the developer before it is released to customers. Alpha software may contain serious errors, and any resulting instability could cause crashes or data loss. Alpha software may not contain all of the features that are planned for the final version. In general, external availability of alpha software is uncommon in proprietary software, while open source software often has publicly available alpha versions. The alpha phase usually ends with a feature freeze, indicating that no more features will be added to the software. At this time, the software is said to be feature complete. A beta test is carried out following acceptance testing at the supplier's site (alpha test) and immediately prior to general release of the software as a product.

Beta

Beta, named after the second letter of the Greek alphabet, is the software development phase following alpha. Software in the beta stage is also known as betaware. A Beta phase generally begins when the software is feature complete but likely to contain a number of known or unknown bugs. Software in the beta phase will generally have many more bugs in it than completed software, speed or performance issues, and may still cause crashes or data loss. The focus of beta testing is reducing impacts to users, often incorporating usability testing. The process of delivering a beta version to the users is called beta release and this is typically the first time that the software is available outside of the organization that developed it. Software beta releases can either be public or private, depending on whether they are openly available or only available to a limited audience. Beta version software is often useful for demonstrations and previews within an organization and to prospective customers. Some developers refer to this stage as a preview, preview release, prototype, technical preview / technology preview (TP), or early access. Since the introduction of Windows 8, Microsoft has called pre-release software a preview rather than beta. All pre-release builds released through the Windows Insider Program launched in 2014 are termed "Insider Preview builds". "beta" may also indicate something more like a release candidate, or as a form of time-limited demo, or marketing technique.

Beta testers are people who actively report issues of beta software. They are usually customers or representatives of prospective customers of the organization that develops the software. Beta testers tend to volunteer their services free of charge but often receive versions of the product they test, discounts on the release version, or other incentives.