At the time being, neXus's movement of time is uncharted to allow maximum freedom to you as an RPer. The board does not implement any type of time stamp that forces your character(s) to be hours ahead of others, minutes behind someone, or perhaps even days in the future or past.

There's really only one thing you need to know:
All current threads happen at the same time as other current threads.

There's been discussions and debates over certain threads being during the time of day, or other threads in the same area happening at the same time, being at night. There's two basic options you can choose from to alleviate that argument:

A: Simply ignore the time of day discrepancies from thread to thread. You'll find out the majority of RPers here at neXus don't mention whether or not it's day or night (or even react to the time of day), simply because most of the time, it's irrelevant to whatever's going on in the thread. If you wish to use it, that's fine, but realize just because it's night in your thread doesn't mean someone else has to say it's night too. Be weary of time specifics. They may mess up a thread if implemented too specifically.

B: If you want your thread to be at dawn in a unified time structure, realize that would force everyone else to be at dawn as well in the same area. Which means the person currently shopping at a clothing shop in New York City would be forced to leave because the clothing shop would have been, technically, closed, and the character couldn't have been shopping to begin with. The person that was currently thieving in the dead of night couldn't have been thieving in the dead of night because, thanks to you, you say it's dawn.

All that could be bypassed if a structured time occurred, yes, but let's realize a few things:

A: For those traveling, they'd be forced to wait on your characters, which meant if a single hour was equal to 24 hours in real life--the characters traveling would have to wait for *days* to pass, in real life, in order to RP again. That's not fair to anyone.

B: Character inactivity can drastically slow down a thread, which would force certain characters to be hours behind other characters. If twenty-four hours past in real time, and all your character did was say hi to someone, would that be realistic of someone simply standing there and saying hi for an hour? Fight threads act in the same way. Realistically, a fight wouldn't last any longer than a half hour, but may very well take months, in real time, depending if the fight is in a plot oriented thread.

Why not just have time delays or a single character in multiple threads? I can answer that question in one answer:

A: A battle has started, with different characters, which realistically only lasted thirty minutes, starting at 1 PM. Your character, time wise, is well beyond that thirty minutes and is currently at 3:30 PM. Your character would have no choice but to RP not knowing the outcome of the battle, simply because in the game, no one knows the consequences yet. But yet, you're in the future in the RP, and you should *know* those consequences, but don't. If your character is in that battle at 1 PM, but also in the future at 3:30 PM, you can't possibly predict how the outcome of a battle is going to happen, and as such, don't know if your character is injured or not at 3:30 PM.

Just because time isn't charted does not mean you have free scope to do whatever you wish. Time exists, just it's fluid and goes uncharted. As players pointed out, you have to go to the hangar to hop on a jet in NY before you can end up in Mexico. NeXus simply skips the time in which it takes to get from Point A to Point B. Time exists. Characters are constantly saying, "He/She stayed quiet during the ship's flight." Characters aren't sporadically healing from a broken arm within the next post, but we also don't expect that arm to be broken forever since time is uncharted.

Essentially, use your best judgement. Know time exists, but it's fluid, which means every thread that's currently happening happens at the same time as others.