Petr Hudeček's Personal Website

Sorry, this entry is only available in Czech. For the sake of viewer convenience, the content is shown below in the alternative language. You may click the link to switch the active language.

Sorry, this entry is only available in Czech. For the sake of viewer convenience, the content is shown below in the alternative language. You may click the link to switch the active language.

Když jsem byl menší, hrál jsem s bráchou hru “chodičku” s dřevěnými kostkami. Chodička funguje tak, že dva hráči pohybují jednotkami z dřevěných kostek po koberci a snaží se obsadit budovy. Budovy produkují jednotky, a jednotky hráčů proti sobě navzájem útočí. Jeden z hráčů hraje typicky za “nepřítele”, který “přichází”, tzn. nemá základnu, ale jeho jednotky se spawnují na okraji území, který “hráč” vidí.

Chodička je modelována částečně podle Dračího doupěte, ale hlavně podle počítačových real-time strategií jako Age of Empires a State of War.

Read more »

When you develop, i.e. create, a video game, you may want to follow this checklist of best practices. This is less important than the actual content or gameplay of the game but these items apply to the majority of video games:

1. Enemies don’t respawn automatically unless the player is informed. By default, except for JPRG games, the expectation is that there is a limited number of enemies. No matter your genre, you must be consisent: enemies either respawn everywhere or nowhere. If there’s a special area with respawn, you must inform the player (for example, the character could be repeating “I don’t think they’ll ever stop coming.”).
2. When there’s a time limit, you must show an actual countdown timer on the screen. No matter how bad the situation looks, the default assumption is that you can leave the game on for hours away from keyboard and nothing bad will happen. The characters can keep repeating things like “We need to hurry.” or “There’s not much time left.”  but unless there’s an actual countdown timer in the HUD, you cannot punish a player for waiting.
3. Mark all points of no return. In open world games, any points of no return must be clearly marked. If completing a question will cause a chapter to end, or if moving into a certain dungeon will end a part of the game or if talking to a certain NPC will move you in the finale, a big red dialog box should pop up in the player’s face, stating in no uncertain terms something like “This is a point of no return. If you proceed, the chapter will end and you will no longer be able to return to Littletown. Do you wish to proceed? [Yes, move on.] [No, not yet.]” Do not use in-character dialog for this. Make it very clear by using a game interface element.

Read more »

Abstract: Many people sometimes wish to talk to other via instant messaging applications about their lifes, news, common interests and other topics without having important information to tell and without wanting to make a request (we will call these conversations “chats”). However, it may be difficult to find out whether your interlocutor wants to chat or would prefer to end the conversation because we encounter problems related to courtesy. For these reasons, we present a new protocol for chats that could save time for both interlocutors and help them lead the conversation for exactly as much as they both desire.

Read more »