In Progress Textbox in Language Filters Custom replacements does not allow hyphen

[Melphina]

I am reporting two separate issues I want to bring attention to in version 0.9.139-BACKER#6353

The first thing I want to mention is probably a result of changes you guys made on the backend at some point to update how parsing and naming conventions are handled. I recently built a new PC and in the process of porting over my data from my old device to my new one I found that I can no longer use the hyphen symbol in the custom replacements for language filters in the game options screen. I've included a screenshot of one of my custom edits from my old machine, where I had set "Feline-Morph" to replace with "Catgirl" and "Herm-Sperm" with "Futa-Cum". That was from an older version of the game and in the current build I can only type FelineMorph or HermSperm, which is not the same. One was a personal preference for a racial name and one was for a few in game instances of a term that I enjoy the latter more than the former.

My browser is the latest build of Firefox, but I'm certain it isn't the browser's fault. All of my data from my old PC is backed up onto an external hard drive so to test things I went into Firefox options on my old PC and completely cleared out the entire browser history and relaunched the browser fresh. All the options on the TiTS page were reset to their default, and on my old PC I am no longer able to use the hyphen on the custom replacements screen anymore. My save file and other things are still saved and I won't be using the old PC anymore so I don't really mind the loss of functionality there, but I'd like to see it re-implemented in the current build if possible. I don't know if it would break anything to re implement hyphen functionality or not, but I would like to hope it wouldn't.

 

[Melphina]

Update to issue one: This screenshot is taken from the current version of the game. It appears that hyphen functionality does in fact still work on the "with" side, but not on the "Replace" side. You can't use hyphens on the text you're replacing, only on the textbox you're replacing WITH. That leads me to believe this actually is a bug and one half of the fields are somehow missing something.

 

[lowercase_donkey]

Looking at the code, restrictions were added in June of this year with the note "disallow any non-alphanumeric character".

Not sure why this was done, but it does seem to be intended.

 

[Melphina]

It's odd that that constraint would only apply to the replace field on the left and not the with field on the right. But I agree that that kind of restriction doesn't sound accidental. Oh well.

Is there any chance of a mention for the second point? If nothing else, maybe make anusoft allow for the hyper-pumped attribute if overdosed or something. I suppose that would be more a thing for content creators though.

 

[lowercase_donkey]

I'm submitting a change that would allow the dash to be used again.

Would you mind opening a different thread for your other issue? A bit easier to manage.

 

[Melphina]

That's fair. I edited out the hyper pumped status from this thread's original post and created a separate thread for it.