Icon

01_​BlackJack

BlackjackThis workflow implements the Blackjack card game via the Tile View (JavaScript) and CSS Editor nodes as well as the WebPortal functionality. It has an outer game loop that loops over multiple play sessions, and an inner game loop that iterates over the state (i.e., hands ofcards, player decisions taken, etc.) of a single play session.Some Blackjack rules are not implemented yet, but could be added in the feature. These include betting with chips, insurances and the player options to double down, split, or surrender.Ready to play? Run this workflow in WebPortalCredits:Vectorized Playing Cards from http://code.google.com/p/vector-playing-cards/ Outer Game LoopEach iterations corresponds to one match of blackjack. A new match begins with the player being dealt two cards and the bank being dealt a single card. It ends with a game over screen, in which the player can decide to have a rematch or end the game. Inner Game LoopIterates over a single match of blackjack and reacts to human player input. The current game state is presented to the player in the game panel.The player can then decide to hit another card or to stand and let the bank draw to 17. At the end of each iteration, the game checks if a winnercan be determined yet. If so, the match ends. to playerHit?Stand?to playerto playerto bank Deal One Card IF Switch Empty Table Creator End IF Recursive Loop End RecursiveLoop Start IF Switch End IF Deal One Card Deal One Card Deal One Card Generic Loop Start Variable ConditionLoop End Check Game State Bank hitsuntil at 17 Game Panel Game Over Screen BlackjackThis workflow implements the Blackjack card game via the Tile View (JavaScript) and CSS Editor nodes as well as the WebPortal functionality. It has an outer game loop that loops over multiple play sessions, and an inner game loop that iterates over the state (i.e., hands ofcards, player decisions taken, etc.) of a single play session.Some Blackjack rules are not implemented yet, but could be added in the feature. These include betting with chips, insurances and the player options to double down, split, or surrender.Ready to play? Run this workflow in WebPortalCredits:Vectorized Playing Cards from http://code.google.com/p/vector-playing-cards/ Outer Game LoopEach iterations corresponds to one match of blackjack. A new match begins with the player being dealt two cards and the bank being dealt a single card. It ends with a game over screen, in which the player can decide to have a rematch or end the game. Inner Game LoopIterates over a single match of blackjack and reacts to human player input. The current game state is presented to the player in the game panel.The player can then decide to hit another card or to stand and let the bank draw to 17. At the end of each iteration, the game checks if a winnercan be determined yet. If so, the match ends. to playerHit?Stand?to playerto playerto bank Deal One Card IF Switch Empty Table Creator End IF Recursive Loop End RecursiveLoop Start IF Switch End IF Deal One Card Deal One Card Deal One Card Generic Loop Start Variable ConditionLoop End Check Game State Bank hitsuntil at 17 Game Panel Game Over Screen

Nodes

Extensions

Links

Download

To use this workflow in KNIME, download it from the below URL and open it in KNIME:

Download Workflow
Created by: Marc
Created at: 2018-11-02
On NodePit since: 2020-04-09
Last update: 2024-12-21
Created with KNIME version: v4.0.2

Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.

Try NodePit Runner!