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

Terrain validation #265

Open
Corgano opened this issue May 28, 2020 · 5 comments
Open

Terrain validation #265

Corgano opened this issue May 28, 2020 · 5 comments
Labels
enhancement New feature or request good issue A good issue that someone should research

Comments

@Corgano
Copy link

Corgano commented May 28, 2020

As i was cataloging the river / cliff tiles, it occurred to me it wouldn't be hard to also record a list of what tiles can validly be placed above / below / to the side of any other tile. For instance river7A is an inner corner of a river diagonal. if it is rotated with land on the bottom left, it can only have river5b, 7A, or 8A on the top and right side, and only with specific rotations. Same is true of the bottom and left sides needing a river tile with a bank, etc.

It could be possible to have each tile have to have a list of acceptable tiles(:rotations) that can be above, below, left and right. You can then have a validate button that checks the tile rules of all the tiles on the map, and then flags any invalid neighboring tiles.

@Corgano Corgano added the enhancement New feature or request label May 28, 2020
@ghost
Copy link

ghost commented Feb 6, 2021

I'm going to start compiling a list of conditionals and conventional names for each field unit and variation over the next month or so in an effort to improve usability of the terrain editor. I also plan to create SVG graphics for each unit as it would appear on the in-game map.

@Corgano
Copy link
Author

Corgano commented Feb 6, 2021 via email

@ghost
Copy link

ghost commented Feb 7, 2021

This is awesome work! I had actually planned to convert the top-down view of each tile model into SVG files and colour each material its associated map colour to simulate how they are shown in-game. However I do appreciate the notes you've wrote for each tile, that should speed up testing.

I have already started a sheet with example tile sprites https://docs.google.com/spreadsheets/d/12LOYvdpuKxqYc9cuDfMc3PawgVv8mFcOVn6x449kU9s/edit?usp=drivesdk The name column is what the editor itself calls the tiles, you could make a new column for each direction and a list of all compatible tile names

On Sat, Feb 6, 2021, 7:01 AM Friedslick6 @.***> wrote: I'm going to start compiling a list of conditionals and conventional names for each field unit and variation over the next month or so in an effort to improve usability of the terrain editor. I also plan to create SVG graphics for each unit as it would appear on the in-game map. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#265 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGSARLFPFZ24NLMSJ2VBI3S5VDT3ANCNFSM4NMY4CLA .

@Corgano
Copy link
Author

Corgano commented Feb 7, 2021 via email

@Corgano
Copy link
Author

Corgano commented Feb 7, 2021 via email

@berichan berichan added the good issue A good issue that someone should research label Dec 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good issue A good issue that someone should research
Projects
None yet
Development

No branches or pull requests

2 participants