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

Answer check for deformed panel #2

Open
competor opened this issue Jun 7, 2023 · 5 comments
Open

Answer check for deformed panel #2

competor opened this issue Jun 7, 2023 · 5 comments

Comments

@competor
Copy link

competor commented Jun 7, 2023

Hi. I'm making my puzzles using this tool and have one trouble.
I tried to make a deformed panel of a 4x4 board with some edge parts missing, but this software gives me NG processing.
スクリーンショット 2023-06-07 161014

The screen on the right is from the site. This is the only intended one.
How can I fix this problem?

This is my .wit file.
https://gist.github.com/competor/32e89cd5b590c83bd2fcfa161609b58e

@instr3
Copy link
Collaborator

instr3 commented Jun 17, 2023

Hi competor,

The reason is that there are extra facets (cells) in the puzzle. Facets are associated with vertices instead of edges, so by deleting the edges, the facets will not be automatically deleted.

You can see the facets are still there by dragging the map in the editor. If a place shows a dot then there exists a facet.

image

You can simply select them and delete them, then the puzzle should work as intended.

image

@competor
Copy link
Author

Oh, thank you it worked! I overlooked the "Delete elements" function in the editor.

@competor
Copy link
Author

There is one more related question.
I would like to create a board with directly erased Edges without using BrokenDecorator to make the board view simpler and easier to understand.
As in the example below.
スクリーンショット 2023-06-19 094453

This is the path that I expected.
スクリーンショット 2023-06-19 094032

But when I erase the edges, this one is judged as incorrect.
スクリーンショット 2023-06-19 094909

This is my .wit file.
https://gist.github.com/competor/a495f18a8655bcdad241467c083a6994

@instr3
Copy link
Collaborator

instr3 commented Jun 20, 2023

I think now the problem comes with the game client. The game client assumes the graph is topologically "correct":

  • Every N-sided facet is surrounded by exactly N edges and N vertices.
  • No overlapping vertices.
  • No crossing edges. Crossing points must be a vertex.
  • Etc.

The editor was created long before the game client so they have different restrictions.

While the code can be modified to judge Tetris correctly in an "ill-defined" graph, I would not recommend doing so since there are other components that rely on the "correctness" of the graph (e.g., correct region segmentation, triangle judging etc).

Therefore, I recommend avoiding this for custom levels.

@competor
Copy link
Author

okay!

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