Lore ideas for my map!

greetings :waving_hand:

I need some lore ideas for my map “Trust No One”. you might’ve seen the thumbnail request already
Here is a summary of the game: 8 gims were on EchoShip-34, and suddenly it crashed into GIMKON HQ, and one of the gims was the sabotager who crashed the ship. The innocents have to do jobs to restart the ship and fly back.

the lore can be like Among Us if you want, like how the imposter was affected by a parasite or something

Thank you for everybody’s ideas!

2 Likes

The gims were flying to planet earth to discover new lands and find new signs of life. They aren’t researchers, they are just finding a way to see a planet, and settle there. The gims face a captain, who commands them to search until they find planet earth’s location. When they did, they started to fly there from space. Everyone seemed unsure. Until when everyone was on lunch break and the ship was on auto-piliot, a mystery gim heads inside and crashes the ship onto GIMKON HQ, a place on planet earth they weren’t trying to land on. The HQ wasn’t damaged as bad as the ship, and everyone scattered to find the mystery gim. When they were unsuccessful, they started to repair the ship.
The mystery gim finds themselves wrapped around a cloak, and when the cloak removes itself, the mystery gim changes back to its normal self, unaware of what happened. Little did the gims know the source of the evil that was about to come…

Hope you likey :D.

7 Likes

On the fourth planet in the Gondo System in the Commonwealth, or Tyr, far away in space, a group of 8 gims decided to leave their home. The Commonwealth told them it was not something they were not allowed to do, but they ignored them. They stole EchoShip-34 from the dockyards there, and escaped. Little did they know, one of their crew members was a Commonwealth agent. His goal was to eliminate the group and prevent them from escaping from them.

They traveled for a long time, and weird things began to happen slowly on the ship. Things started to malfunction, and the cause was unknown. Everyone said they did nothing, and no culprit was found.

However, once they reached a new planet, the ship had been sabotaged fully and crashed there. They landed at GIMKON HQ, with no idea of where they were. It was an unchartered part of space, not in the Commonwealth’s knowledge.

4 Likes

A bit of a generic theme, but the only decent Lore request I’ve seen in a while, so I’ll give it a whirl:

Trust No One (Rather bland, but the least boring prompt I received in a month)

Having just launched on its maiden voyage, the crew of the EchoShip-34 were ecstatic, as they had been given a milk run, just a simple inspection of some outlying systems in the northern sector of Echo territory. The most recent skirmishes with Vortex being on the southeastern border, it was incredibly unlikely they would encounter any danger, and they got to use the first frigate of the Voyager class starships that Echo had been developing for the past decade. If only they knew how quickly their peaceful hopes would be dashed…

Nine days into the voyage, about two thirds of the way to the Echo research outpost, they suffered critical engine damage due to an expl0sion of unknown cause. With all the technology and funding poured into the design of the vessel, system malfunction was unlikely, but the crew was hesitant to jump to the obvious alternate cause of sabotage. Regardless, such thoughts had to be put on hold once it was clear there was no salvaging the shattered machinery. As the ship began barreling through the atmosphere of a nearby planet known as Chrystantia, the crew rushed to the escape pods as klaxons blared and cast a pale red light onto the rumbling floors. All pods launched in time to save the crew, but the planet they were landing on was quarantined, and had been listed as a no fly zone within the Echo database. All the crew glimpsed as they plummeted towards the earth was a strange gray building shrouded by a verdant forest, the jade green leaves rushing up to ever greater prominence in the pods window until

CRASH

As the survivors crept from their pods, they emerged into an eerily silent landscape. They all had fallen within the grounds of what appeared to be an abandoned research facility, electric fences and dense foliage caging them in from the north, east, and west, and a sheer cliff dropping to a rushing series of rapids in a valley far below acting as a natural barrier to the south. How power was still active was unknown, perhaps through some form of solar or nuclear energy, but it seemed very unreliable, with lights flickering and doors sealing shut at random intervals. As the system’s star fell below the horizon, the surviving crew formed a small encampment for the night, intending to explore the ruins in the morning.

As dawn broke over their refuge, they split off to search the nearby buildings in hope of finding a way to request rescue, or to find a way off the planet for themselves. A brief walk around gave a basic layout, and presented serious concerns. Not only were the electrical systems in a state of disrepair, but the ship’s wreckage had crashed into the reactor chamber, putting it at risk of meltdown. Furthermore, the planet’s atmosphere was found to be incompatible with Gim biochemistry, and they had only survived due to the oxygen tanks in the suits they donned in the escape pods. Thankfully the base had a machine to refill the canisters, but were it to fail they would all perish in a matter of hours. On a positive note, it seemed that the communications array, while broken, could be repaired if the Gims fixed up ancillary systems around the base and collected wreckage from their fallen ship. Faced with a list of tasks essential to both immediate survival and long term escape, they might have been able to manage them long enough to signal aid. However, they soon realized the Captain had not yet returned from exploring. Searching, they spotted his body tucked away in a corner of the electrical room, confirming in an instant their fears of a traitor. Suspicion and mistrust sowed between them, they agreed on a basic procedure should further incidents be discovered. If a body is found or you feel threatened by a number crew member, you are to use a walkie talkie to call an emergency meeting. Should someone be suspected as the traitor, the crew may vote to shove them off the southern cliffs for their betrayal.

Lore for Imposter and the crew’s true mission
(This can be revealed through hidden papers and when the imposter receives their role.)

