DEV BUILD (branch: deploy) - NOT FOR PUBLIC USE
 

New Loremaster, New Opportunities!

September 29, 2020

Hullo, Bravo Fleet! Were you all tired of my announcements as Chief of Staff? I’ve got good news and bad news, then. Good news: I’ll be making fewer of them. Bad news: You still have to sit through this one.

I am thrilled to bits to take on the role of Bravo Fleet Loremaster. The Lore Office is a fantastic resource, here to work with Task Forces in developing a universal canon for the Fleet. This means every story has the capacity to impact another, and we can all contribute to the dynamic universe of 2399, instead of only experiencing or being affected by our separate games. It means long-term narratives, stories that prevail through staff changes or unit reshuffles. It means consistency of theme, a commitment to a vision of Trek that is exciting and adventurous, occasionally dark and dangerous, but fundamentally optimistic and thoughtful.

And this is a canon you can engage with. We want you to read it and think, “Wow, what story can I tell with that?” – and for you to then do it in your games or on the forums. The Charter says that the Loremaster “is charged with maintaining, updating, and expanding the fictional lore and story line of Bravo Fleet.” This is true, and it’s why I’ll be working with Task Force staff to offer support with current projects, so every area of operations has a robust, developed launching point for storytelling. But I think my most important job is getting people to want to write within that maintained, updated, and expanded lore – and to support the best way for you all to do that.

Keep your eyes posted for updates from Task Forces as they continue to develop their canon. Within the next few months, we intend for every notable faction of every Task Force to have their own fully-developed page on the Bravo Fleet Infobase. Think of these as the sandpits in which you can play and write and tell stories. From there, the Lore Office has schemes – oh, yes – but in the meantime we’ll be bringing 2399 to life and to your screens.

And until then, some book-keeping!

 

New Positions

Looking to the future of the Lore Office, we have opened recruitment for some new positions. Please Apply Here for either role!

Infobase Admin

The BF Infobase’s purpose is to be our one-stop-shop for canon. This is only possible if it’s well-managed, tidy, and consistently presented. As such, the Lore Office is looking for an Administrator for the Infobase, who will be responsible for making sure articles are properly formatted, designing templates, managing categories, and assisting writers in the Lore Office and Task Force Senior Staff in getting their content up. This role requires an eye for detail and would benefit from some skills (or eagerness!) as a writing editor, but most important of all is a familiarity with MediaWiki.

Technology Team (temporary)

We’ve been rewriting many of our starship specifications over the last year. The intention has been to write articles about ship classes that don’t focus on how many torpedo launchers are at the fore and aft of the ship, but properly explain things like what a class is good at, how independently it can operate, and what life aboard is like for the crew. We want these to be guides to inspire and advise writers in their storytelling, while still providing what technical detail is necessary (apparently we care more than VOY how many shuttles are aboard).

We are almost done with our articles on Federation ships. We have keen volunteers looking to work on alien vessels. But we would welcome more assistance, particularly with the latter. This would be a temporary role; while this project has taken a long time, we’d like the manpower to not still be working on it in another year. But it’s a great chance to contribute to the Fleet with a useful resource that players will use and refer to all the time!

If you’re interested, please first take a look at some of our starship articles – and remember, we want to produce writing guides rather than technical manuals.

 

 

