Matt

I still don't think that changing the scenario names is a good idea. People are used to what it is and guidelines will have the name that it currently is,...

> > I still don't think that changing the scenario names is a good idea. People are used to what it is and guidelines will have the name that it...

I think we should move all those things into the Import function, we have too much of those calls scattered all over the place.

> I don't think it's as simple as calling it in Import because there seem to be codepaths which use Import but don't create animations. Maybe they're also wrong, but...

> I'd like to take this issue on! Can anyone suggest where to start looking for fixing this? The data is most likely stored in uint8_t, this type needs to...

I've said this in the other PR before but this one might have unwanted side effects, it's quite possible that people used this to block of paths on purpose, there...

This changes the path finding which currently does not support paths at invalid heights which is a drastic change and some parks may rely on this. They are called invalid...

> @ZehMatt How can a park 'rely' on the pathfinding not working? People do all sorts of things with odd behavior from the game so I wouldn't be surprised if...

Lets be clear here, when I say "I'm reluctant" doesn't mean I reject it, the concern is keeping existing parks the way they are. Also adding yet another cheat is...

> I find it kind of funny how _difficult_ it is to get anything approved on here. Reason I stopped committing code/features is cause it never got through. First thing...