Guidance & Rules

Wander is a Star Wars Jedi Knight: Jedi Academy roleplaying community set shortly after Order 66.

The core story follows an ensemble cast of characters as they adapt to a galaxy that shifted seismically overnight.

Set in real time, where one day in the real world is one day in-universe, Wander champions immersive storytelling, rich character development and collaborative content creation.

Our website and timeline can be found at: https://www.wander-rp.com

This documentation and guidance is new and will be updated as players engage with it, ask questions and roleplay.

Recommended Reading

About

• Our Vision
  • Ethos
  • Goals
• Core Mechanics
  • Give and Take
  • Date and Time
  • Wandering
  • The Beacon
  • TW-W2
  • The Whole Story
• Community Structure
  • Membership & Structure
  • Management
  • Disputes
• Rules and Guidelines
  • Community Rules
  • Code of Conduct
  • Rules
  • Roleplaying Rules and Guidance
• Getting Set-up

Roleplay Information

• The story so far...
• Locations
  • Wandering
  • The Beacon

Joining

• Character Creation
• Joining Process

Help/Questions

• Glossary

Ethos

The mindset we want to apply when thinking about and contributing to wander.

'Our' Story

The central timeline is at the core of Wander, capturing every part of our story.

Whilst characters move in and out of focus, experiencing moments of attention and great distinction, Wander remains rooted in the idea that the whole is greater than the sum of its parts, and that no great character can exist in isolation.

Every roleplayer is collectively responsible for advancing Wander's story, both by taking part in stories and events and by creating them.

Always Improving

Wander utilises roleplay mechanics specifically tailored for Wander.

Some are untested and when put into practice may need to be tweaked.

Wander must remain open to making changes to mechanics and requirements to deliver on its wider ethoese and goals.

We must be careful not to inadvertently mould or change mechanics simply because of familiarity or individual preference.

Flexibility

Wander is designed with the natural ebbs and flows of life in mind. Wander's story isn't exclusively told in-game, with roleplay possible over Discord and individually through journals.

The 'Wandering' mechanic means when players have limited time to engage, their characters aren't disproportionately impacted, and their absence is easily explained.

Those who can and wish to roleplay in-game regularly can do so through 'The Beacon' mechanic.

Good Faith & Trust

Stories are subjective and disagreement over direction, subject matter or interpretation of lore is natural in roleplay.

When disagreements arise, everyone is expected to engage in good faith and with the collective understanding that everyone simply wants the best for roleplay and Wander.

Direction and subject matter are entrusted to the Wander member leading the storyline, and as long as it follows the rules and guidance, they have final sign-off.

For matters of lore, options that maximise storytelling should always be sought.

Wander does not utilise a strict XP system. New characters are given a generous grant of XP on creation and trusted to build a template reflective of their character.

Goals

The actions and practical approaches that will help Wander grow.

Rich and Character-Focused Roleplay over Quantity, Assets and Infrastructure

• Character-driven roleplay is at the heart of Wander and should not be compromised on. Everyone needs to be in-sync with this goal, even if that results in limited member numbers.
• Asset creation and acquisition should only serve to enhance roleplay, never to prevent it or act as a long-term distraction.
• Additional infrastructure must serve an immediate and obvious purpose to Wander. If its benefit cannot be explained simply it should not be pursued.

Consistent Activity

• Create a sustainable routine of roleplay and activity that progresses characters and storylines across the three mediums available to roleplayers (in-game, Discord and the website).
• Note: Consistent does not necessarily equate to high activity/daily activity.

Document It

• Have a preserved record of Wander, its characters and the stories told.
• Make the timeline adaptable and easily updatable through Discord or other medium. Build scalable timeline updates, so updates to the site can be just a sentence or image.

Give and Take

Every member of Wander is both a creator and a participant.

Our story only moves forward when people contribute, whether that's organic/unplanned roleplay, directing events, Discord roleplay, or adding to the website.

Life comes first, and periods of increased/decreased motivation and contribution are expected.

Volume is not reciprocal; if you take part in a five-part arc, you do not need to return one of an equal size.

What Wander asks is simpler: when you're enjoying what others create, look for ways to give back that help keep all roleplay outlets moving.

Wandering

Wandering is the default state for characters. In between sessions, characters are assumed to be 'wandering' the galaxy.

