Murdoc Loch - Total Noob | Forums

[MurdocLoch]

two questions:

1: when you say iterate do you mean scroll through the index and apply the logic to each slot one tick at a time? If yes, wouldn't this take nearly a full second to get through the index? and then once any pieces are broken the whole index needs to be checked again to slide the new pieces into place? and again it needs to get checked a third time for these new values may also need to be broken. so on and so forth - if i'm understanding iterate correctly, won't that take way too long?

2: what do you mean by flag?

[LukeMSki]

2: what do you mean by flag?

http://en.wikipedia.org/wiki/Flag_(computing)

If I understand correctly, das is referring to Boolean logic. Boolean is either true or false. The flag is set to false, and when the conditions that are required to make it true, the flag turns true. When the flag is true, code is executed.

An example is say you have a score counter, when that score counter reaches 100, you want to give the player a bonus. So you would set it up like this.

Way to score -> Variable Data Source -> Generic Filter = 100 -> bonus code. The flag is the generic filter which is set to false at the beginning of the game, but it can be changed to true.

I hope this made some sense. However, I could be completely wrong so wait for das's confirmation.

[MurdocLoch]

yeah I know how all this stuff works I just don't know the fancy scripting names or the most efficient way to do any of it - for me figuring this stuff out is like a massive Sudoku puzzle - just cause you can count to 9 doesn't mean you can solve the puzzle - I know next to nothing about programming but I know how all these tools work - so it's a nice challenge

[LukeMSki]

yeah I know how all this stuff works I just don't know the fancy scripting names or the most efficient way to do any of it - for me figuring this stuff out is like a massive Sudoku puzzle - just cause you can count to 9 doesn't mean you can solve the puzzle - I know next to nothing about programming but I know how all these tools work - so it's a nice challenge

The problem is that Das thinks everyone know math and programming like he does so a lot of what he says goes of most people's, me included, heads.

[Jarr3tt88]

....and this i why I told you the game was over my head man haha So far what you got looks pretty cool tho

das, it would be SUPER helpful I think if you got a nice cap card and made videos, instead of trying to write paragraphs of info where even people like me who do the complex coding go

[Blastergamer]

Wait, you are better than me at track creating!

[dasraizer]

The problem is that Das thinks everyone know math and programming like he does so a lot of what he says goes of most people's, me included, heads.

not true, i saw the complexity in the video and thought, yeah murdoc can handle it, its just a shame i find it hard to express code in text.

two questions:

1: when you say iterate do you mean scroll through the index and apply the logic to each slot one tick at a time? If yes, wouldn't this take nearly a full second to get through the index? and then once any pieces are broken the whole index needs to be checked again to slide the new pieces into place? and again it needs to get checked a third time for these new values may also need to be broken. so on and so forth - if i'm understanding iterate correctly, won't that take way too long?

1: it should execute each loop i think at most in 6 ticks, best case would be 1.

i've done a helper google doc for looping.

i'll work on doing a grid based doc, thing is i don't want to write your game so its going to be an outline only.

also one thing im thinking your having a nightmare with is the numbered tiles, not sure how u've done this, my guess and im thinking its the only way is you have a big *** block of hidden events pointing to each cell that sets the numbers up, or are you using variation events and road side numbers?

edit:

Gameplay

The game is played with touch controls on a 7x7 square grid. In each round, the player places a disc that falls from the top of the grid. Each disc has a number 1-7, or a blank. Whenever the number of any disc matches the number of contiguous discs in a row or column, that disc disappears and also hits any blank discs it touches. When a blank is hit twice, it turns into a numbered disc. After a number of turns, the round ends and a full row of blank discs emerges from the bottom of the grid. There is no time limit, and discs may be dropped at the player's leisure. The objective is to eliminate discs and score combos for as long as possible until the grid is full and it is impossible to place another disc. If the player clears the screen of all discs, then the player is given a 70,000 point bonus.

There are three modes available[1] – "Normal Mode" is the basic way to play. The player will drop a mixture of colored and gray discs, and the levels will come more frequently as the player goes on; "Hardcore Mode" starts with the levels coming quickly, but the player won't be given gray discs to drop; "Sequence Mode" is exactly like Normal Mode, except the player (and everyone else in the world) will get the same discs in the same order every time.

ouch... hmmm

[LukeMSki]

The problem is that Das thinks everyone know math and programming like he does so a lot of what he says goes of most people's, me included, heads.

not true, i saw the complexity in the video and thought, yeah murdoc can handle it, its just a shame i find it hard to express code in text.

I think it is hard for some people to understand is because you explain stuff without talking about the tools in the editor enough. Looking at the google doc, I could understand a lot more than what you had written since it was shown using the in game tools instead of you speaking in computer programming terms.

[dasraizer]

fair point luke, i try my best to convey in terms of the game language, i really thought i did

anyway found a video of the game and bloody hell it will be tough to achieve in evo, i do think it is possible however.

nailing the order the game does things in would be a 1st step. looks like it drops the number and then checks the neighbours, starting with highest number found it checks its neighbours cell count, then scores if required and rescans for lower numbers until scoring finished, then drops any floaters and runs another check for scoring. not to mention the blank cells.. this poses its own new kind of problem. wow some thought is required for this game, i really don't envy you murdoc

[Jarr3tt88]

Das I pretty much said the same. Man Murdoc if you can pull this game off, seriously....kudos! I think it would be the most complex next to Jezzball, Pac Man and Klax!

I just came off a month build, I don't think I could build anything that complex yet still haha