Buttons, Signals and the Bottom Bar
The bottom bar is very similar to the top bar in terms of the basic principles for aligning and sizing the elements. But in contrast to the top bar, a few additional features are needed:
Now let's add the BottomBar.qml file to our qml folder and fill it with code.
We again only set a fixed height and add a background image that fills the whole bar. The start- and auto-buttons are quite similar to each other. They define an Image that is aligned at the right or the left side of the bar and include some additional features. With the line source: bottomBar.startActive ? "../assets/ButtonStartActive.png" : "../assets/ButtonStart.png", the start-button shows a different image based on the startActive property. Also, when the MouseArea detects a click, we trigger the matching signal. For the auto-button, we use the corresponding properties and signals in the same way.
The buttons to control the bet amount are horizontally centered within the bottom bar and aligned next to each other. For this purpose, we use the Row component, that places all of its child elements in a horizontal row. We can then set the position of the Row component within the bar without worrying about the horizontal alignment of the buttons themselves. For the buttons, we only define an Image that is vertically centered and contains a MouseArea that triggers the correct signal.
That looks like a lot of code, but it's mainly for displaying all the elements correctly and for listening to the events and triggering the signals.
Situs Slot Gacor: Rahasia Menemukan Slot Online dengan Peluang Kemenangan Tinggi
Di dunia perjudian online, istilah “slot gacor” belakangan ini menjadi sangat populer di kalangan pemain. Istilah ini merujuk pada slot online yang dianggap memiliki peluang kemenangan lebih tinggi daripada slot lainnya. Bagi banyak pemain, menemukan situs slot yang gacor merupakan langkah penting untuk meraih kemenangan besar. Artikel ini akan membahas tentang situs slot gacor, cara mengenali slot yang sering memberikan kemenangan, dan strategi untuk meningkatkan peluang menang Anda.
Istilah "gacor" berasal dari bahasa gaul yang berarti "berisik" atau "aktif." Dalam konteks slot online, slot gacor adalah permainan slot yang sering memberikan kemenangan, baik dalam bentuk payout kecil secara konsisten maupun jackpot besar. Banyak pemain percaya bahwa slot yang gacor lebih sering memberikan hasil positif, terutama pada jam-jam tertentu. Meskipun semua slot menggunakan teknologi Random Number Generator (RNG) yang memastikan hasil acak, ada beberapa faktor yang dapat membuat slot tertentu tampak lebih "gacor" di mata pemain.
Beberapa pemain berpengalaman mengatakan bahwa slot yang baru diluncurkan atau yang jarang dimainkan cenderung lebih sering memberikan kemenangan sebagai cara untuk menarik pemain baru. Namun, penting untuk diingat bahwa tidak ada jaminan 100% bahwa Anda akan menang, karena slot pada dasarnya adalah permainan yang didasarkan pada keberuntungan.
Some Minor Improvements
As you can see, the game is quite cool by now. But there are still some things we can work on. In terms of animations, it would be nice to see the player credits increase and decrease fluently. For this purpose, you can just add a Behavior to the scene, that animates the credit amount whenever it is changed.
As of now, whenever we reduce the credit amount to start the slot machine, or when we increase it in case of a win, we can watch the amount change over time. We base the duration for this animation on the current bet amount. The animations for a higher bet, that also lead to higher wins, will take longer. The animation duration in our case spans from 200 ms to 1000 ms for the bet amounts of 4 to 20.
Another cool thing would be to add some additional randomness by changing the delay time for stopping each reel. Per default, the slot machine stops each of its reels 250 ms after the previous one. The property reelStopDelay lets us change this value. If we choose a random value whenever a new spin is started, our slot machine stops its reels with a random delay.
If you want to execute some code every time the slot machine starts a spin, one possibility is to use the spinStarted signal of the slot machine. We use this signal to set a random delay for every spin. Another possibility would be to change the reelStopDelay property within the startSlotMachine() function of our scene.
This was the last feature we cover in this tutorial, but feel free to add some improvements yourself!
In case you need some suggestions for additional features, this is what you can do:
Also visit Felgo Games Examples and Demos to gain more information about game creation with Felgo and to see the source code of existing apps in the app stores.
If you are interested in the full source code of this demo game, see Flask of Rum - Slot Game.
Congratulations, you completed the tutorial and created your own slot game!
Belanja di App banyak untungnya:
Setting Up the Project
The first step is to create a new empty project in Qt Creator. We want the game to be in landscape orientation, so make sure to select this mode during the project setup. When you're done, just add the downloaded images to the assets folder of your project. They should also appear in the Other files\assets directory of the project tree in Qt Creator. Please take care not to add an additional subdirectory that might be created when you unpack the resources archive.
This is how your project tree should look like.
If you are all set, we can finally start to add some code!
First, we want to create the basic game layout that fills the space around the actual slot machine in the middle of the screen. It includes:
The basic game layout consists of a bar at the top, one at the bottom and a beautiful dark red background.
Let us start with a simple game scene, that only defines a few properties and a colored rectangle for our red background. Just replace the current Main.qml file in your qml folder with the following implementation.
With these few lines, we set up our game window to be 960 x 640 px. This is the default window size when you play the game on your computer. On mobile devices, the game window size is different for each device.
We then add a Scene to the game window and configure it as the active scene by stating activeScene: scene. The value scene in this expression refers to the id that we set for our Scene element. The scene in this example has a logical size of 480 x 320 px. All the elements within the scene are scaled up along with the scene to match the game window size. This makes it very easy to add elements, that have a fixed position and size, without worrying about them being smaller on displays with higher resolutions.
Note: There are different scaling modes available in Felgo. The default mode fits the scene to the game window, which may leave empty areas at the side of the screen. To learn more about scaling modes, visit the tutorial How to create mobile games for different screen sizes and resolutions.
The two properties betAmount and creditAmount are global properties for handling the current bet amount and total credit amount of the game. We already set the initial values 4 and 400, so each spin of the slot machine reduces the initial credit amount of 400 by 4 credits. The last element of the scene is the rectangle, that sets our background color. We configure the rectangle to fill up the whole game window and not only the scene. This ensures that the background covers the whole screen on every device.
The top bar is a very distinct element of the scene, that contains additional items like the game logo and the credit amount. It is a good idea to create a separate QML item for such elements to keep your code clean and well structured. Create a new file TopBar.qml in your qml folder and fill it with this code:
The topbar has a height of 50 px, which matches the height of the background Image. But we do not set a fixed width for the top bar at this point. Instead, we configure the background image to fill the whole topbar, so it is possible to set any width for the topbar at a later point and the background image always covers all of it. We will use this behavior to match width of the bar with width of the game screen.
The other elements of the top bar have fixed sizes, but are not placed at a fixed point of the bar. Instead, we anchor the items relatively to the topbar or to one another. This ensures the same relative positions on any device width. For example, the logo is always vertically and horizontally centered.
The icon for the credits is a pile of gold coins that we place 4 px from the left and 8 px from the top of the bar. We then anchor the credit amount text directly to the left of the gold coins and center it vertically. By using scene.creditAmount as the text value, we display the corresponding property of our scene. Furthermore, any changes that occur in the creditAmount property are automatically applied to the text as well. This is possible due to the concept of property binding and erases any worries about keeping the text and the actual credit amount in sync.
And that kids, is how you create the top bar. ;-)
Ciri-Ciri Situs Slot Gacor yang Terpercaya
Memilih situs slot gacor yang aman dan dapat dipercaya adalah langkah pertama untuk memaksimalkan peluang Anda. Berikut adalah beberapa tanda yang menunjukkan bahwa sebuah situs layak untuk dicoba:
Lisensi Resmi: Situs slot gacor yang terpercaya selalu memiliki lisensi dari badan pengawas seperti Malta Gaming Authority atau UK Gambling Commission. Lisensi ini menunjukkan bahwa situs telah diaudit dan beroperasi sesuai dengan standar keamanan yang ketat.
RTP (Return to Player) Tinggi: Situs slot gacor umumnya menawarkan permainan dengan RTP di atas 96%. Semakin tinggi RTP, semakin besar peluang Anda untuk mendapatkan kembali sebagian besar dari taruhan Anda.
Bonus dan Promosi Menarik: Situs yang baik biasanya menawarkan bonus besar, seperti bonus selamat datang, free spins, dan cashback. Manfaatkan promosi ini untuk meningkatkan saldo Anda dan memperpanjang waktu bermain tanpa harus menambah modal.
Ulasan Positif dari Pemain: Membaca ulasan dari pemain lain adalah cara terbaik untuk menilai reputasi sebuah situs. Situs slot gacor umumnya memiliki ulasan positif terkait kecepatan penarikan, keandalan, dan kualitas layanan pelanggan.
Metode Pembayaran Cepat dan Aman: Situs yang andal selalu menyediakan berbagai metode pembayaran yang aman, termasuk e-wallet, transfer bank, dan cryptocurrency. Proses penarikan dana yang cepat menjadi indikator bahwa situs tersebut benar-benar menghargai pemainnya.
Scope of the Tutorial
After you complete this tutorial, you should be well-prepared to create your own slot machine game with Felgo in record time. This tutorial covers:
However, if you just started with Felgo and don't know how to work with Qt Creator or QML, please consider taking a look at the following tutorial:
Also, in order to keep this game simple and leave some room for improvement, we did not add the feature of winning ten free games when three or more flasks of rum form a line. It's up to you to transform the slot machine of this sample game into a full-fledged slot machine that perfectly fits your needs.
In case you prefer to directly look at the source code of the Flask of Rum demo game - you can find it along with the other demos in the Felgo SDK. See here where to find the demo in your SDK directory.
For an overview of the game features, see Flask of Rum - Slot Game.
The only additional resources that you need for this tutorial are some images. They should be placed within the assets directory of the Qt Creator project you are going to create. You can download the images here.
Putting Everything Together
By adding this slot machine to our scene, we can check if everything looks good:
After we state import "slotmachine", we can add the component. We anchor it in the center of the scene and specify the default width and height for the items and reels. As we didn't set a specific height for our symbols, the default values are used for all of them. When you hit play, this already look quite good. But at a closer look, the fixed height allows blank areas above or below the slot machine.
The slot machine is displayed correctly, but the fixed height might lead to blank areas.
Let's correct that! And while we're at it, we can also bring everything to life by adding a handler to the spinEnded signal and implementing the startSlotMachine() function.
We start with aligning the whole slot machine below the top bar. But the topbar image also includes a shadow at the bottom. So we move the slot machine 10px upwards to let the topbar and the slotmachine overlap a bit. Because the top bar is placed on top of the slot machine, it casts its shadow upon it. The same applies to the bottom bar. Only that in this case, the height of the slot machine is set accordingly to let it overlap with the bottom bar.
After setting a dynamic height for the slot machine based on the available space, we also calculate the width and height of the symbols accordingly. And as the last step we also scale the spin velocity along with the item height. If we didn't set a dynamic movement velocity, a slot machine with smaller symbols would appear faster.
For the startSlotMachine() function, we only execute a new spin if the player has enough credits and the slot machine is not currently running. We also set bottomBar.startActive = true to switch the image for the button and prevent changes to the bet amount. We then reduce the player credits and start a new spin. To stop the slot machine, we pass a random interval between 500 and 1000 ms to the spin() function. The slot machine automatically stops after that time has passed and the spinEnded signal is fired.
After every spin, we deactivate the start button again and restart the slot machine if we're on autoplay.
If you run the game at this point, you can already watch the symbols line up and your credits decline for every spin. I know what you are thinking now: "What? I got three captains in a row and didn't win anything?!", but relax, we'll take care of that now!
Adding the Bars to the Scene
I am sure that at this point, you are eager to see both the top and the bottom bar in action. Just add both of them to the main scene and we can see how it looks like.
The two bars are quickly added with just a few lines. Because we prepared the bars to work with any width we want, we can set the width to the actual width of the game window. They then use the whole screen width on every device. For the bottom bar, we also already link the signals to the handler functions, that we added in our scene. Most of the functions can already be implemented:
All of the functions that change the bet amount immediately return when the slot machine is currently running. That's because we want to prevent any changes in the bet amount during a slot machine run. We use the startActive property of the bottom bar for this check. When we start the slot machine, we will activate the start-button and thus also disable bet changes.
That's all for now! You can hit run, play around with the buttons and look at the awesome bars, that always fit the screen!
We Need a Slot Machine
We can finally come to the fun part: The actual slot machine! Felgo offers a special SlotMachine component, that really helps us to get the main tasks done. We don't have to take care of positioning the symbols on multiple reels, spinning the reels or stopping them one after another. This is what we will do:
I suggest we start with the definition of the symbols. Our game uses these ten symbols:
From the left: Flask of Rum, the poker card symbols 10, J, Q, K and A, the parrot, skull, treasure and the captain.
For each of these symbols, we want to define its frequency on the reels. The queen symbol should appear five times on each reel. The captain only exists once. That's why the player wins big when a line of captains appear on the slot machine. We want our slot machine to have five reels, and if three or more symbols form a line at the end of a spin, the player receives credits based on the amount he bet. This table shows you the return factors for each symbol if they form a line of 3, 4 or 5 symbols.
These values are just a configuration setting that you could also choose differently. It would be wise to have a configuration file to store these settings, so it is possible to easily change the symbols and win factors at a later point. We don't want to adapt any code just when some symbol settings change. There are several ways to achieve this. For example, we could add a global configuration property or include a JavaScript file that holds the configuration data. We decided to implement a configuration object as a singleton to show you yet another way how you can add global settings.
In programming languages, singletons are a very common way to implement objects, that should be unique within the application. There can and will be only one instance of a singleton class. They are used for many different tasks. In our case, we define a configuration object as a singleton. We only want one global configuration setting in the application. Also, we do not need to add the singleton to our scene or anywhere else. We can conveniently access the configuration object, with all its properties, signals and functions, directly in other files.
A singleton is forever alone.
It takes two steps to implement a singleton in QML:
We are going to use the SlotMachineModel element to initialize the SlotMachine component with symbol data. This SlotMachineModel can also store additional custom configuration data you might need for each symbol. So how about we take advantage of that and use it to set up our configuration object? Let's create a new folder config in your qml directory and add the file SymbolConfig.qml.
qml/config/SymbolConfig:
This class is just like any other QML class that you define, except for the line pragma Singleton, which marks it as a singleton object. The base class for our object is the SlotMachineModel, which is why we can also use our configuration object to initialize the SlotMachine component. The important property for this initialization is the symbols property. It is required that this property holds a JavaScript object that defines all our symbols as properties, which themselves contain the frequency setting for that symbol and some custom data.
The custom data for each symbol is the place where we can add our additional configuration data like the win factors for each symbol. We decided to not only add the win factors as custom data, but also the source of the image that should be displayed for the symbol. This way, you can easily remove or add symbols later with the desired and symbol image and win factors. In addition, we can add some functions to our class that help us to access our configuration data.
That was already the first step to create a singleton. What's left is to declare a QML type for our singleton object. For this we add a new file qmldir to our qml/config directory. Make sure that this file doesn't have any file type extension like *.qml or *.txt.
This declares that the type SymbolConfig with version 1.0 is implemented in the file SymbolConfig.qml. With this, we configured all the data we need to set up our SlotMachine.
Model, Delegate and the Slot Machine
We want to create a custom slot machine based on the configuration we just added. As mentioned before, the SlotMachine component helps us to easily set up a slot machine. The main part to get a SlotMachine to work is to specify its model and delegate properties.
As we use the SlotMachineModel to set the data for our slot machine, we can move on to defining the appearance of our symbols. Create a new folder slotmachine in your qml directory and add the following Symbol.qml definition.
qml/slotmachine/Symbol.qml:
The symbol item is quite simple: It contains an Image and allows to set the image source using a property alias. We fill the whole item with the Image and add a margin at the top and the bottom.
Note: We do not set a fixed width for the item at this point. This is because we want to set the total size of the slot machine with the symbols based on the available screen size. To be able to do that, we don't specify a width and height for the items initially. The SlotMachine component then automatically sets the item size, if we configure some properties for the default width and height of the items.
As we now have our model and delegate ready, we can create the slot machine in a new file qml/slotmachine/FlaskOfRumMachine.qml.
qml/slotmachine/FlaskOfRumMachine.qml:
The line import "../config" allows us to use our configuration object in this file. But we do not need to import our Symbol QML item, because it is located in the same folder with our FlaskOfRumMachine component. We then base our custom slot machine on the SlotMachine component and set it up to display three rows and five reels. For the model, we can simply pass our singleton configuration object. The slot machine then creates the symbol items, that are defined by the delegate property, with the data of our model. Within the delegate, you can use some special properties to access the data of the SlotMachineModel you created:
After the model and delegate definitions, we also add two images. One that fills the slot machine with a background, another shows white lines as a border between the reels. This image is placed above the background and the created symbols by setting the z property.