In practical terms, it is the simple agreement and understanding that at the end of each RP session, characters will go their separate ways.

This removes the expectation that characters stay and live together between scenes, and with it the awkward impact it can generate:

• Characters who supposedly live together but haven't spoken in some time
• Explaining why another character isn't present when they naturally would be
• Accounting for an absence/low-activity period of a particular character

In-character, Wandering can be anything you deem relevant for your character. It may be travelling the galaxy, or it may be that they simply live on their ship in orbit. You will need to self-generate what your character is doing in between scenes; this can be as detailed as you like.

There may be times when characters choose not to default to Wandering and instead stay together.

Organic/unplanned RP is still encouraged and an important part of Wander. This is done through 'The Beacon' mechanic.

The Beacon

The Beacon is the name of a communal location Wander characters can visit. It is a transient hub for Wander characters and other NPCs to pass through.

It acts as the 'home' map for Wander and is the base map on the server.

The Beacon enables organic/unplanned RP: Wanderers could be passing through at the same time, one character may be temporarily staying at The Beacon utilising its functions, or they could be present to receive a briefing.

TW-W2 resides at The Beacon.

TW-W2 & Events

Events are usually organised ahead of time and are generally narrative-based. They can feature a single Wanderer, multiple, or none at all (see The Whole Story mechanic).

The droid TW-W2 acts as the entity that runs The Beacon and can be used as a medium to brief events on behalf of directors. TW-W2 has access to the following data sources:

• The private journal of Jedi Master Zurli Vivor, a prolific seer who died during Order 66. The journal contains details of her visions, dreams and meditations.
• A tap into encrypted operational Imperial communications and data
• Galactic Holonews, social media and television channel feeds
• An old unmonitored channel used for requesting help from the Jedi Order.
• Additional sources can be added and discussed

Unless stated otherwise, it is assumed that characters can be in any location for an event. Mission/scene directors can place your character in a location, possibly with other Wander characters, and collectively you will need to generate a reason for being there.

Assuming the RP session is organised ahead of time, this is ideally decided before the RP actually occurs.

Story Hooks

Characters can have up to five Story Hooks.

These are elements of your character’s backstory, relationships, ambitions, or unfinished business that other Wander members can use as starting points for storylines involving your character.

Story Hooks give the wider community complete creative control over how that hook develops so only choose aspects of your character’s story that you are comfortable opening up.

The Whole Story (Time-bending and non-Wander roleplay)

Wander encourages roleplayers to tell as much of the story as they want.

This includes past events, for example:

• Events from the Clone Wars
• Assignments with their mentor
• Life at the Temple

It also includes events that focus on Supporting Characters and don't include a main Wander character.

The only requirement is that the roleplay ties back to a main character or storyline.

Occasional true stand-alone pieces are permitted but broadly should be few and far between. This is not applicable to written news stories, which can be completely stand-alone.

Date and Time

One day in the real world is one day in Wander.

Time is still flexible. If a set of missions takes place over three days but takes a couple of weeks to run, date those events from when the roleplay finishes, or from the run-up to the final event.

Where real-world time would get in the way, such as long-term injuries or travel, you are free to bend it, so long as the result stays believable.

Wander uses the Galactic Standard Calendar (GSC). In-character, years are counted from the founding of the Republic. Dates follow the real-world calendar and are written as GSC 253YY-MM-DD:

• YY: the last two digits of the real-world year
• MM: month
• DD: day

For example:

• The Clone Wars began on GSC 25323-04-30 (30th April 2023)
• Order 66 took place on GSC 25326-05-19 (19th May 2026)

Time of day can be changed freely to suit the roleplay. The server operates a 20 hour day cycle to create some natural variation of day/night across different time zones.

When events are organised the discord @time function should be used. This built in feature automatically adjusts the time and date posted to the readers timezone.

Membership & Structure

Wander membership is currently capped at around 10 members. 

The intention is to steadily grow to around 12 members, with a hard cap of 16.

The member cap is designed to enable a richer, more focused story, set around a smaller group of characters, whilst reducing the need for extensive community management.

Recruitment is currently open.

In-character (IC)

In character, all player characters are equal.

The era Wander is set in and the character requirements mean there are no higher/lower ranks between main characters.

