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

Update level_compatibility.zs #973

Merged
merged 2 commits into from Nov 20, 2019
Merged

Update level_compatibility.zs #973

merged 2 commits into from Nov 20, 2019

Conversation

edthebat
Copy link
Contributor

Map fixes for some older mods

Map fixes for some older mods
@coelckers
Copy link
Member

Can you please add links to the mods? They are mainly obscure so I cannot check what was done here.

@edthebat
Copy link
Contributor Author

Yes, sir!
One against hell: https://www.doomworld.com/idgames/levels/doom2/Ports/m-o/one1
Toon Doom II: https://www.doomworld.com/idgames/levels/doom2/megawads/toon2b
Valletta's Doom Nightmare: https://www.doomworld.com/idgames/themes/terrywads/vltnight
Swan Fox Doom v2.4: https://www.wad-archive.com/wad/7bd37271e818ef60456e3370501c31dd

If there any objections to including any of these mods in level_compatibility, I am perfectly willing to host my fixes personally in user-made patches, which are thankfully now possible with the advent of the level_postprocessor.

Copy link
Collaborator

@alexey-lysiuk alexey-lysiuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would say that if it’s impossible (or much harder) do finish map without cheating, or if it’s impossible to get 100% kills/items/secrets, then it’s OK to include fixes to internal compatibility.
Without playing a map, and/or without checking with an editor sometimes, is it worth including or not.

Also, do you have a spacebar broken on the keyboard? It would be nice to have whole file formatted consistently, i.e. a space after comma, a space after //, and so on.

@edthebat
Copy link
Contributor Author

edthebat commented Nov 17, 2019

Also, do you have a spacebar broken on the keyboard?

I hardly feel that level of attitude was warranted... but fine, I can add spaces after commas and comments if it will make you happy.

@alexey-lysiuk
Copy link
Collaborator

No offense, but let’s not forget that the code is mostly read, not written. The thing is how it was written does matter. If it’s hard to read, then it was written poorly.

@edthebat
Copy link
Contributor Author

I genuinely find spaces after commas make code harder to read. In addition to wasting filespace; sometimes every byte can matter.

However I do agree with you that consistency is important, and since the existing body of the file follows those conventions, I can adapt my commit to match. After all, I even followed along with adding braces around the body of each Case, even though that doesn't follow any conventions I'm aware of for Switch statements.

Spaces around commas and comment markers, to better match the rest of the file
@madame-rachelle
Copy link
Collaborator

I'm going to go ahead and take this one since it seems pretty harmless. If I am wrong the changes can always be undone.

@madame-rachelle madame-rachelle merged commit 826c3c4 into ZDoom:master Nov 20, 2019
@edthebat edthebat deleted the levelcompat branch November 20, 2019 19:05
drfrag666 pushed a commit to drfrag666/gzdoom that referenced this pull request Nov 23, 2019
* Update level_compatibility.zs

Map fixes for some older mods

* Formatting changes

Spaces around commas and comment markers, to better match the rest of the file
drfrag666 pushed a commit to drfrag666/gzdoom that referenced this pull request Nov 23, 2019
* Update level_compatibility.zs

Map fixes for some older mods

* Formatting changes

Spaces around commas and comment markers, to better match the rest of the file
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.

None yet

4 participants