While the 8 surviving members of the crew believed they had been tasked with a basic expedition to a research outpost, their mission carried far more importance than all but the Captain realized. Upon arriving on the bridge, the Captain received a coded transmission from Echo High Command about their journey’s true purpose. The planet the crew would pass on the way to the outpost was quarantined due to an aggressive hive mind discovered amongst the planet’s flora. The base the crew crashed into was an abandoned research outpost, as Echo scientists had isolated a compound within the plants responsible for their regenerative capabilities. Dubbed as Chemical X, it would serve as a powerful tool for maintaining the frontline forces in contested planets, and very well could determine the outcome of the most recent Echo/Vortex War. Unfortunately for Echo, a Vortex agent was part of the research team, and they managed to send a transmission on Echo’s findings before being captured and… taken care of after interrogation. Echo High Command lost contact with the secondary outpost the team moved to due to the inhospitable conditions of the flora’s homeworld. It was suspected that a Vortex strike force was laying siege to the base, and the EchoShip-34 was sent in order to quickly rescue the scientists and samples of the Chemical. Apparently screening for Echo’s military is incredibly bad, for it turns out a second Vortex agent was planted within the ships crew shortly before launch, transferred in as a secondary mechanic. This role granted them easy access to the engine room, allowing them to sabotage the ship mid-voyage. However, things didn’t go as planned for them either, as the ship was captured by Chrystantia’s gravitational pull instead of being stranded in space for boarding by Vortex forces. The infiltrator wanted to repair the base’s comms as well, but required a different set of resources to access Vortex frequencies, the gathering of which would reveal their identity to the other crew… if they were still alive. They quickly isolated the Captain for elimination so as to prevent the crew from ever finding out why they were targeted, and began tinkering with the decrepit electrical systems to create remote access to door and power controls, enabling them to threaten all of the crew with malfunction of essential systems, or to isolate specific members behind closed doors and darkened rooms.

9 Likes

Steal the plot of the first Alien movie

1 Like

Dang @King_Thunder_Alt1 you aced all of that!

Anyway, what does lore mean? I could help.

2 Likes

What kind of lore do you want? I’m good at hidden notes, and things like that.

2 Likes

Cooking up something for this rn . . . It should be ready soon!

Don’t worry It isn’t subnautica

3 Likes

I could try this =/
So basically the 8 gims were on the ship as air patrol. Their job? Patrol the surrounding areas of HQ for Vortex scouts or just anyone related to Vortex. Little do they know a Vortex agent managed to slip under their radar and become one of them. The sabotager. (woahhh) The sabotager then does some “accidental” mumbo jumbo stuff (Which totally wasn’t just pressing the big red button that says “SELF DESTRUCT DO NOT PRESS UNLESS IN CASE OF EMERGENCY”) and causes the ship to crash directly into HQ making them obliterate what they wanted to protect. Unfortunately the crash mayyyyy (yk mayyyy) have completely ERASED the entire HQ. So now they have to fix the ship so they can use it as their new HQ since it’s just easier to fix a ship that’s partially damaged than MAKING an entire new giant building. And now they gotta fix it fast because Vortex comes closer and closer to them while they still have their sabotager among their ranks. And they also can’t get help from anyone else because EchoShip-34 was the only ship close to HQ. So now they have to either try to fix and defend their ship from Vortex, or hope that other Echo agents come to save them.
Welp that’s all I have. Hopefully it was helpful in some way and if not, hopefully ya liked it. =P

6 Likes

Do you need more lore or have you gotten an adequate amount?

1 Like

thats an adequate amount, thanks for the lore!

lore is basically just a backstory of how things happened

@Fireball any lore is fine

1 Like

Gimkon hq, a massive multi terrestrial investigation center and megastructure with a large, dome shaped glass containment unit in the center that stretches for miles, simulating alien ecosystems for the gims to run tests on, was sabotaged by a rival corporation, Kit tech united. An assassin/super spy was employed by them to destr0y Gimkon’s space vessel before it took off, but they fa!led in the attempt, and had to destr0y it middair. the ship (EchoShip-34) crashed down, breaking through the dome and into the middle of an alien ecosystem. since it was so large, It would take days for rescue to come. So, the survivors had to escape the dome. while at the same time figuring out which member of the party was the KTU assassin. If they manage to reach the edge without the assasin knocking them out, then they return to GK HQ, which underwent a hostile takeover while they were gone. they now must defeat the KTU agents along with the assassin and then board a helocopter, take it to KTU HQ and defeat them once and for all.

2 Likes

Thank you everybody for the lore ideas! It helped me a ton!

Which one(s) are you going to use?

I’ll try mix everybody’s lore ideas into one, so i’ll use everybody’s

1 Like

Hate to prevent this from closing, but is it really fair if your using everyone’s story and only one person gets the solution?
I honestly wouldn’t have minded if you selfed this topic. No one person did the full credit in this situation.

Edit: Got it!

2 Likes

U should probs mark KT as a solution then since he made josh knows how many paragraphs for your lore

That or he chose the shameful route of AI, which is highly unlikely

@Scary_Friend bro u did the same thing :roll_eyes:

@ForsakenGD?

3 Likes

reaper bro it was bouta close :pensive_face:

sigh.

ill leave it up to op

2 Likes

This topic was automatically closed 3 hours after the last reply. New replies are no longer allowed.