Oh, well I feel stupid. Why use UIstroke over Textstroke though?
The stroke effect property directly in TextLabels is deprecated — this means its likely slower and won’t get maintained.
While creating UIStroke instances does require creating another instance, I’d say I prefer not using a deprecated feauture.
1 Like
I didn’t even know this. I looked it up, it seems that the documentation says it isn’t deprecated, UIstrokes just provide a way to use Gradients.
Thanks for pointing this out. I don’t know how I was confident I saw it was deprecated. 
I can’t seem to find the property for changing the text stroke size in the TextLabel. Any idea where it is and what it’s called?
1 Like
Oh. I guess that’s the downside. I always remembered there being an option to adjust the stroke size, strange. 
You can search in the properties window, and I’ve had no luck finding it with any keyword like size, stroke etc.
Weird, yea, I sure do remember there being a size option too.
I guess, for now, I’ll stick with UIStrokes. Let me know if you find this size control, and I’ll be sure to change it!
1 Like
Just a few suggestions;
If you haven’t already, you should add a way to utilize the UIStroke to add gradients to the stroke. This should probably happen automatically if StrokeColor is passed in as a number sequence.
Same thing for text color as well.
Ability to merge text so we can use less instances for things like stroke. Sure, this removes some functionality like having a letter fade in effect, but it’s fully up to the developer. Preferrably this can be possible within the string itself using certain tags? It can also easily create other unique effects such as a specific word fading in whole instead of each of the letters separately. (as an example)
2 Likes
If you haven’t already, you should add a way to utilize the UIStroke to add gradients to the stroke. This should probably happen automatically if StrokeColor is passed in as a number sequence.
That’s a great idea, I will include that in the next update.
Ability to merge text so we can use less instances for things like stroke. Sure, this removes some functionality like having a letter fade in effect, but it’s fully up to the developer. Preferrably this can be possible within the string itself using certain tags? It can also easily create other unique effects such as a specific word fading in whole instead of each of the letters separately. (as an example)
Do you realize that you can already achieve all sorts of custom effects? That’s the whole purpose of this plugin. You can sort by characters, word and lines. You can loop through in any way you want. Did I miss anything?
2 Likes
Not really, but I don’t know if it’s the best idea to have a UIStroke for every single character in the string.
Sometimes, a creator may want a whole word to have a basic stroke instead of doing some effect with it, and if that’s the case I don’t know if creating a whole new UIstroke for every character in the word is really the best idea.
Unless UIstrokes under folders apply to every textlabel in it, that’s also an option.
1 Like
Well they can simply loop through that specific word and apply the stroke like this:
-- Requires to have only word sorting.
for _, character in ipairs(frame["4"]) do -- Will go through 4th word. do
local uiStroke = Instance.new("UIStroke")
uiStroke.Thickness = 6
uiStroke.Color = Color3.fromRGB(255, 255, 255)
uiStroke.Parent = character
end
This module is not supposed to cover all cases with built-in functions. It’s supposed to open up for creativity, while still preserving the intuitive, quick customization properties when creating basic text.
1 Like
This applies a UIstroke for every character in the word.
I’m suggesting that there should be a way to use a single UIstroke for a full word, but it’s fine if you don’t wanna implement that.
I’m confused. You can’t create a stroke for multiple characters using only one UIStroke instance.
As far as I know, that’s not possible.
1 Like
Version 1.2.0
New features:
- New
Dynamicoption (customization) — automatically re-renders the text when the frame is resized. - New
StrokeColorcustomization.
Changes & improvements:
- Renamed
Strokecustomization toStrokeSize. - Now warns about invalid provided customization options.
- Added a simple template in
CustomFontsmodule. - Linked devforum post at the top.
- Minor performance improvements.
-
falsebooleans are stored as nil instead. - Minor comment changes and additions.
1 Like
[my bad didn’t see it xddd]
when will i have some way to like, convert all fonts that i already pre-built into my own instead of creating a new text?? i usually create my UI at the beginning instead of storing it in the code
i read “custom fonts” and died on the spot. thank you for this
2 Likes
It’s a code library. You can’t render anything outside of the code.
You could set up a system, where you give frames a tag like e.g. TextPlus, then detect those in a script that then runs TextPlus on it — it could pass the attributes of the frame to TextPlus, so that you will have to add a Size attribute on each TextPlus frame etc.
TLDR; You can implement a half-fix yourself, but by default, this isn’t an option with TextPlus.
I hope this helps.
1 Like
Thanks for pointing that out! I apologize for the mistake.
It might be a future feature, and I must’ve accidentally added it to the list of customizations.
So unfortunately, TextScaled is not yet a feature.
I might be adding it in the future, though.
Hey! I’m facing an issue with custom fonts, the module is giving a warning that my custom font’s style doesn’t have a “Size” value in it. I have it set as 100
This is what the output console looks like:
I will try to figure it out, but help will be appreciated
(It’s either that I’m stupid or no lmao)
Sorry, it turns out I really am stupid 
, what it was is that the size ant characters aren’t an extra table, see that bracket below Image variable? Yea, that wasn’t supposed to be there. I fixed it and it works fine now.
(ts (this) is peak btw, I’m using this everywhere now 
)
2 Likes