The hardcoded was left in from early variations of WinryChat before it was made public with version 1.0, thanks for catching that! It’ll be removed and resizing addressed in an update that’ll also address another bug that @Tomi1231 caught with ASCII Characters. (I’ve been busy the last few weeks doing a few things, and haven’t been able to build up WinryChat 1.6 yet.)
As for directly customising the theme, that was the original intention of how it was supposed to be done. It’s the way I’d recommend doing it first and foremost, but UseCustomTheme can be for those who want to keep the default as-is as a backup.
2 Likes
Just noticed a post error. For those wondering why the counter for the alternative LegacyChat resource jumped down from 37 to 9:
I accidentally linked a comment I made on that post clarifying WinryChat, not the original post itself, which was a mistake!
Sorry to @Tomi1231 for the incorrect URL!
2 Likes
I just realized this thing does not even have a GitHub page listed nor a documentation page??? Can we have that and how is the OSS Discord suggestion going? Will that be in this project’s future?
Hey, just some quick pointers as to why:
-
I don’t have the knowledge to reliably convert project files from ROBLOX to GitHub via Rojo. Even if I did, I do not have any ability to verify it will work beyond studio’s own tooling. No tools I know of exist for me to test and produce ROBLOX Games in VS Community 2022.
-
I don’t have the time, sadly, to document WinryChat to the best of my abilities as I am currently in full-time games production with a production studio now.
-
I don’t like the output or formatting of Moonwave, nor similar automation tooling out there currently for the purpose of documenting projects.
-
I am in OSS discord as “Claire (extraclear)”, though currently do not know how to handle or publicly publish projects there.
Feel free to adapt WinryChat for VS Code manually. I have no interest in using VS Code, or using it to test anything. It’s a fine editor, it just isn’t my kind of editor and I don’t want to pretend to support something that I personally hate using and being unable to resolve any issues that result from it.
If anyone can find any way to get Luau + ROJO support for Visual Studio Community (Windows) and XCode (MacOS), I would be more than happy to receive that information.
2 Likes
Yeah, thanks for the resource though.
There is no OSS community for this, no GitHub community, and it looks like I am one of a few people who use this if I do adopt it which makes me hesitant to adopt.
Plus, I don’t think you even have an incentive to keep this updated so I may just use this for study instead 
For some reason the other OpenTextChatService is gaining more traction.
There are plans to update WinryChat to 1.6 alongside THA’s internal rewrite of it’s game framework (Shalltear), namely for Mobile Chat support, which we found to be ill-suited for phones during development of Teensy Tiny Tankery’s BETA.
There’s no OSS Community page, because I have no idea how to set one up. There’s no GitHub community because it’s not set for Rojo and may not be a compatible project for it. If anyone wants to reach out via OSS discord to help set either up, I’d be happy to listen.
Update: There’ll be an official project posting on OSS Community tomorrow.
Update 2: One has been setup.