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.

Campfire

Make a fire


Fire with matches


Required

Energy x10
Matches - 0/1
Tinder - 0/1
Sticks - 0/10

Start a fire with some matches. Quick and easy.



Fire with lighter


Required

Energy x10
Lighter - 0/1
Tinder - 0/1
Sticks - 0/10

Start a fire with a lighter. Quick and easy.



Fire with Firesteel


Required

Energy x50
Firesteel - 0/1
Tinder - 0/1
Sticks - 0/10

The piece of steel that never expires. This item can light 10,000 fires.



Fire with Fireplough


Required

Energy x300
Fire Plough - 0/1
Tinder - 0/1
Sticks - 0/10

Huge energy consumer. But if there's no other option, rub these pieces of wood together.



Fire with Bowdrill


Required

Energy x300
Bow Drill - 0/1
Tinder - 0/1
Sticks - 0/10

A skill that requires time to master, creating fire with friction has been used for hundreds of years




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.