I don't think your choice of easy levels is suitable for new players. When displaying the range of flowers some of the covered cells receive a different shade than others which is weird. Connected to this is that when tapping on the "finish"-screen it is still possible to increase the number of "failures" (visible when the game fades to the menu) if you happen to hit an unrevealed black cell. While this is standard behaviour for minesweeper, it is non-standard behaviour in Hexcells: A level is finished if all cells are revealed. You declare a level as finished when all blue cells are revealed. Some of your tutorial levels look unsolvable to me, namely number 2, 8 and 12. Now to Darm4n: I played a little more and this is what I found/think: One thing for everyone: I believe that Darm4n and his pal acted with the best of intentions and commited an error of ettiquette not out of spite but by accident. :/Įdit: does the editor have some sort of bug that sometimes makes all cells revealed or is Android Studio doing something fishy with my txt files? The only major concern I have right now is the general confusion regarding a ripp-off. However, I could add a tag to sort the sectionList in the level selection screen by either author, category and additionally Level Pack. I'd need to modify the reader quite heavily and somehow have it stay active or at least remember where the next level starts after you've finished the current one. It seems to be too much of a hassle for so little convenience. I might add some levels in the future that my friend or I created depending on how good they are.Īs for level packs: probably not. (It's not easy reaching that many people and waiting for an answer from every single one.) But I can still take it out retroactively. I also highly doubt somebody would object, and they already made their level public after all. Regarding the choice of levels, I will include all publicly released levels from this sub. Right now the Import Level button links to this subreddit if there is no content in the EditText field, but I forgot it in the credits. I'll test it a little and may post again or edit this post as a get a clearer picture. For instance, I don't see why you included "The Info Must Flow" (which is broken in my book) but would have included some other levels you didn't include. It may be appropriate to adopt a clear policy (include levels based on the number or percentage of upvotes) or have your level browser actually crawl reddit to display all levels and the votes they got. Your choice of levels seem a bit arbitrary. This is where the levels are distributed and this is where people can find more of them, so I'd like to see a link to this subreddit (not only on the store page but ingame). The credits should link to r/hexcellslevels. I doubt anyone would object (I, for one, am fine with my levels being included), but it seems like common courtesy to ask first. You should ask level creators for permission when including their levels. If, however you plan to improve/extend it, I suggest you address the following issues: I understand this is primarily a small practice project, so if you want to just leave it as it is, I'm fine with that. I took a first glance at it, and it seems pretty cool. I can send them to you if you so wish, but I doubt that. Those are 2 or 3 Tutorial level that have been created yesterday at 2am because everybody wanted something changed. Looks like you are including levels exclusive to this app If you are so unhappy about the levels v2, I can change it or completely remove the feature and make the app break bigger levels. So knowing the length is rather important. And reading out from a String never blocks the reader like it does from a file. Meaning if your level is something as: 100x3 reading out the first line would result in a grid of 3x3 because the BufferedReader only reads per line. And The Editor roughly matches the size of the level. To avoid NullPointers I need to know the size of the level beforehand. We have never used it, and so far all levels here are of standard size. It's simply an easy way to avoid haveing the BufferedReader go through the entire file multiple times.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |