Search Requests

[glencolans]

SEARCH REQUESTS

At game start, the map is completely unexplored and covered by a "fog of war" obscuring its features. New characters will be randomly dropped onto the island's shores; from there, to uncover tiles on the map and figure out more about where they are, search requests are required to document movement, attempt to uncover hidden materials and passages, discover or confront dangers, find old ruins and create new settlements, and potentially, solve puzzles related to the mystery of the island itself.

RULES AND GUIDELINES

• Search requests are a required mechanic of this game. A search request for the current AC cycle must be submitted in order to pass AC without a strike.
• Mistakes in search requests will never be penalized. Don't be afraid to eyeball a distance or make an approximate guess; if the math doesn't quite match up, or the path doesn't exist, I will offer alternate destinations and work with you in order to decide how the search request will resolve.
• Search requests will rarely be immediately fatal. Unless your character is doing something intentionally reckless, I will do my best to offer paths of escape for any sudden dangers that arise.
• You can be as precise or as vague as you want. If you want to exactly plot out the squares your character will travel through and search every IC day, that is totally fine. It's also fine to simply report that your character is staying in one place all month, or to give a starting point and a desired destination, with a general request to search a wide area. Just note that, the more vague you are in your request, the more I will extrapolate to fill in the blanks.
• Retroactive/backdated search requests are allowed. They just can't be used for the current month's AC if they fall outside of the current month's AC period, or overwrite a previously submitted search request. Forward-dated search requests are also allowed as long as they fall within the same IC day that the request was posted (for example, if you post a search request on IC Day 30 morning, you can make that search request last for the entirety of IC day 30, not just the morning of).
• Thoroughly searching a square, rather than just traveling through it, halves movement through that square. So if you choose to search every square along a path, you'll only travel half as far as someone moving with purpose to a destination. Remember that simply traveling through a square will still fully reveal it.
• IC Days are split into three 8-hour increments. Each of these corresponds to one OOC day. Morning is from 4AM -> 11:59AM, Day is from 12PM -> 7:59PM, and Night is 8PM -> 3:59AM.
• Several examples of search requests are provided below to help illustrate how they work. If you still have questions, please ask them in the FAQ (or in your search request!).

MAP REFERENCE/TRAVEL CONDITIONS

TRAVEL CONDITIONS | IC DAYS 15 → 17

MORNING

DAY

NIGHT

BEACH

OCEAN*

JUNGLE

FOOTHILLS

MOUNTAINS

4 squares/hour
(32 total)
3 square visibility

4 squares/hour
(32 total)
5 square visibility

4 squares/hour
(32 total)
1 square visibility

2 squares/hour
(16 total)
3 square visibility

2 squares/hour
(16 total)
5 square visibility

2 squares/hour
(16 total)
1 square visibility

2 squares/hour
(16 total)
1 square visibility

2 squares/hour
(16 total)
1 square visibility

1 square/hour
(8 total)
0 square visibility

2 squares/hour
(16 total)
2 square visibility

2 squares/hour
(16 total)
3 square visibility

1 square/hour
(8 total)
1 square visibility

1 square/hour
(8 total)
5 square visibility

1 square/hour
(8 total)
7 square visibility

1 square/hour
(8 total)
3 square visibility

*The average human can only tread water for three hours

LEGEND

- Preexisting Structure

- Ocean

- Reef

- Deep Water

- River

- Natural Landmark

- Beach

- Jungle

- Mangroves

- Character-Made Landmark

- Foothills

- Mountain

Click on any of the map tiles for details.

I

II

III

IV

V

VI

VII

VIII

IX

X

XI

XII

XIII

XIV

XV

XVI

SUBMISSIONS

# | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z
All new characters will be given a toplevel to this post. To submit a search request, fill out the below form and copy/paste it as a response to your toplevel.

<b>IC DATES:</b> <b>STARTING SQUARE:</b> <b>ENDING SQUARE:</b> <b>DETAILS:</b>

IC DATES: The IC dates the search request covers (I would also recommend putting this in the subject line to make it easier to keyword search later). You can use whole days, partial days, or a combination of either. To verify what IC days line up with real-world days and events, consult the Calendar.

STARTING SQUARE: The square your character is starting their search request on, format TILE.COLUMN.ROW. This should line up with your previous search request, or your starting location if newly arrived/revived.

ENDING SQUARE: The square your character is ending their search request on. If you're not sure where they'll end up (the area is unexplored/your character has a vague idea of where they want to go/you're not sure on the math/etc.), you can give a more rough answer here. Something like "they want to make it to Tile II," or "as close to II.AA.3 as possible" are perfectly valid answers.

DETAILS: The meat of your request. This is where you describe:

1. The path your character is taking,
2. The squares you want them to search,
3. Any special actions your character is taking during this period of time (or inaction), and
4. Any other special notes or questions you might have about this request.

Again, you can provide as much or as little information as you want; saying that your character is simply moving from point A to point B without searching anything is 100% acceptable.

NAVIGATION

Comments

[glencolans]

If she takes it out, the menu and all of her nicknames/saved callsign groups disappear. They do return as she left them if she plugs it back in. However, her changed callsign stays as she left it even after she removes the module. A conversation saved with a name cannot be accessed 24 hours later, and the Callsign Group also has the 6-character limit.

I had considered something like this would happen lol - for everyone's sanity, please only log changes that you intend to keep semi-permanent. You can still do things like temporarily change her callsign mid-conversation in a public network thread without having to make a note of it.

[ichoosefight]

If she plugs it back in, are the saved conversations and other people's callsigns erased? I'm assuming she's the only one who sees those, but do they transfer if it's plugged into someone else's transceiver?

Can she use other people's callsigns???? Are there any restricted characters?

[glencolans]

If she plugs the module back in, the named conversations only reappear if they are 24 hours old (or more specifically, the messages within the conversation that are within 24 hours old reappear; if all messages in the conversation are more than 24 hours old, the entire conversation disappears, module or otherwise). The nicknamed callsigns return to the last names Steph assigned them. She is the only one that sees the nicknamed conversations/callsigns/groups, and they do not transfer if someone else plugs in the same SD card to their own transceiver.

Nothing will stop Steph from reassigning her callsign to someone else's callsign, either existing or dead/missing. If she does, she'll quickly discover that she can see and receive private messages intended for that callsign. The owner of that callsign, if they are still alive, will also still see and receive those messages; however, if a person with a copied callsign tries to receive or view incoming messages of any type, they will hear an annoyingly loud feedback noise that sounds no matter how far they have their transceiver's volume nob turned down. Please coordinate with players before copying their characters' callsigns and respect their permissions on mimicry.

[ichoosefight]

Are there any restricted characters, or can she use spaces, ?!@#$% etc?

Does the feedback noise happen only when the OG callsign opens a message, or as soon as it's received? I assume this means they can't hear spoken messages? Can they still read text messages? What happens if they try to send a message? Is there a way for the OG callsign to see that their own callsign has sent a message?

[glencolans]

Numbers and letters only; special characters and spaces will kick the user back to the nickname entry popup without an error message.

The feedback noise happens when the OG callsign both receives and opens the message (since the transceivers beep whenever a message is received by default). They can still hear spoken messages when they receive them/try to play them back, it's just that they hear a loud, crackly noise right at the starts of them, with some staticky background noise as the message itself plays. They can still read text messages without noise, although they will get the same feedback when text messages are received.

Someone with a copied callsign can send messages with no issues. They can also see if someone else is sending messages under their callsign; messages sent from another transceiver, even one copying their callsign, will still register as a new incoming message in a conversation (so it will feedback-beep every time), and will show up in conversation logs as if they had sent it.