v0.3.1 progress

[millabasset]

v0.3.1 progress

[MillaBasset]

Suggested by @terpyderp on the Discord: add 1-4 unused buttons that mod makers (modes, rulesets) can purpose into their own creations.

[MillaBasset]

Millisecond based tuning settings

Unfortunately impossible. Would require a large amount of migration as well as adapting the code to not run at 60FPS.

[terpyderp]

Not sure if this is already planned because of the new high score system, but having built in support for showing scoring information on the side of the board without manually having to draw the text with LOVE 2D would be nice lol.

[terpyderp]

Making it so when you game over, the board only gets slightly darker instead of making everything disappear completely. Also maybe displaying some text like "GAME OVER" or "FINISH" when you finish idk. I just think that the current game over is boring and it makes it so you can't see your stack at the end, which is especially important when playing invisible modes imo.

[MillaBasset]

Not sure if this is already planned because of the new high score system, but having built in support for showing scoring information on the side of the board without manually having to draw the text with LOVE 2D would be nice lol.

I'd rather have mod makers choose what to draw and what not to draw in a mode. What will be drawn with the highscore overhaul is the highscore(s) for each mode on the mode select.

[PyrbatNeoxi]

Millisecond based tuning settings

[MillaBasset]

Making it so when you game over, the board only gets slightly darker instead of making everything disappear completely. Also maybe displaying some text like "GAME OVER" or "FINISH" when you finish idk. I just think that the current game over is boring and it makes it so you can't see your stack at the end, which is especially important when playing invisible modes imo.

I could probably make it slightly lighter, but I probably won't add text simply because it could clash with text that a mode maker chooses to use.

[terpyderp]

I'd rather have mod makers choose what to draw and what not to draw in a mode. What will be drawn with the highscore overhaul is the highscore(s) for each mode on the mode select.

Ahh, I just thought it would be nice if there was an optional function that would draw whatever text you wanted, without manually positioning it. Like maybe you could just send an array of strings. Plus then it could be transformed with the board easier. ¯_(ツ)_/¯

[MillaBasset]

I'd rather have mod makers choose what to draw and what not to draw in a mode. What will be drawn with the highscore overhaul is the highscore(s) for each mode on the mode select.

Ahh, I just thought it would be nice if there was an optional function that would draw whatever text you wanted, without manually positioning it. Like maybe you could just send an array of strings. Plus then it could be transformed with the board easier. ¯_(ツ)_/¯

In all fairness, there are onGameOver and onGameComplete functions, which trigger on self.game_over and self.completed respectively. In vanilla modes, onGameComplete is a redirect to onGameOver, but you could make it do different things if you wanted, like drawing text to the screen. Something like this:

function YourMode:onGameOver()
    YourMode.super:onGameOver() -- remove for no default effect
    love.graphics.printf(...)
end

[MillaBasset]

I'd rather not have default functions programmed to do specific things especially when the feature requested is fairly easy to do yourself, because then the documentation grows unnecessarily long (when I do end up writing that).

[terpyderp]

I'd rather not have default functions programmed to do specific things especially when the feature requested is fairly easy to do yourself, because then the documentation grows unnecessarily long (when I do end up writing that).

understandable, have a nice day

[MillaBasset]

Suggested by AgentBasey on the Discord: add DAS to the menus so people don't strain their hands navigating things like the mode select.

[MillaBasset]

More flexible / user BGM support is almost if not fully complete.

Broad description:
If there exist files in the save directory like such:
<save directory>/res/bgm/track1.mp3
<save directory>/res/bgm/track2.ogg
and so on... (extensions can be changed, mixed, and matched, the engine supports many music formats)

A mode maker can play them with:
switchBGM(1)
switchBGMLoop(2)
and so on.

Tracks are searched until a number is reached for which the track does not exist. For example, if track3 did not exist but track1, track2, and track4 did, only the first two tracks would be loaded.

[MillaBasset]

New feature thought of by me: allow mod makers to add more next sounds, for the purpose of creating polyomino rulesets. For example, in the current system, I had to reuse the 7 base next sounds for all pentominoes in the PAIRS ruleset (https://github.com/MillaBasset/cambridge-modpack/blob/0e72e403e024646687e9ad1c0e123f1fbafedbca/tetris/rulesets/pairs.lua#L51). Ideally, someone creating a pentomino ruleset would be able to supply 18 of their own next sounds and use those. Or, alternatively, allow the player to select 18 next sounds that they'd want to use.

When this is finished, next sounds would be dragged and dropped into <save directory>/res/se. How I want it structured in terms of filenames I haven't decided yet.

[MillaBasset]

@terpyderp reminded me I have to refactor the entire draw code for the game scene.

[MillaBasset]

Base refactor of game scene draw code done. New code:

function GameScene:render()
	self.game:drawBackground()
	self.game:drawFrame()
	self.game:drawGrid()
	if self.game.lcd > 0 then self.game:drawLineClearAnimation() end
	self.game:drawPiece()
	self.game:drawNextQueue(self.ruleset)
	self.game:drawScoringInfo()
	self.game:drawReadyGo()
	self.game:drawCustom()

	love.graphics.setColor(1, 1, 1, 1)
	love.graphics.setFont(font_3x5_2)
	if config.gamesettings.display_gamemode == 1 then
		love.graphics.printf(self.game.name .. " - " .. self.ruleset.name, 0, 460, 640, "left")
	end

	love.graphics.setFont(font_3x5_3)
	if self.paused then love.graphics.print("PAUSED!", 80, 100) end

	if self.game.completed then
		self.game:onGameComplete()
	elseif self.game.game_over then
		self.game:onGameOver()
	end
end

I've yet to add board / screen transformations.

[PyrbatNeoxi]

Perhaps a system for checking finesse for faults and counting them? I don't know how easy that'd be to implement though, especially with varying rotations systems

[MillaBasset]

@PyrbatNeoxi: I'd most likely be able to implement a sort of lookahead that doesn't depend on the rotation system being used but this sounds like something that might be better suited implemented in a single gamemode, rather than globally

[MillaBasset]

beta6 will come out soon, which means any feature still listed at the top is scheduled for beta7.

[MillaBasset]

I forgot I had finished giving control of board and screen transformations to the mod maker. Whoops.

[MillaBasset]

• Campaign has been started, first 5 missions done.
• My idea: add a color scheme selection in the settings that can go beyond Arika and TTC colors.
• Suggested: add a randomizer test script utility that can run outside the game, or add a sandbox mode to test randomizers.

[MillaBasset]

Suggested by Electra on the Discord: separate the menu bindings from the game bindings so people can use different, more convenient keys in the menu.

For right now, arrow keys, enter/return, escape, and backspace work in the menus by default.

[MillaBasset]

Suggested on the Discord by @nightmareci and others: instead of giving buttons an explicit label, give buttons a name, such as A, B, C, etc. The context for what the button does would then be dependent on the mode, going hand in hand with giving mod makers extra virtual buttons to do with as they please.

[MillaBasset]

Suggested on the Discord by Kirby703 and others: Toggle the fade out on game over or just include a better default game over effect. (Makes me wonder why I did that to begin with.)

[MillaBasset]

This issue is severely out of date with the progress that's been made - in fact, the last comment was 3 months ago!

Even though v0.3 has been released, there are still features on this list left unimplemented. This will remain open as a general progress thread.

[MillaBasset]

Strikethroughs have been added through completed tasks. Those that are uncompleted shall be worked on whenever.

[MillaBasset]

Going to close this and make a new progress issue as this one hasn't been updated for a while.