/ Not Meant to Survive: A LitRPG Settlement Survival Story / Chapter 62 — The First Great Project

Chapter 62 — The First Great Project

1788816024

Mark went and talked to Tom and Dale about the new Regional Infrastructure Project opportunities. Dale and Tom both thought they were pretty cool, and they all disagreed on which one should be done first. Most options would take more than a month, require a team of 10+ people, and consume a huge amount of resources.

They decided the best idea would be to call a meeting of all the major groups in the area. They decided maybe first thing in the morning, and they could send runners out with the time and have them gather for breakfast.

With time to kill, he looked around the outpost at all the changes. The longhouse had been completed, and they already had all 10 beds booked out for the next month. They were charging system credits for room and board. The cookhouse was finished this morning, and Dale was moving all his supplies in. There was room for 10 to eat inside and tables out and around it that could feed another 15–20 in a single sitting.

Dale now had two assistant cooks and a busboy/dishwasher to help. His food was in high demand. He fed those who lived in camp, and many people visited from the other outposts every day or two for his fantastic cooking.

The cabins were now under construction. There were going to be 3 of them. Tom and Dale planned to share the first one, with each having a room and a sitting room they shared. There was also a loft that the two kids planned to share.

Mark was told one of the cabins was reserved for him with a room, an office, a sitting room, and a loft, but only for him. He was still fighting this, as he did not think he needed his own cabin; he could share or sleep in a tent for all he cared. The third cabin had 3 rooms and a loft, and so far they were planning on putting Ava in there and had room for more. Cora and Lena were planning to move to Wayrest when the first longhouse was done and either stay there or build a cabin of their own somewhere in the woods.

There was a crowd at the tables outside the cookhouse when the meeting began. Mark began explaining the regional infrastructure opportunity message. He brought up the message and read it to the group.

[Regional Infrastructure Opportunity Detected]

Settlement development thresholds reached. Only one Regional Infrastructure Project may be active within a controlled zone at a time.

Projects require assigned personnel, sustained contribution investment, and long-term regional support.

Available Projects:

Sanctioned Forgeworks

Regional Road and Bridge Network

Infirmary and Alchemy Workshop

Warning: Beginning a project will heavily affect regional reserves and available labor.

◈ ◈ ◈

He went on to explain the detailed information he received when he opened each of the three projects, reading every option to the group.

[Project Option: Forgeworks]

Estimated Time: 35 Days

Personnel Required: 10 Assigned Workers

Requires large supplies of stone, hardwood, charcoal, ore, water access, and regional contributions.

The tale has been taken without authorization; if you see it on Amazon, report the incident.

Projected rewards include a sanctioned forge, basic equipment and manuals, furnace knowledge, and expanded metalworking professions.

◈ ◈ ◈

[Project Option: Regional Road and Bridge Network]

Estimated Time: 50 Days

Personnel Required: 12 Assigned Workers

Requires timber, stone, survey teams, bridge materials, labor, and regional contributions.

Projected rewards include reinforced roads, stabilized crossings, wagon and bridge plans, and improved regional travel.

◈ ◈ ◈

[Project Option: Infirmary and Alchemy Workshop]

Estimated Time: 30 Days

Personnel Required: 8 Assigned Workers

Requires herbs, clean water, medical storage, healers, specialized labor, and regional contributions.

Projected rewards include medical facilities, herbal preparation manuals, basic alchemy knowledge, and improved recovery.

◈ ◈ ◈

Mark was really surprised he got through reading the full list before the fight started. Everyone had an opinion on which one was the most important. They talked about recovery from the fight and the wounds they had. Others talked about tools, weapons, and building supplies for the forgeworks. Others fought for the trail network.

They all had various costs and benefits, so even Mark could agree that each and every one of them would be used and, in some ways, needed. The first option they removed from the list was the Infirmary and Alchemy, both of which Mark felt were good options, but it boiled down to the fact that they did not even have enough people with those classes to support the initial 8 required personnel.

The debate went on for three hours until, through a series of votes, they decided that the Forgeworks would be the best upgrade at this time, and everyone agreed when it was completed they would check to see if there were more options or the ability to do one of the other two.

Mark brought up the screen to select the Forgeworks as their first great project. Before clicking the button, he scrolled through the list of items that would be removed from the contribution store and outpost inventories; there was not a single outpost in the area that did not have something substantial being taken for this opportunity. Mark guessed that just over half of all the resources they had gathered were going to be taken in just the next click of a button.

There was a general system message sent to every person in the zone.

[Project Started]

Project: Forgeworks

Category: Regional Infrastructure

Estimated Duration: 35 Days

Assigned Personnel: 0 / 10

Available Tasks Generated: 12

◈ ◈ ◈

As Mark looked at the message, the available tasks counter kept going up. He finally closed the screen when it passed 150. He then opened the tasks screen and saw that there was a new task category called Regional Infrastructure, and it had lists of jobs, tasks, and resources needed. Mark filled in on the system that the location of the Forgeworks would be at the Cave Camp outpost, and he was able to pick and align its location on the map.

He went to the Assigned Personnel page and clicked the apply button. He instantly received an applicant-rejected message, followed by a list of classes that could apply, none of which he had. As he was puzzling over his rejection message, he saw John’s name pop onto the list and his position title and responsibilities listed. Then 2 more names popped onto the list, and Mark was not familiar with either of them.

He went over and talked to John, who was sitting at the table and was part of the discussion and, of course, led the push for this project. He told Mark that after he selected the button, he received a system notice that he was eligible for one of the assigned personnel options.

The system gave him a contribution signup bonus and a list of personal rewards he would get upon specific milestones that would need to be completed along the path to full completion of the project. He also mentioned that the final reward upon completion of the project would be a class upgrade/evolution dependent on performance in his role.

Mark brought back up the progress page, and it indicated that 6 positions were now fulfilled and over 250 tasks had now been created.

As Mark sat there, he realized that activity throughout camp had stopped. People everywhere were reviewing the new regional task list.

Mark decided to look for a task he could help with. The list covered everything from clay delivery and charcoal production to hauling stone, gathering ore, digging foundations, and trading with distant villages. When he tried accepting a trade request, the system told him he was not qualified.

He eventually found the filter for tasks suited to him. At the top of his list was repeatable water delivery, with compensation based on the amount delivered. Mark laughed, closed the screen, and decided he needed breakfast.