Out-of-character (OOC)

Out of character, there is a two-tier structure (Leader & Community Member), with additional roles of 'Clerical Admin' and 'Beacon Operative'.

Leader

Leader: Turgle Oom (known OOC as 'Iffo')

The creator of Wander and its infrastructure.

Statement (last updated: 03/10/26)
"My vision and plan for Wander has formed slowly over a number of years, so I'm excited to finally have everything in place to give it the maximum chance of succeeding.

In the early stages of Wander, I will aim to put decisions to the community, but that may not always be possible. As we find our feet, adapt and discover what does and doesn't work, we must have a clear single vision of what Wander should aim to be. I might not always get it right, and in those moments I ask for patience and understanding.

My long-term goal is to ultimately build a community of like-minded individuals to the point where Wander becomes self-sustaining, decisions become democratic and community administration is as automated as possible.

I can't wait to see what we do with this project."

• Iffo

Community Members

A member of Wander: someone who has gone through the application process, been invited to join and accepted that invitation.

Everyone is equal, and all votes in clan matters carry the same weighting.

They have full admin access to all the server story tools, and full access to post to the website as their character and submit events, news stories and lore entries.

Community members utilise the core mechanics to advance Wander and its storylines.

Clerical Admins

Clerical admins are appointed by the Leader for their technical skill and confidence with Wander's infrastructure. They update the website and in-game mod on members' behalf and help anyone who needs a hand.

They carry no extra rank or voting weight. It is anticipated the need for clerical admins will reduce as community administration becomes more automated and members grow more confident with the infrastructure.

Beacon Operatives

While applications are open, Beacon Operatives look after new applicants. They approve biographies, roleplay with applicants on Discord, and take part in the in-game RP stage of the application.

Anyone can help with onboarding once they've been in Wander for three months.

Leaving Wander

Members who leave and have been actively contributing to Wander for six months or more will be classed as 'Former Members', and will retain certain permissions both on the Discord and on the server.

Former members do not need to go through the application process if they wish to return. However, due to the limit on membership numbers, if Wander is near capacity or has a number of applicants pending, their wish to return may be delayed.

Management

There are four community management approaches utilised in Wander. It is anticipated most day-to-day community management will be either self-managed or subject to random approval.

Self-managed

In line with the good faith and trust ethos, a fair portion of Wander's community management is given to the players themselves.
For example:

• Storylines need no approval (assuming they follow the guidelines and the story so far)
• Posting to the website (Journals)
• Tagging and interlinking events
• Creating and setting up RP events

Random approval

Where something needs some approval or oversight, a community member is picked at random by TW-W2 to approve or deny the request. The person who approves/denies it is kept anonymous.
For example:

• XP grants for new skills
  • Wander has no XP-dispensing mechanic. Instead, XP can be requested via a command in Discord. This is then sent for random approval.
• Event, Lore and News posts to the website
  • This is to check for typos and imagery suitability.

Votes

A full clan vote. Every member of Wander is asked to vote on a topic anonymously.

Leader

A decision made by the Leader.

IC

In-character disputes are to be settled in character.

They are a natural part of roleplay and should not be conflated with OOC.

OOC

All disputes should be raised in good faith, with an understanding that everyone's preferences are unique.

Storylines shouldn't be disputed unless they directly impact your character or a shared community storyline, or clearly break the roleplay guidelines.

If you're concerned about the quality of someone's content or roleplay, you can submit a quality report through the bot with evidence; this can be done anonymously.

Leadership will review and decide on how to proceed.

Community Rules

Whilst Wander is in its infancy, these rules may be amended or added to, but the spirit will remain consistent.

These community rules aim to keep Wander roleplay-focused, whilst ensuring that everyone feels welcome.

Code of Conduct

How members should act and expect to be treated.

• Be respectful to all and treat everyone with kindness.
• No harassment, hate speech, racism, personal attacks or discrimination in any form.
• Avoid discussing serious real-world events, politics, religion or cultural topics.
• Keep content age-appropriate (PG-15). No sexually explicit media, excessive gore or extreme profanity.
• Be mindful and avoid meming or joking about storylines that parallel real-world events.

General Rules