For all of this – lore development, applying to the office, ideas about the writing community in Bravo Fleet – my e-mail inbox or my Discord (justslide#9285) are open. Questions? Suggestions? Wanting to know if you can Do A Thing, or wanting us to Do A Thing? You all know I love how BF has expanded for gaming, competitions, expanded as a community, but our origins will always be as a writing group. I intend to only expand our writing community in future, increasing engagement with the storytelling on Relay Station Bravo or workshopping opportunities to discuss and develop our fictions. Until that all kicks off, I’d love to hear people’s thoughts, ideas, or queries.

Load Time: 0.77 seconds

Total SQL Queries: 38

1 SELECT wp_posts.* FROM wp_posts WHERE 1=1 AND wp_posts.post_name = 'new-loremaster-new-opportunities' AND wp_posts.post_type = 'group_news' ORDER BY wp_posts.post_date DESC
1 SELECT post_id, meta_key, meta_value FROM wp_postmeta WHERE post_id IN (34812) ORDER BY meta_id ASC
1 SELECT * FROM wp_posts WHERE ID = 158922 LIMIT 1
1 SELECT post_id, meta_key, meta_value FROM wp_postmeta WHERE post_id IN (158922) ORDER BY meta_id ASC
1 SELECT * FROM wp_posts WHERE ID = 158923 LIMIT 1
1 SELECT post_id, meta_key, meta_value FROM wp_postmeta WHERE post_id IN (158923) ORDER BY meta_id ASC
1 SELECT * FROM wp_posts WHERE ID = 49387 LIMIT 1
1 SELECT post_id, meta_key, meta_value FROM wp_postmeta WHERE post_id IN (49387) ORDER BY meta_id ASC
1 SELECT wp_posts.ID FROM wp_posts WHERE 1=1 AND wp_posts.post_type = 'group_news' AND ((wp_posts.post_status = 'publish')) ORDER BY wp_posts.post_date DESC LIMIT 0, 2
1 SELECT * FROM wp_posts WHERE ID = 147863 LIMIT 1
1 SELECT wp_posts.* FROM wp_posts WHERE ID IN (159212,159053)
1 SELECT t.*, tt.*, tr.object_id FROM wp_terms AS t INNER JOIN wp_term_taxonomy AS tt ON t.term_id = tt.term_id INNER JOIN wp_term_relationships AS tr ON tr.term_taxonomy_id = tt.term_taxonomy_id WHERE tt.taxonomy IN ('group_news_category') AND tr.object_id IN (159053, 159212) ORDER BY t.name ASC
1 SELECT post_id, meta_key, meta_value FROM wp_postmeta WHERE post_id IN (159053,159212) ORDER BY meta_id ASC
1 SELECT wp_posts.ID FROM wp_posts INNER JOIN wp_postmeta ON ( wp_posts.ID = wp_postmeta.post_id ) INNER JOIN wp_postmeta AS mt1 ON ( wp_posts.ID = mt1.post_id ) WHERE 1=1 AND ( ( wp_postmeta.meta_key = 'event_status' AND wp_postmeta.meta_value = 'In Progress' ) AND ( mt1.meta_key = 'event_type' AND mt1.meta_value = 'fleet_action' ) ) AND wp_posts.post_type = 'events' AND ((wp_posts.post_status = 'publish')) GROUP BY wp_posts.ID ORDER BY wp_posts.post_title DESC LIMIT 0, 1
1 SELECT * FROM wp_posts WHERE ID = 84168 LIMIT 1
1 SELECT * FROM wp_posts WHERE ID = 136019 LIMIT 1
1 SELECT ID, post_name, post_parent, post_type FROM wp_posts WHERE post_name IN ('donate') AND post_type IN ('page','attachment')
1 SELECT * FROM wp_posts WHERE ID = 147861 LIMIT 1
1 SELECT post_id, meta_key, meta_value FROM wp_postmeta WHERE post_id IN (16756) ORDER BY meta_id ASC
1 SELECT t.*, tt.*, tr.object_id FROM wp_terms AS t INNER JOIN wp_term_taxonomy AS tt ON t.term_id = tt.term_id INNER JOIN wp_term_relationships AS tr ON tr.term_taxonomy_id = tt.term_taxonomy_id WHERE tt.taxonomy IN ('group_news_category') AND tr.object_id IN (26834) ORDER BY t.name ASC
1 SELECT * FROM wp_posts WHERE ID = 16756 LIMIT 1
1 SELECT post_id, meta_key, meta_value FROM wp_postmeta WHERE post_id IN (26834) ORDER BY meta_id ASC
1 SELECT * FROM wp_users WHERE ID = '1036' LIMIT 1
1 SELECT user_id, meta_key, meta_value FROM wp_usermeta WHERE user_id IN (1036) ORDER BY umeta_id ASC
1 SELECT wp_posts.* FROM wp_posts INNER JOIN wp_postmeta ON ( wp_posts.ID = wp_postmeta.post_id ) WHERE 1=1 AND ( ( wp_postmeta.meta_key = 'promoted_user' AND wp_postmeta.meta_value = '1036' ) ) AND wp_posts.post_type = 'user_rank_assignment' AND ((wp_posts.post_status = 'publish')) GROUP BY wp_posts.ID ORDER BY wp_posts.post_date DESC
1 SELECT post_id, meta_key, meta_value FROM wp_postmeta WHERE post_id IN (69176,39168,19422,19023) ORDER BY meta_id ASC
1 SELECT * FROM wp_posts WHERE ID = 24587 LIMIT 1
1 SELECT post_id, meta_key, meta_value FROM wp_postmeta WHERE post_id IN (24587) ORDER BY meta_id ASC
1 SELECT wp_posts.* FROM wp_posts INNER JOIN wp_postmeta ON ( wp_posts.ID = wp_postmeta.post_id ) WHERE 1=1 AND ( ( wp_postmeta.meta_key = 'user' AND wp_postmeta.meta_value = '1036' ) ) AND wp_posts.post_type = 'staff_record' AND ((wp_posts.post_status = 'publish')) GROUP BY wp_posts.ID ORDER BY wp_posts.post_date DESC
1 SELECT post_id, meta_key, meta_value FROM wp_postmeta WHERE post_id IN (18806) ORDER BY meta_id ASC
1 SELECT post_id, meta_key, meta_value FROM wp_postmeta WHERE post_id IN (34847) ORDER BY meta_id ASC
1 SELECT * FROM wp_posts WHERE ID = 34812 LIMIT 1
1 SELECT * FROM wp_posts WHERE ID = 34844 LIMIT 1
1 SELECT * FROM wp_posts WHERE ID = 34813 LIMIT 1
1 SELECT * FROM wp_posts WHERE ID = 34819 LIMIT 1
1 SELECT wp_posts.ID FROM wp_posts INNER JOIN wp_postmeta ON ( wp_posts.ID = wp_postmeta.post_id ) WHERE 1=1 AND ( ( wp_postmeta.meta_key = 'member_user' AND wp_postmeta.meta_value = '1036' ) ) AND wp_posts.post_type = 'member' AND ((wp_posts.post_status = 'publish')) GROUP BY wp_posts.ID ORDER BY wp_posts.post_date DESC LIMIT 0, 1
1 SELECT wp_posts.* FROM wp_posts WHERE ID IN (18806)
1 SELECT * FROM wp_posts WHERE ID = 12371 LIMIT 1