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

Add support for ValueTypes.STR_SOUNDSCAPE "soundscape" #36

Merged
merged 2 commits into from
Nov 11, 2024

Conversation

ozxybox
Copy link
Contributor

@ozxybox ozxybox commented Nov 11, 2024

This adds a new FGD valuetype for soundscapes. This is needed for a feature I'm working on. I don't think there's really any reason to use this in the HammerAddons FGD, as it would likely end up worse than the current system with choices. I thought about maybe making a polyfill for this, but it would likely end up more messy than what you have now haha.

@ozxybox
Copy link
Contributor Author

ozxybox commented Nov 11, 2024

I don't think the test failure is from me, but maybe I'm not understanding the output of it. Some of it seems to be from a tokenizer and the other seems to be from escape sequences?

@TeamSpen210
Copy link
Owner

Okay those test failures are mine. For the valuetype, can you name it ValueTypes.EXT_SOUNDSCAPE, to mark it as non-standard. HA might want to use it in the engine definition.

@ozxybox
Copy link
Contributor Author

ozxybox commented Nov 11, 2024

Sure thing!

@ozxybox ozxybox force-pushed the valuetype-soundscape branch from d3d0648 to 2db97dc Compare November 11, 2024 20:37
@TeamSpen210
Copy link
Owner

If you merge in, the tests should pass now.

@TeamSpen210 TeamSpen210 merged commit 671ea12 into TeamSpen210:master Nov 11, 2024
8 checks passed
@ozxybox
Copy link
Contributor Author

ozxybox commented Nov 12, 2024

Thanks!!

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.

2 participants