• Wander's is an English speaking community. All roleplay must be conducted in English and all supporting media (e.g. event logs, journals). should also be written in English
• You must not be a member of another JKO/JKA roleplay group, community or clan.
• Do not steal or take original assets from other roleplay groups without the explicit permission of the creator.
• Do not share Wander assets with people outside of Wander.

Contributions Are Permanent

When you join Wander, your characters and roleplay become part of the story we're all telling together. Anything you submit to the website, like characters and records, adds to that story and helps shape it.

If you leave Wander, Wander retains the right to keep anything you've already submitted to the website.

AI Usage

Wander's story is written by its members. AI can be used to help speed things up, but it should never write, speak or roleplay for you.

• AI must not be used in the generation of text used in storylines, in roleplay or to create any entry on the website.
  • Spellcheck and grammar checks are fine.
• It may be used to support the administration of RP, like generating StoryForce stunt sheets for use in missions, and for the development of tools and resources.
  • AI must always be validated by someone with the ability to do so or, failing that, extensively and rigorously tested.
• Images: an in-game screenshot is always preferred to ensure image consistency. Custom artwork is also welcomed and permitted. AI images are not.

Discord

The main purpose of the Wander Discord is roleplay, the development of Wander and creative projects stemming from Wander. Whilst out-of-character and off-topic chat is permitted, it should never become a primary use of the server or your own individual interaction with Wander.

• Channels in the ((Huttese Fried Nuna Shack)) category are considered OOC.
• Use channels for their intended purposes, and keep conversations relevant to the channel.
  • Utilise threads for longer conversations on a single topic.
• Avoid excessive spam of all kinds (messages, GIFs, stickers etc.).

Server

• OOC chat should be limited to crucial messages that aid the flow of roleplay.
• Be mindful of holding the server when prepping. Be sure to clear and vacate the server when you're not using it, rather than idling during set-up.

Website

• Your main character profile image must be a transparent PNG of your character, although you may include other props. Your mini icon must be a head-and-shoulders mini silhouette.
  • More custom artwork can be uploaded to your character gallery.

Roleplaying Rules and Guidance

Wander wants to deliver quality roleplay. Please find below some general rules and guidance outlining how we aim to do this.

General

• Defer decisions to IC conversations.
  • If you're having a conversation OOC that could easily be had IC, switch to roleplay either on Discord or on the server.
• No romance, erotic or sexual roleplay.

Storyline Guidance

• No storyline can kill or permanently injure another player's main character without that player's agreement (either beforehand or during).
• In storylines where a player's ability to Wander is removed from them (e.g. captured), the responsibility is on the director to ultimately resolve this and restore that player to Wandering, unless agreed beforehand.
• Do not utilise any known characters from any other Star Wars media in your storylines. Wander sits completely stand-alone. Known lore that may be referenced can be found in includable canon lore.
• Check the 'what is accurate for right now' post to ensure you are using era-appropriate story elements in your roleplay.
• Key adversaries should be included as part of the Wander record, with their own profiles. This means that character depth and consideration of backstory and motivation are critical. Main adversaries are not to be 'throwaway'. They ideally should feature in multiple events, arcs or characters' stories.
• Unless told by leadership, no storyline should risk exposing 'The Beacon'.

Individual Guidance

• Before you start a story, use a rare skill or give your character something unusual, ask yourself: what would happen if every Wanderer did this?
  • One Wanderer with a secret contact in the Imperial Navy is a story. Sixteen would be ridiculous.
  • That doesn't mean you can't have one; it just means it needs earning. Show how your character got there through journals. Update your Story Hooks and see if others will run events to build it, so it feels believable by the time it matters.
  • Just make sure to give it a semi-realistic timeline; a trusted contact made in a week or a rare skill mastered in a fortnight will feel rushed.
• Describe the attempt, not the outcome, especially when your action affects another character.
• Play within your character; failure, weakness and defeat are what make a character worth following. Do not god-mod.
• No meta-gaming. Your character only knows what they have learnt in character. Whilst you, the player, may have read journals or timeline entries, it doesn't mean your character has.
• Share the spotlight: don't routinely dominate the conversation or action in a group scene. Especially in Discord group scenes, allow and give time for others to reply before posting again.

Installing JKA & Wander

You will be provided with installation files and instructions as your application progresses.

Joining the Servers

Details on the server and how to join will be provided to you as your application progresses.