This is due to a workaround for an issue that was causing the backspace key to be super janky. That issue may be in bevy and/or winit.

Ex:

11月1日
juuichigatsutsuitachi

Possible fixes

• Just decrease font size in help mode
• Can bevy_ui do some sort of automatic scaling?
• Decrease the font size of everything in the action panel

Taipo was originally based on https://github.com/mrk-its/bevy_webgl2_app_template but diverged and removed native build options so that we could escape "dependency feature heck" with bevy_tiled

We should figure this out, because running natively is handy even if just for testing.

One of the main things contributing to low motivation to work on this project is artwork. I'm bad at it and it's not fun for me. The current art set is heavily inspired by tiles from Mother 3 with monsters drawn in a completely different style / scale and various poor quality custom work by me.

I am somewhat attached to the Good Pupper Memorial Tower and (slightly less so to the) Boss Coffee Vending Machine Tower, so they would need to be re-imagined.

It would be amazing if we could find an asset pack that covers more ground in a cohesive way. Especially if the author is amenable to doing custom work.

Requirements

• Compatible licensing for redistribution in an open source project
• A decent variety of monsters with walk and attack animations
• 16x16 tiles. (maybe 32x32, but 16x16 seems easier to build on)

Wants

• Japanese city and/or train things
• Towers
• Monster portraits

Hello!

Copied from the itch.io comments:

One comment I have is that I really struggled with some of the IME-like input since the behavior seems to not be quite the same as what I'm used to. Some examples:

enpi -> えんぴ (game requires ennpi. IME allows n followed by any consonant, I think)
tu -> つ (requires 'tsu')
ti -> ち (requires chi)

There might be a few others as well I didn't notice or which I don't tend to use, (e.g. li -> ぃ, xyo -> ょ).

But, especially since this is a time-sensitive kind of game, it would be nice to support some of these common shortcuts. Maybe it would be useful to use a library like https://docs.rs/wana_kana/

I had a couple thoughts based on your reply. First, I just wanted to share this article I found which is related, but unfortunately their advice is primarily targeted to native applications and I don't think it can really be applied to web apps...

So, other potential options I could see working:

1. Develop an IME for every possible language used in word list (seems... impractical at best, impossible at worst)
2. Accept user input via an HTML box or something like that (basically, players bring their own IME. Might be annoying to glue together and look weird)
3. Handle some basic forms of input and allow word lists to define a mapping for non-ascii characters (basically the current model, but with some changes)

Option 2 probably has the best support for all possible languages, but would require some glue code that can handle shuffling keyboard input from browser to the game, and might cause other input problems if you want to use things like arrow keys, etc.

Option 3 seems like the least work, and would probably entail just using a more robust conversion layer from ascii input to language output (check more possibilities while matching characters). If you wanted to go that route, here are some ideas about ways you could support multiple languages:

• In the word list, include a language designator indicating the target language
  • You could use this to decide whether to enable specific-language IMEs like Japanese/Korean/Pinyin
  • This raises the question of how to deal with "unsupported" languages
• Create mappings from ASCII characters -> target characters, some examples follow. This could easily get messy and be easy to miss things, I think. It also doesn't scale for e.g. Chinese which I believe would require thousands of mappings to be usable
  • e -> é
  • ss -> ß
  • ka -> か | カ

All around, I think this is a tricky issue so it may come down to what you are willing to give up vs how seamless you want the user experience to be. Hopefully this gives you some ideas to play with, and if you're interested I could even try implementing something to see how it is in practice. Let me know what you think!

I believe I have maybe already done a good portion of the refactoring / cleanup to make this more straightforward.

So this shouldn't be too hard.

When an ennemy is hitting the house. If you kill him he desn't die, continue hitting and isn't focused by towers anymore