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

Entity IO contains "line break" character will make entity been deleted #1

Open
dounai2333 opened this issue Oct 11, 2024 · 1 comment

Comments

@dounai2333
Copy link

dounai2333 commented Oct 11, 2024

If a entity IO connections contain any of "line break" character, Stripplier will detect it as a invalid entity and delete it and doesn't tell in log file.

For example, I have a "game_text" entity, and I need to set a new message to it by a "trigger_once" entity through IO, but Hammer didn't support using '\n' so I have to edit vmf directly to add a "line break (i.e. '\n')" for it, and it work like a charm.
However Stripplier will just delete the "trigger_once" entity with no log preset, no any warning or error, it will disappeared even there is no any stripper touch the "trigger_once" entity.

EDIT: I found 2 maps that will trigger this issue: ze_ffvii_mako_reactor_v6_b08 and ze_ffxii_ridorana_cataract_t5_3 .

This is how it looks in vmf:

Entity
{
	"classname" "trigger_once"
	connections
	{
		"OnStartTouch" "text,AddOutput,message Test message!
I'm in new line!
This is another new line!,0,-1"
	}
}
@lameskydiver
Copy link
Collaborator

I am aware that CS:S .vmf's allow the use of newline char, but since Stripplier was mostly made with CS:GO in mind this is indeed a oversight I did not account for.

For reference, this is (for now) an intended behaviour; the newline breaks the keyvalue pair into multiple names, which Stripplier ignores in case of a erroneous .vmf.

Due to how the code is set up it may need a bit of revision, but I'll try to fix it based on the examples you've given me.

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

No branches or pull requests

2 participants