Video Slots (Templates)

Interesting slot template.

I think game design for online slots is surprisingly such a creative field.

So many games by top developers such as NetEnt, Amaya, etc. come up with the quirkiest, eye-catching designs that it's no wonder the players get hooked.

It's unbelievable how great the graphics are these days, and the soundtrack. We've come a long way from the old fashioned days of land-based casinos.

AdrianBaker

Thanks and I agree! There are some very creative online slot games out there. No wonder they are so addictive <img src="{SMILIES_PATH}/icon_lol.gif" alt=":lol:" title="Laughing">

—

Cool, I found the bug and have released a new version, it is pending review in the store so it should be available very soon. In the mean time the new demo is available on http://indie.kiwi/arcade/slots_v3/ <img src="{SMILIES_PATH}/icon_e_biggrin.gif" alt=":D" title="Very Happy">

Release notes:

[quote:3vu9yuto][Mar 12, 2016]

Version 3

• Bug fixes

-- Fix line 8. It used line 3's co-ordinates which caused two lines to be shown and only one marked as a win

-- Fix background tile 11, background was transparent for this tile instead of solid white

IndieKiwi

Awesome!!!

GLWS!

Recently bought your game.... Exceptional work.

Trying to understand the maths. what was the reasoning in this following line in your checkline function

if (value == 0 || value == 9 || value == 10 || value == 11)[/code:1dvyh7z2]

Why did you compare value 9,10,11?

Recently bought your game.... Exceptional work.

Trying to understand the maths. what was the reasoning in this following line in your checkline function

if (value == 0 || value == 9 || value == 10 || value == 11)[/code:19dys2cp]

Why did you compare value 9,10,11?

Thanks for the compliments!

These numbers refer to the frame of the "cards" (as I call them). Please refer to the pay table (Bottom left of the game), the following:

0 = wild

9 = diamond

10 = Crown

11 = "7"

These are special "cards" and allow a win even if only 2 are matched. All the others require at least 3

if ((c[0] == 0 || c[0] == t) && (c[1] == 0 || c[1] == t)) {
	if (t == 0 || t == 9 || t == 10 || t == 11) {
		win = 2;
	}
...
}
[/code:19dys2cp]

The first if statement compares if the first reel and second reel match.
Then the second if statement checks if it is a Wild, Diamond, Crown or "7". If it is, it'll set it to a "2 card" win with a payout of 5 - 10 credits.
The following if statements will then check if there are further matches, to allow "3 - 5" card wins.

Release notes:

[quote:26u5gkiy][Mar 12, 2016]

Version 3

- Bug fixes

-- Fix line 8. It used line 3's co-ordinates which caused two lines to be shown and only one marked as a win

-- Fix background tile 11, background was transparent for this tile instead of solid white

did something got lowered on the spin? seems to work much better as last time... spinning and frames keep up now .. however ... did the winning table success got lowered? cause i get a low win 125/250/500 once in 10/15 spins...sometimes i empty all the 10,000 credits and still doesn't give a win... can this be done using a already winning table.... like in real slot machines and not just pure random?

at the moment the spins happen then when they stop they check the winning table...

However,

the real slot machines... have multiple variations and each time you spin the variations refresh randomly keeping your jackpot success to 0.001% or what ever is set to.....then while the graphics are spinning ...1 variation winning or loosing one is picked... then graphics are stopping based on the picked variations ... if you manage to do that...you got a real slot machine system... plus there should be a 2 items win for the first rows as the cherry "lowest special item" on most of slots... if you do this its gonna be the best game engine/ slot machine ever made... and u can actually increase your price on the engine.

But the above are more complicated then it looks just by typing it, it wold be just awesome if you could just make a global variable to increase decrease the success % of the game for us who dont know ur XML format wold be great... just a few tips, i see could work on this product you made ... it has huge potential, just needs some small tweaks to become a Ruby.

BTW guys if you looking for a good just to reskin slot machine system this is it.

Hi —

Only the listed changes were made for the last update.

As for the Variations of preset wins, this template is designed with some "physics" and collision detection, so to increase odds you could increase the rate of certain "cards" spawning. Enforcing presets may not be possible due to the physics like behavior.

Yes this template does include 2 card wins for wild, diamond, crown, "7" (see my previous post on this thread )

The XML contains payout rates only, not the % of success.

To "Rig" which cards get spawned and therefore increase odds of winning:

1. Create a local variable and generate a random number between 1 - 1000 and set it to the local variable, this should happen for every "card" that spawns.

2. If the card is between 1 - 10, spawn card with frame 0, if it is between 11 - 100, spawn card with frame 1 etc. Sometimes if you preset and want a type of win, you can increase the range for the card for this spin.

...

To "Rig" which cards get spawned and therefore increase odds of winning:

1. Create a local variable and generate a random number between 1 - 1000 and set it to the local variable, this should happen for every "card" that spawns.

2. If the card is between 1 - 10, spawn card with frame 0, if it is between 11 - 100, spawn card with frame 1 etc. Sometimes if you preset and want a type of win, you can increase the range for the card for this spin.

yea that is awesome tip, i was looking at it as maybe to normal approach i guess thanks il give it a try love your work man keep it up.

any update on the "falling cards" ?

You can recreate that "bug" by playing on very low fps

any update on the "falling cards" ?

You can recreate that "bug" by playing on very low fps

Hi, this depends on the physics/collision detection. So with the way this template is designed, it'll continue to behave this way for less powerful devices, unless the spawning behavior is changed to another approach.