Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Speech Fomatting (PORT) #663

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

NPC1314
Copy link

@NPC1314 NPC1314 commented Feb 2, 2025

About The Pull Request

Ports the Formatting from https://github.com/sylphynford/Penumbra/pull/110/files
Looks like this
emphasis

So / word / for cursive, //other// for thick
Also reminder you can sing by putting % in front of words, for all the bards.

The Blackstone branch refactored their speech code somewhat at some point, possibly worth considering adopting the whole thing, then again maybe not. This works independently at least. Had to include the autopunctuation from Azure to keep it consistent, works too.

Pre-Merge Checklist

  • You tested this on a local server.
  • This code did not runtime during testing.
  • You documented all of your changes.

Copy link

@tontyGH tontyGH left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not fond of the implementation for emphasis... It's very messy and hard to follow. Having the same symbol / have 3 different uses might also make it unwieldy for users.

We should just port TG's emphasis implementation instead as it's way cleaner. No point in re-inventing the wheel.

Comment on lines +101 to +103
//allow player to format their speech
message = replacetextEx(message, regex(@"^([/+]*)(.*?)([/+]*)$"), /proc/format_dialogue)

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A bit early, no? There's still quite a bit of parsing to go through.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could be, can´t claim to understand this code, just tested if it did what it said on the tin and it did.

@aberrantQuesrist
Copy link

Could we make this consistent with SS13 in terms of formatting?
|Sample| for italics.
+Sample+ for bold.
Et. cetera.

Otherwise, lovely addition.

@NPC1314
Copy link
Author

NPC1314 commented Feb 5, 2025

Could we make this consistent with SS13 in terms of formatting? |Sample| for italics. +Sample+ for bold. Et. cetera.

Otherwise, lovely addition.

Haven´t been able to do this, but perhaps someone else is. Would make sense to keep commands consistent.

@tontyGH
Copy link

tontyGH commented Feb 5, 2025

Haven´t been able to do this, but perhaps someone else is. Would make sense to keep commands consistent.

Would you be alright if I made an alternative PR with TG's implementation then? Or would you prefer to redo this one

@NPC1314
Copy link
Author

NPC1314 commented Feb 5, 2025

Haven´t been able to do this, but perhaps someone else is. Would make sense to keep commands consistent.

Would you be alright if I made an alternative PR with TG's implementation then? Or would you prefer to redo this one

Of course, go right ahead! I´ll close this as soon you put yours up.

@NPC1314 NPC1314 marked this pull request as draft February 5, 2025 21:36
@tontyGH
Copy link

tontyGH commented Feb 6, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants