I just published a new mission called The Show Must Go On.
It's about a holiday, pirates, and a Klingon Opera.
It's dialogue-heavy and combat-light, what you might call a "roleplay" mission.
It doesn't have any plays yet, so it's still pending review. If your captain needs a break, have them drop by.
I just played through your mission, sorry for taking a while to get around to it, I know how frustrating it can be getting your mission to qualify. Frankly I thought it was brilliant, easily a 5 star mission with a great story that really kept me entertained throughout.
I do have a few comments if they are welcome, they are all minor points but did detract a little from the overall experience.
- My biggest issue is there is a little too much characterisation of bridge officers. You've advertised this as a singleplayer roleplaying mission and so a lot of people playing it may already have an idea of what their bridge crew are meant to be like. Much of the dialogue conflicts with that. For example the opening scene with the happy tactical officer being referred to as "number one", that did not match with my hardened cardassian who is not my first officer. Equally my vulcan science officer smiling and talking about things that "amuse" her is a bit odd. Maybe tone down the personalities on the bridge officers and allow your unique mission characters (who are great!) fill in the emotional bits.
- There are quite a few grammatical errors throughout, particularly at the end of sentences you inconsistently add full stops. One response dialogue may have a full stop, the next won't. Some of your OOC text ends in full stops, some don't. Equally there is quite a bit of inconsistency in capitalisation, "Northwest and Northeast beach" is odd, either it is a name and beach should be capitalised or it is not and North shouldn't be. Rigelean pearls is also capitalised in one paragraph and not in the next. Its all minor but quite widespread, just need to take some time to go through it all (I understand there is a lot of dialogue to go through).
- A few spelling errors cropped up, mainly dylithium, it should be dilithium (i.e. two lithium atoms).
-The loftball bit was fun until the combat, that seemed out of place and jarring. All of a sudden a squad of people materialise, you're forced into combat and then the player is critised for it. Maybe making the player simply say "that's all too complicated" and skipping the combat might be better. It would go well with the entertainingly overly complex ruleset.
-Lastly, and this is just the RL scientist in me complaining, graphite and diamond are *not* the same on the molecular level. They are the same on the atomic level (i.e all just carbon), but on the molecular level they have a different crystal structure. I'm also not sure you needed to talk about quantum states, a slightly different quantum state of diamond would probably still have the diamond structure, its more geometric changes.
Don't get me wrong, these are all minor things, all the mission is great as it stands. I really enjoyed the focus on story and the use of combat where the story dictated it should be, not manipulating the story to fit the combat. Its clear you put a lot of work and effort into this and it truly deserves 5 stars, well done
I actually saw your review and spent the morning going through all the dialogue with a fine-tooth comb. Found most of the spelling errors, I think, but I would have completely missed dilithium, thanks for the heads up (I'm kinda new to Star Trek).
While I'm fixing the spelling and factual errors, I'll be sure to work on the consistency as well.
Believe it or not, referring to the officer as "number one", although minor, was one of the biggest things that stood out to me when I was creating the mission. On one hand, at that moment, I felt the captain would refer to that character as something. On the other hand, I have no idea who that character is to the player. I was worried it might be jarring, but left it in in case it could be brushed over. If it stood out to you (first person to play it), it will also stand out to others, though.
Ultimately the devil is in the details, so I really appreciate the feedback, it's what makes the difference between a good mission and a great mission.
I liked it. Didn't think the BOFF characterization was too jarring myself but it is definitely to always be careful about. I once played a mission that included a pre-existing romantic relationship between my captain and a member of the crew. That was pretty jarring.
Do not be afraid to joust a giant just because some people insist on believing in windmills.
Check out my foundry mission "The Writers of History".
Comments
I just played through your mission, sorry for taking a while to get around to it, I know how frustrating it can be getting your mission to qualify. Frankly I thought it was brilliant, easily a 5 star mission with a great story that really kept me entertained throughout.
I do have a few comments if they are welcome, they are all minor points but did detract a little from the overall experience.
- My biggest issue is there is a little too much characterisation of bridge officers. You've advertised this as a singleplayer roleplaying mission and so a lot of people playing it may already have an idea of what their bridge crew are meant to be like. Much of the dialogue conflicts with that. For example the opening scene with the happy tactical officer being referred to as "number one", that did not match with my hardened cardassian who is not my first officer. Equally my vulcan science officer smiling and talking about things that "amuse" her is a bit odd. Maybe tone down the personalities on the bridge officers and allow your unique mission characters (who are great!) fill in the emotional bits.
- There are quite a few grammatical errors throughout, particularly at the end of sentences you inconsistently add full stops. One response dialogue may have a full stop, the next won't. Some of your OOC text ends in full stops, some don't. Equally there is quite a bit of inconsistency in capitalisation, "Northwest and Northeast beach" is odd, either it is a name and beach should be capitalised or it is not and North shouldn't be. Rigelean pearls is also capitalised in one paragraph and not in the next. Its all minor but quite widespread, just need to take some time to go through it all (I understand there is a lot of dialogue to go through).
- A few spelling errors cropped up, mainly dylithium, it should be dilithium (i.e. two lithium atoms).
-The loftball bit was fun until the combat, that seemed out of place and jarring. All of a sudden a squad of people materialise, you're forced into combat and then the player is critised for it. Maybe making the player simply say "that's all too complicated" and skipping the combat might be better. It would go well with the entertainingly overly complex ruleset.
-Lastly, and this is just the RL scientist in me complaining, graphite and diamond are *not* the same on the molecular level. They are the same on the atomic level (i.e all just carbon), but on the molecular level they have a different crystal structure. I'm also not sure you needed to talk about quantum states, a slightly different quantum state of diamond would probably still have the diamond structure, its more geometric changes.
Don't get me wrong, these are all minor things, all the mission is great as it stands. I really enjoyed the focus on story and the use of combat where the story dictated it should be, not manipulating the story to fit the combat. Its clear you put a lot of work and effort into this and it truly deserves 5 stars, well done
Click for more details
I actually saw your review and spent the morning going through all the dialogue with a fine-tooth comb. Found most of the spelling errors, I think, but I would have completely missed dilithium, thanks for the heads up (I'm kinda new to Star Trek).
While I'm fixing the spelling and factual errors, I'll be sure to work on the consistency as well.
Believe it or not, referring to the officer as "number one", although minor, was one of the biggest things that stood out to me when I was creating the mission. On one hand, at that moment, I felt the captain would refer to that character as something. On the other hand, I have no idea who that character is to the player. I was worried it might be jarring, but left it in in case it could be brushed over. If it stood out to you (first person to play it), it will also stand out to others, though.
Ultimately the devil is in the details, so I really appreciate the feedback, it's what makes the difference between a good mission and a great mission.
Cheers
Please check it out if you have the time.
Check out my foundry mission "The Writers of History".
You have to have some liberty with officers, otherwise the writing is a little flat. All about striking a balance.
It's finally past review and has gone live. Still not sure why it doesn't qualify for rewards, but oh well.
Hope everyone enjoys it.