SketchyMaze/doodle
SketchyMaze/doodle
1
0
Fork 0
Code Issues 41 Pull Requests 1 Releases Wiki Activity
actor-collision
doodle/pkg/cheats.go

290 lines
8.4 KiB
Go
Raw Permalink Normal View History

The Window Manager Update * Take advantage of the new Window Manager feature of the UI toolkit. * Move the MenuScene's "New Level" and "Play/Edit Level" windows into stand-alone functions in new pkg/windows/ package. The 'windows' package is isolated from the rest of Doodle and communicates using config variables and callback functions to avoid circular dependency. * MenuScene calls the window constructors from the new package. * Add an "Options" button to the Menu Bar in the Editor Scene, which opens the "New Level" window to allow changing the wallpaper or bounding type of the level currently being edited. * Move the cheat codes into their own file, cheats.go
2020-04-07 06:21:17 +00:00
package doodle
Technical Doodad: Checkpoint Region The Checkpoint Region acts as an invisible checkpoint flag, remembering the player's location should they need to respawn there. New cheat: `show all actors` during Play Mode will make every hidden actor visible. Useful to see your technical doodads during gameplay! Developer shell: `Execute(command string)` is available to the JavaScript interpreter. It simulates another command being run on the developer console.
2021-10-03 04:12:57 +00:00
import (
New Doodad: Blue Bird * The blue bird follows the same base AI as the red bird (it has a target altitude that it tries to maintain, and it will dive at the player) but the blue bird flies in a sine wave pattern around its target altitude. It also has a longer scan radius to search for the player than the red bird. * The sine wave pattern of the blue bird means you may fly under its radar depending how high it is on average. Cheat codes that replace the player character are refactored to make it easier to extend, and new cheats have been added: * super azulian: play as the Red Azulian. * hyper azulian: play as the White Azulian. * bluebird: play as the new Bird (blue).
2022-05-01 00:59:55 +00:00
"strings"
Spit and polish UI improvements specifically for mobile (running the game with the `-w mobile` or `-w landscape` options) screen sizes. * Rework the Settings window to be mobile friendly to landscape oriented screens (`doodle -w landscape`) and migrate Options tab to magicform. * The toolbar in the Editor will be a single column of buttons on small screens, such as `-w mobile` (375x812) portrait mode smartphone. On larger screens the toolbar shows in two columns of buttons. * Fix tooltips not drawing on top. * Centralize the hard-coded references to specific font filenames * Add cheat code: `test load screen` to bring a sample loading screen up for a few seconds. It needs improvement on `-w landscape`
2022-03-06 06:44:54 +00:00
"time"
Rename Go module
2022-09-24 22:17:25 +00:00
"git.kirsle.net/SketchyMaze/doodle/pkg/balance"
Wait Modal * Add modal.Wait() that creates a global progress bar modal which is not dismissable by the user; the caller must Dismiss() the modal themselves when ready. * It will be useful in the future in case e.g. saving a Level needs to take a while to rebalance chunks and the modal prevents ALL interaction with the game so the user can't further modify the level while it's busy refactoring itself. * Cheat code: "test wait screen" to show the Wait modal for 10 seconds.
2022-09-25 01:39:02 +00:00
"git.kirsle.net/SketchyMaze/doodle/pkg/modal"
Rename Go module
2022-09-24 22:17:25 +00:00
"git.kirsle.net/SketchyMaze/doodle/pkg/modal/loadscreen"
Add cheat code to send power to all actors
2023-02-18 22:21:07 +00:00
"git.kirsle.net/SketchyMaze/doodle/pkg/scripting"
Cheats Menu UI * Added a Cheats Menu UI accessible from the Settings window's "Experimental" tab and from there you can enable the Cheats Menu from the "Help" screen of the gameplay mode. * Commonly used cheats all have corresponding buttons to click on, especially helpful for touchscreen devices like the Pinephone where keyboard input doesn't always work reliably. * The buttons in the Cheats Menu just automate entry of the cheat commands. * `boolProp` command has a new `flip` option to toggle their value (e.g. `boolProp show-hidden-doodads flip`)
2023-01-02 20:36:12 +00:00
"git.kirsle.net/SketchyMaze/doodle/pkg/shmem"
"git.kirsle.net/SketchyMaze/doodle/pkg/windows"
"git.kirsle.net/go/ui"
Add cheat code to send power to all actors
2023-02-18 22:21:07 +00:00
"github.com/dop251/goja"
Technical Doodad: Checkpoint Region The Checkpoint Region acts as an invisible checkpoint flag, remembering the player's location should they need to respawn there. New cheat: `show all actors` during Play Mode will make every hidden actor visible. Useful to see your technical doodads during gameplay! Developer shell: `Execute(command string)` is available to the JavaScript interpreter. It simulates another command being run on the developer console.
2021-10-03 04:12:57 +00:00
)
Death Barrier and Player Character Cheat Codes * Added the Death Barrier to Play Mode to catch players from falling off the map and then falling indefinitely, especially on Unbounded maps. * The Death Barrier is set 1,000 pixels below the lowest point on your map. If the player falls here they get a death message: "Watch out for falling off the map!" * Added cheat codes to change the default Player Character doodad, as a way to force play as a different character (for levels which don't specify a custom character): * Play as Bird: fly like a bird * Play as Blue Azulian: the cell * Play as Thief: play as thief * Reset to default (Boy): pinocchio
2021-08-16 00:01:18 +00:00
Centralize cheats, detect cheated player character * If the player runs the PlayAsBird cheat they shouldn't be able to win a high score on a level, so at level startup it detects whether the DefaultPlayerCharacterDoodad has changed from default on a level that doesn't use the Start Flag to set a specific doodad - and immediately marks the session as cheated
2022-01-09 02:27:37 +00:00
// IsDefaultPlayerCharacter checks whether the DefaultPlayerCharacter doodad has
// been modified
Cheats Menu UI * Added a Cheats Menu UI accessible from the Settings window's "Experimental" tab and from there you can enable the Cheats Menu from the "Help" screen of the gameplay mode. * Commonly used cheats all have corresponding buttons to click on, especially helpful for touchscreen devices like the Pinephone where keyboard input doesn't always work reliably. * The buttons in the Cheats Menu just automate entry of the cheat commands. * `boolProp` command has a new `flip` option to toggle their value (e.g. `boolProp show-hidden-doodads flip`)
2023-01-02 20:36:12 +00:00
// MakeCheatsWindow initializes the windows/cheats_menu.go window from anywhere you need it,
// binding all the variables in. If you pass a nil Supervisor, this function will attempt to
// find one based on your Scene and
func (d *Doodle) MakeCheatsWindow(supervisor *ui.Supervisor) *ui.Window {
// If not given a supervisor, try and find one.
if supervisor == nil {
if v, err := d.FindLikelySupervisor(); err != nil {
d.FlashError("Couldn't make cheats window: %s", err)
return nil
} else {
supervisor = v
}
}
cfg := windows.CheatsMenu{
Supervisor: supervisor,
Engine: d.Engine,
SceneName: func() string {
return d.Scene.Name()
},
RunCommand: func(command string) {
Update README and fix perfect run icon display
2023-02-18 05:49:19 +00:00
// If we are in Play Mode, every command out of here is cheating.
if playScene, ok := d.Scene.(*PlayScene); ok {
playScene.SetCheated()
}
Cheats Menu UI * Added a Cheats Menu UI accessible from the Settings window's "Experimental" tab and from there you can enable the Cheats Menu from the "Help" screen of the gameplay mode. * Commonly used cheats all have corresponding buttons to click on, especially helpful for touchscreen devices like the Pinephone where keyboard input doesn't always work reliably. * The buttons in the Cheats Menu just automate entry of the cheat commands. * `boolProp` command has a new `flip` option to toggle their value (e.g. `boolProp show-hidden-doodads flip`)
2023-01-02 20:36:12 +00:00
d.shell.Execute(command)
},
OnSetPlayerCharacter: func(doodad string) {
if scene, ok := d.Scene.(*PlayScene); ok {
Update README and fix perfect run icon display
2023-02-18 05:49:19 +00:00
scene.SetCheated()
Cheats Menu UI * Added a Cheats Menu UI accessible from the Settings window's "Experimental" tab and from there you can enable the Cheats Menu from the "Help" screen of the gameplay mode. * Commonly used cheats all have corresponding buttons to click on, especially helpful for touchscreen devices like the Pinephone where keyboard input doesn't always work reliably. * The buttons in the Cheats Menu just automate entry of the cheat commands. * `boolProp` command has a new `flip` option to toggle their value (e.g. `boolProp show-hidden-doodads flip`)
2023-01-02 20:36:12 +00:00
scene.SetPlayerCharacter(doodad)
} else {
shmem.FlashError("This only works during Play Mode.")
}
},
}
return windows.MakeCheatsMenu(cfg)
}
Cheat: $ d.SetPlayerCharacter("anything.doodad") Too restricted by the cheat codes to play as certain characters on-demand? Use the JS shell in the developer console to set any doodad you want: $ d.SetPlayerCharacter("key-blue") $ d.SetPlayerCharacter("anvil") $ d.SetPlayerCharacter("box.doodad") The .doodad suffix is optional. Interesting behaviors when playing as odd doodads: * Most non-mobile doodads don't collide with each other, so you can pass through doors and not activate buttons if you play as a key or a trapdoor. Non-mobile doodads also generally have antigravity so you can fly freely around the map. * Non-mobile doodads can not open Warp Doors or interact with the Exit Flag. You'll have to change back to a creature such as "boy" or "azu-blue" to win the level. * If you are a key, the Thief can collect you! This removes your player doodad from the level and soft locks the game. No worries, another call to d.SetPlayerCharacter() will put you back on the map! * If the doodad name isn't found, you'll play as the built-in fallback doodad, which is just a red "X" shape. It has anti-gravity and does not generally interact with any doodad (can not push buttons or collect keys - but it can pass through doors and other obstacles. Can not win the level goal flag, though!)
2022-04-30 04:27:07 +00:00
// SetPlayerCharacter -- this is designed to be called in-game with the developer
// console. Sets your player character to whatever doodad you want, not just the
// few that have cheat codes. If you set an invalid filename, you become the
// dummy default doodad sprite (a red "X").
func (d *Doodle) SetPlayerCharacter(filename string) {
balance.PlayerCharacterDoodad = filename
if playScene, isPlay := d.Scene.(*PlayScene); isPlay {
playScene.SetPlayerCharacter(balance.PlayerCharacterDoodad)
}
}
The Window Manager Update * Take advantage of the new Window Manager feature of the UI toolkit. * Move the MenuScene's "New Level" and "Play/Edit Level" windows into stand-alone functions in new pkg/windows/ package. The 'windows' package is isolated from the rest of Doodle and communicates using config variables and callback functions to avoid circular dependency. * MenuScene calls the window constructors from the new package. * Add an "Options" button to the Menu Bar in the Editor Scene, which opens the "New Level" window to allow changing the wallpaper or bounding type of the level currently being edited. * Move the cheat codes into their own file, cheats.go
2020-04-07 06:21:17 +00:00
// cheatCommand is a subroutine of the Command.Run() method of the Doodle
// developer shell (commands.go). It looks for special cheat codes entered
// into the command shell and executes them.
//
// Returns true if a cheat was intercepted, false if the command is not a cheat.
func (c Command) cheatCommand(d *Doodle) bool {
// Some cheats only work in Play Mode.
playScene, isPlay := d.Scene.(*PlayScene)
Optimize memory by freeing up SDL2 textures * Added to the F3 Debug Overlay is a "Texture:" label that counts the number of textures currently loaded by the (SDL2) render engine. * Added Teardown() functions to Level, Doodad and the Chunker they both use to free up SDL2 textures for all their cached graphics. * The Canvas.Destroy() function now cleans up all textures that the Canvas is responsible for: calling the Teardown() of the Level or Doodad, calling Destroy() on all level actors, and cleaning up Wallpaper textures. * The Destroy() method of the game's various Scenes will properly Destroy() their canvases to clean up when transitioning to another scene. The MainScene, MenuScene, EditorScene and PlayScene. * Fix the sprites package to actually cache the ui.Image widgets. The game has very few sprites so no need to free them just yet. Some tricky places that were leaking textures have been cleaned up: * Canvas.InstallActors() destroys the canvases of existing actors before it reinitializes the list and installs the replacements. * The DraggableActor when the user is dragging an actor around their level cleans up the blueprint masked drag/drop actor before nulling it out. Misc changes: * The player character cheats during Play Mode will immediately swap out the player character on the current level. * Properly call the Close() function instead of Hide() to dismiss popup windows. The Close() function itself calls Hide() but also triggers WindowClose event handlers. The Doodad Dropper subscribes to its close event to free textures for all its doodad canvases.
2022-04-09 21:41:24 +00:00
// If a character cheat is used during Play Mode, replace the player NOW.
var setPlayerCharacter bool
The Window Manager Update * Take advantage of the new Window Manager feature of the UI toolkit. * Move the MenuScene's "New Level" and "Play/Edit Level" windows into stand-alone functions in new pkg/windows/ package. The 'windows' package is isolated from the rest of Doodle and communicates using config variables and callback functions to avoid circular dependency. * MenuScene calls the window constructors from the new package. * Add an "Options" button to the Menu Bar in the Editor Scene, which opens the "New Level" window to allow changing the wallpaper or bounding type of the level currently being edited. * Move the cheat codes into their own file, cheats.go
2020-04-07 06:21:17 +00:00
// Cheat codes
switch c.Raw {
Centralize cheats, detect cheated player character * If the player runs the PlayAsBird cheat they shouldn't be able to win a high score on a level, so at level startup it detects whether the DefaultPlayerCharacterDoodad has changed from default on a level that doesn't use the Start Flag to set a specific doodad - and immediately marks the session as cheated
2022-01-09 02:27:37 +00:00
case balance.CheatUncapFPS:
The Window Manager Update * Take advantage of the new Window Manager feature of the UI toolkit. * Move the MenuScene's "New Level" and "Play/Edit Level" windows into stand-alone functions in new pkg/windows/ package. The 'windows' package is isolated from the rest of Doodle and communicates using config variables and callback functions to avoid circular dependency. * MenuScene calls the window constructors from the new package. * Add an "Options" button to the Menu Bar in the Editor Scene, which opens the "New Level" window to allow changing the wallpaper or bounding type of the level currently being edited. * Move the cheat codes into their own file, cheats.go
2020-04-07 06:21:17 +00:00
if fpsDoNotCap {
d.Flash("Reset frame rate throttle to factory default FPS")
} else {
d.Flash("Unleashing as many frames as we can render!")
}
fpsDoNotCap = !fpsDoNotCap
Centralize cheats, detect cheated player character * If the player runs the PlayAsBird cheat they shouldn't be able to win a high score on a level, so at level startup it detects whether the DefaultPlayerCharacterDoodad has changed from default on a level that doesn't use the Start Flag to set a specific doodad - and immediately marks the session as cheated
2022-01-09 02:27:37 +00:00
case balance.CheatEditDuringPlay:
The Window Manager Update * Take advantage of the new Window Manager feature of the UI toolkit. * Move the MenuScene's "New Level" and "Play/Edit Level" windows into stand-alone functions in new pkg/windows/ package. The 'windows' package is isolated from the rest of Doodle and communicates using config variables and callback functions to avoid circular dependency. * MenuScene calls the window constructors from the new package. * Add an "Options" button to the Menu Bar in the Editor Scene, which opens the "New Level" window to allow changing the wallpaper or bounding type of the level currently being edited. * Move the cheat codes into their own file, cheats.go
2020-04-07 06:21:17 +00:00
if isPlay {
playScene.drawing.Editable = true
Savegame and High Scores * Adds pkg/savegame to store user progress thru Level Packs. * The savegame.json is mildly tamper resistant by including a checksum along with the JSON body. * The checksum combines the JSON string + an app secret (in savegame.go) + user specific entropy (stored in their settings.json). If the user modifies their save file and the checksum becomes invalid the game will not load the save file, acting like it didn't exist, resetting all their high scores. Updates to the Story Mode window: * On the LevelPacks list: shows e.g. "[completed 0 of 3 levels]" showing a user's progress thru the level pack. * Below the levels on the Detail screen: * Shows an indicator whether the level is completed or not. * Shows high scores (fastest times beating the level) * Shows a padlock icon if levels are locked and the player hasn't reached them yet. Pops up an Alert modal if a locked level is clicked on. Scoring is based around your fastest time elapsed to finish the level. * Perfect Time (gold coin): player has not died during the level. * Best Time (silver coin): player has continued from a checkpoint. In-game an elapsed timer is shown in the top left corner along with the gold or silver coin indicating if your run has been Perfect. If the user enters any Cheat Codes during gameplay they are not eligible to win a high score, but the level will still be marked as completed. The icon next to the in-game timer disappears when a cheat code has been entered.
2022-01-03 00:28:43 +00:00
playScene.SetCheated()
The Window Manager Update * Take advantage of the new Window Manager feature of the UI toolkit. * Move the MenuScene's "New Level" and "Play/Edit Level" windows into stand-alone functions in new pkg/windows/ package. The 'windows' package is isolated from the rest of Doodle and communicates using config variables and callback functions to avoid circular dependency. * MenuScene calls the window constructors from the new package. * Add an "Options" button to the Menu Bar in the Editor Scene, which opens the "New Level" window to allow changing the wallpaper or bounding type of the level currently being edited. * Move the cheat codes into their own file, cheats.go
2020-04-07 06:21:17 +00:00
d.Flash("Level canvas is now editable. Don't edit and drive!")
} else {
Async Giant Screenshot, Player Physics and UI Polish * The "Giant Screenshot" feature takes a very long time, so it is made asynchronous. If you try and run a second one while the first is busy, you get an error flash. You can continue editing the level, even playtest it, or load a different level, and it will continue crunching on the Giant Screenshot and flash when it's finished. * Updated the player physics to use proper Velocity to jump off the ground rather than the hacky timer-based fixed speed approach. * FlashError() function to flash "error level" messages to the screen. They appear in orange text instead of the usual blue, and most error messages in the game use this now. The dev console "error <msg>" command can simulate an error message. * Flashed message fonts are updated. The blue font now uses softer stroke and shadow colors and the same algorithm applies to the orange error flashes. Some other changes to player physics: * Max velocity, acceleration speed, and gravity have been tweaked. * Fast turn-around if you are moving right and then need to go left. Your velocity resets to zero at the transition so you quickly get going the way you want to go. Some levels that need a bit of love for the new platforming physics: * Tutorial 3.level
2021-10-08 01:24:18 +00:00
d.FlashError("Use this cheat in Play Mode to make the level canvas editable.")
The Window Manager Update * Take advantage of the new Window Manager feature of the UI toolkit. * Move the MenuScene's "New Level" and "Play/Edit Level" windows into stand-alone functions in new pkg/windows/ package. The 'windows' package is isolated from the rest of Doodle and communicates using config variables and callback functions to avoid circular dependency. * MenuScene calls the window constructors from the new package. * Add an "Options" button to the Menu Bar in the Editor Scene, which opens the "New Level" window to allow changing the wallpaper or bounding type of the level currently being edited. * Move the cheat codes into their own file, cheats.go
2020-04-07 06:21:17 +00:00
}
Centralize cheats, detect cheated player character * If the player runs the PlayAsBird cheat they shouldn't be able to win a high score on a level, so at level startup it detects whether the DefaultPlayerCharacterDoodad has changed from default on a level that doesn't use the Start Flag to set a specific doodad - and immediately marks the session as cheated
2022-01-09 02:27:37 +00:00
case balance.CheatScrollDuringPlay:
The Window Manager Update * Take advantage of the new Window Manager feature of the UI toolkit. * Move the MenuScene's "New Level" and "Play/Edit Level" windows into stand-alone functions in new pkg/windows/ package. The 'windows' package is isolated from the rest of Doodle and communicates using config variables and callback functions to avoid circular dependency. * MenuScene calls the window constructors from the new package. * Add an "Options" button to the Menu Bar in the Editor Scene, which opens the "New Level" window to allow changing the wallpaper or bounding type of the level currently being edited. * Move the cheat codes into their own file, cheats.go
2020-04-07 06:21:17 +00:00
if isPlay {
playScene.drawing.Scrollable = true
Savegame and High Scores * Adds pkg/savegame to store user progress thru Level Packs. * The savegame.json is mildly tamper resistant by including a checksum along with the JSON body. * The checksum combines the JSON string + an app secret (in savegame.go) + user specific entropy (stored in their settings.json). If the user modifies their save file and the checksum becomes invalid the game will not load the save file, acting like it didn't exist, resetting all their high scores. Updates to the Story Mode window: * On the LevelPacks list: shows e.g. "[completed 0 of 3 levels]" showing a user's progress thru the level pack. * Below the levels on the Detail screen: * Shows an indicator whether the level is completed or not. * Shows high scores (fastest times beating the level) * Shows a padlock icon if levels are locked and the player hasn't reached them yet. Pops up an Alert modal if a locked level is clicked on. Scoring is based around your fastest time elapsed to finish the level. * Perfect Time (gold coin): player has not died during the level. * Best Time (silver coin): player has continued from a checkpoint. In-game an elapsed timer is shown in the top left corner along with the gold or silver coin indicating if your run has been Perfect. If the user enters any Cheat Codes during gameplay they are not eligible to win a high score, but the level will still be marked as completed. The icon next to the in-game timer disappears when a cheat code has been entered.
2022-01-03 00:28:43 +00:00
playScene.SetCheated()
The Window Manager Update * Take advantage of the new Window Manager feature of the UI toolkit. * Move the MenuScene's "New Level" and "Play/Edit Level" windows into stand-alone functions in new pkg/windows/ package. The 'windows' package is isolated from the rest of Doodle and communicates using config variables and callback functions to avoid circular dependency. * MenuScene calls the window constructors from the new package. * Add an "Options" button to the Menu Bar in the Editor Scene, which opens the "New Level" window to allow changing the wallpaper or bounding type of the level currently being edited. * Move the cheat codes into their own file, cheats.go
2020-04-07 06:21:17 +00:00
d.Flash("Level canvas is now scrollable with the arrow keys.")
} else {
Async Giant Screenshot, Player Physics and UI Polish * The "Giant Screenshot" feature takes a very long time, so it is made asynchronous. If you try and run a second one while the first is busy, you get an error flash. You can continue editing the level, even playtest it, or load a different level, and it will continue crunching on the Giant Screenshot and flash when it's finished. * Updated the player physics to use proper Velocity to jump off the ground rather than the hacky timer-based fixed speed approach. * FlashError() function to flash "error level" messages to the screen. They appear in orange text instead of the usual blue, and most error messages in the game use this now. The dev console "error <msg>" command can simulate an error message. * Flashed message fonts are updated. The blue font now uses softer stroke and shadow colors and the same algorithm applies to the orange error flashes. Some other changes to player physics: * Max velocity, acceleration speed, and gravity have been tweaked. * Fast turn-around if you are moving right and then need to go left. Your velocity resets to zero at the transition so you quickly get going the way you want to go. Some levels that need a bit of love for the new platforming physics: * Tutorial 3.level
2021-10-08 01:24:18 +00:00
d.FlashError("Use this cheat in Play Mode to make the level scrollable.")
The Window Manager Update * Take advantage of the new Window Manager feature of the UI toolkit. * Move the MenuScene's "New Level" and "Play/Edit Level" windows into stand-alone functions in new pkg/windows/ package. The 'windows' package is isolated from the rest of Doodle and communicates using config variables and callback functions to avoid circular dependency. * MenuScene calls the window constructors from the new package. * Add an "Options" button to the Menu Bar in the Editor Scene, which opens the "New Level" window to allow changing the wallpaper or bounding type of the level currently being edited. * Move the cheat codes into their own file, cheats.go
2020-04-07 06:21:17 +00:00
}
Centralize cheats, detect cheated player character * If the player runs the PlayAsBird cheat they shouldn't be able to win a high score on a level, so at level startup it detects whether the DefaultPlayerCharacterDoodad has changed from default on a level that doesn't use the Start Flag to set a specific doodad - and immediately marks the session as cheated
2022-01-09 02:27:37 +00:00
case balance.CheatAntigravity:
The Window Manager Update * Take advantage of the new Window Manager feature of the UI toolkit. * Move the MenuScene's "New Level" and "Play/Edit Level" windows into stand-alone functions in new pkg/windows/ package. The 'windows' package is isolated from the rest of Doodle and communicates using config variables and callback functions to avoid circular dependency. * MenuScene calls the window constructors from the new package. * Add an "Options" button to the Menu Bar in the Editor Scene, which opens the "New Level" window to allow changing the wallpaper or bounding type of the level currently being edited. * Move the cheat codes into their own file, cheats.go
2020-04-07 06:21:17 +00:00
if isPlay {
Savegame and High Scores * Adds pkg/savegame to store user progress thru Level Packs. * The savegame.json is mildly tamper resistant by including a checksum along with the JSON body. * The checksum combines the JSON string + an app secret (in savegame.go) + user specific entropy (stored in their settings.json). If the user modifies their save file and the checksum becomes invalid the game will not load the save file, acting like it didn't exist, resetting all their high scores. Updates to the Story Mode window: * On the LevelPacks list: shows e.g. "[completed 0 of 3 levels]" showing a user's progress thru the level pack. * Below the levels on the Detail screen: * Shows an indicator whether the level is completed or not. * Shows high scores (fastest times beating the level) * Shows a padlock icon if levels are locked and the player hasn't reached them yet. Pops up an Alert modal if a locked level is clicked on. Scoring is based around your fastest time elapsed to finish the level. * Perfect Time (gold coin): player has not died during the level. * Best Time (silver coin): player has continued from a checkpoint. In-game an elapsed timer is shown in the top left corner along with the gold or silver coin indicating if your run has been Perfect. If the user enters any Cheat Codes during gameplay they are not eligible to win a high score, but the level will still be marked as completed. The icon next to the in-game timer disappears when a cheat code has been entered.
2022-01-03 00:28:43 +00:00
playScene.SetCheated()
The Window Manager Update * Take advantage of the new Window Manager feature of the UI toolkit. * Move the MenuScene's "New Level" and "Play/Edit Level" windows into stand-alone functions in new pkg/windows/ package. The 'windows' package is isolated from the rest of Doodle and communicates using config variables and callback functions to avoid circular dependency. * MenuScene calls the window constructors from the new package. * Add an "Options" button to the Menu Bar in the Editor Scene, which opens the "New Level" window to allow changing the wallpaper or bounding type of the level currently being edited. * Move the cheat codes into their own file, cheats.go
2020-04-07 06:21:17 +00:00
playScene.antigravity = !playScene.antigravity
playScene.Player.SetGravity(!playScene.antigravity)
if playScene.antigravity {
d.Flash("Gravity disabled for player character.")
} else {
d.Flash("Gravity restored for player character.")
}
} else {
Async Giant Screenshot, Player Physics and UI Polish * The "Giant Screenshot" feature takes a very long time, so it is made asynchronous. If you try and run a second one while the first is busy, you get an error flash. You can continue editing the level, even playtest it, or load a different level, and it will continue crunching on the Giant Screenshot and flash when it's finished. * Updated the player physics to use proper Velocity to jump off the ground rather than the hacky timer-based fixed speed approach. * FlashError() function to flash "error level" messages to the screen. They appear in orange text instead of the usual blue, and most error messages in the game use this now. The dev console "error <msg>" command can simulate an error message. * Flashed message fonts are updated. The blue font now uses softer stroke and shadow colors and the same algorithm applies to the orange error flashes. Some other changes to player physics: * Max velocity, acceleration speed, and gravity have been tweaked. * Fast turn-around if you are moving right and then need to go left. Your velocity resets to zero at the transition so you quickly get going the way you want to go. Some levels that need a bit of love for the new platforming physics: * Tutorial 3.level
2021-10-08 01:24:18 +00:00
d.FlashError("Use this cheat in Play Mode to disable gravity for the player character.")
The Window Manager Update * Take advantage of the new Window Manager feature of the UI toolkit. * Move the MenuScene's "New Level" and "Play/Edit Level" windows into stand-alone functions in new pkg/windows/ package. The 'windows' package is isolated from the rest of Doodle and communicates using config variables and callback functions to avoid circular dependency. * MenuScene calls the window constructors from the new package. * Add an "Options" button to the Menu Bar in the Editor Scene, which opens the "New Level" window to allow changing the wallpaper or bounding type of the level currently being edited. * Move the cheat codes into their own file, cheats.go
2020-04-07 06:21:17 +00:00
}
Centralize cheats, detect cheated player character * If the player runs the PlayAsBird cheat they shouldn't be able to win a high score on a level, so at level startup it detects whether the DefaultPlayerCharacterDoodad has changed from default on a level that doesn't use the Start Flag to set a specific doodad - and immediately marks the session as cheated
2022-01-09 02:27:37 +00:00
case balance.CheatNoclip:
The Window Manager Update * Take advantage of the new Window Manager feature of the UI toolkit. * Move the MenuScene's "New Level" and "Play/Edit Level" windows into stand-alone functions in new pkg/windows/ package. The 'windows' package is isolated from the rest of Doodle and communicates using config variables and callback functions to avoid circular dependency. * MenuScene calls the window constructors from the new package. * Add an "Options" button to the Menu Bar in the Editor Scene, which opens the "New Level" window to allow changing the wallpaper or bounding type of the level currently being edited. * Move the cheat codes into their own file, cheats.go
2020-04-07 06:21:17 +00:00
if isPlay {
Savegame and High Scores * Adds pkg/savegame to store user progress thru Level Packs. * The savegame.json is mildly tamper resistant by including a checksum along with the JSON body. * The checksum combines the JSON string + an app secret (in savegame.go) + user specific entropy (stored in their settings.json). If the user modifies their save file and the checksum becomes invalid the game will not load the save file, acting like it didn't exist, resetting all their high scores. Updates to the Story Mode window: * On the LevelPacks list: shows e.g. "[completed 0 of 3 levels]" showing a user's progress thru the level pack. * Below the levels on the Detail screen: * Shows an indicator whether the level is completed or not. * Shows high scores (fastest times beating the level) * Shows a padlock icon if levels are locked and the player hasn't reached them yet. Pops up an Alert modal if a locked level is clicked on. Scoring is based around your fastest time elapsed to finish the level. * Perfect Time (gold coin): player has not died during the level. * Best Time (silver coin): player has continued from a checkpoint. In-game an elapsed timer is shown in the top left corner along with the gold or silver coin indicating if your run has been Perfect. If the user enters any Cheat Codes during gameplay they are not eligible to win a high score, but the level will still be marked as completed. The icon next to the in-game timer disappears when a cheat code has been entered.
2022-01-03 00:28:43 +00:00
playScene.SetCheated()
The Window Manager Update * Take advantage of the new Window Manager feature of the UI toolkit. * Move the MenuScene's "New Level" and "Play/Edit Level" windows into stand-alone functions in new pkg/windows/ package. The 'windows' package is isolated from the rest of Doodle and communicates using config variables and callback functions to avoid circular dependency. * MenuScene calls the window constructors from the new package. * Add an "Options" button to the Menu Bar in the Editor Scene, which opens the "New Level" window to allow changing the wallpaper or bounding type of the level currently being edited. * Move the cheat codes into their own file, cheats.go
2020-04-07 06:21:17 +00:00
playScene.noclip = !playScene.noclip
playScene.Player.SetNoclip(playScene.noclip)
playScene.antigravity = playScene.noclip
playScene.Player.SetGravity(!playScene.antigravity)
if playScene.noclip {
d.Flash("Clipping disabled for player character.")
} else {
d.Flash("Clipping and gravity restored for player character.")
}
} else {
Async Giant Screenshot, Player Physics and UI Polish * The "Giant Screenshot" feature takes a very long time, so it is made asynchronous. If you try and run a second one while the first is busy, you get an error flash. You can continue editing the level, even playtest it, or load a different level, and it will continue crunching on the Giant Screenshot and flash when it's finished. * Updated the player physics to use proper Velocity to jump off the ground rather than the hacky timer-based fixed speed approach. * FlashError() function to flash "error level" messages to the screen. They appear in orange text instead of the usual blue, and most error messages in the game use this now. The dev console "error <msg>" command can simulate an error message. * Flashed message fonts are updated. The blue font now uses softer stroke and shadow colors and the same algorithm applies to the orange error flashes. Some other changes to player physics: * Max velocity, acceleration speed, and gravity have been tweaked. * Fast turn-around if you are moving right and then need to go left. Your velocity resets to zero at the transition so you quickly get going the way you want to go. Some levels that need a bit of love for the new platforming physics: * Tutorial 3.level
2021-10-08 01:24:18 +00:00
d.FlashError("Use this cheat in Play Mode to disable clipping for the player character.")
The Window Manager Update * Take advantage of the new Window Manager feature of the UI toolkit. * Move the MenuScene's "New Level" and "Play/Edit Level" windows into stand-alone functions in new pkg/windows/ package. The 'windows' package is isolated from the rest of Doodle and communicates using config variables and callback functions to avoid circular dependency. * MenuScene calls the window constructors from the new package. * Add an "Options" button to the Menu Bar in the Editor Scene, which opens the "New Level" window to allow changing the wallpaper or bounding type of the level currently being edited. * Move the cheat codes into their own file, cheats.go
2020-04-07 06:21:17 +00:00
}
Centralize cheats, detect cheated player character * If the player runs the PlayAsBird cheat they shouldn't be able to win a high score on a level, so at level startup it detects whether the DefaultPlayerCharacterDoodad has changed from default on a level that doesn't use the Start Flag to set a specific doodad - and immediately marks the session as cheated
2022-01-09 02:27:37 +00:00
case balance.CheatShowAllActors:
Technical Doodad: Checkpoint Region The Checkpoint Region acts as an invisible checkpoint flag, remembering the player's location should they need to respawn there. New cheat: `show all actors` during Play Mode will make every hidden actor visible. Useful to see your technical doodads during gameplay! Developer shell: `Execute(command string)` is available to the JavaScript interpreter. It simulates another command being run on the developer console.
2021-10-03 04:12:57 +00:00
if isPlay {
Savegame and High Scores * Adds pkg/savegame to store user progress thru Level Packs. * The savegame.json is mildly tamper resistant by including a checksum along with the JSON body. * The checksum combines the JSON string + an app secret (in savegame.go) + user specific entropy (stored in their settings.json). If the user modifies their save file and the checksum becomes invalid the game will not load the save file, acting like it didn't exist, resetting all their high scores. Updates to the Story Mode window: * On the LevelPacks list: shows e.g. "[completed 0 of 3 levels]" showing a user's progress thru the level pack. * Below the levels on the Detail screen: * Shows an indicator whether the level is completed or not. * Shows high scores (fastest times beating the level) * Shows a padlock icon if levels are locked and the player hasn't reached them yet. Pops up an Alert modal if a locked level is clicked on. Scoring is based around your fastest time elapsed to finish the level. * Perfect Time (gold coin): player has not died during the level. * Best Time (silver coin): player has continued from a checkpoint. In-game an elapsed timer is shown in the top left corner along with the gold or silver coin indicating if your run has been Perfect. If the user enters any Cheat Codes during gameplay they are not eligible to win a high score, but the level will still be marked as completed. The icon next to the in-game timer disappears when a cheat code has been entered.
2022-01-03 00:28:43 +00:00
playScene.SetCheated()
Technical Doodad: Checkpoint Region The Checkpoint Region acts as an invisible checkpoint flag, remembering the player's location should they need to respawn there. New cheat: `show all actors` during Play Mode will make every hidden actor visible. Useful to see your technical doodads during gameplay! Developer shell: `Execute(command string)` is available to the JavaScript interpreter. It simulates another command being run on the developer console.
2021-10-03 04:12:57 +00:00
for _, actor := range playScene.drawing.Actors() {
actor.Show()
}
d.Flash("All invisible actors made visible.")
} else {
Async Giant Screenshot, Player Physics and UI Polish * The "Giant Screenshot" feature takes a very long time, so it is made asynchronous. If you try and run a second one while the first is busy, you get an error flash. You can continue editing the level, even playtest it, or load a different level, and it will continue crunching on the Giant Screenshot and flash when it's finished. * Updated the player physics to use proper Velocity to jump off the ground rather than the hacky timer-based fixed speed approach. * FlashError() function to flash "error level" messages to the screen. They appear in orange text instead of the usual blue, and most error messages in the game use this now. The dev console "error <msg>" command can simulate an error message. * Flashed message fonts are updated. The blue font now uses softer stroke and shadow colors and the same algorithm applies to the orange error flashes. Some other changes to player physics: * Max velocity, acceleration speed, and gravity have been tweaked. * Fast turn-around if you are moving right and then need to go left. Your velocity resets to zero at the transition so you quickly get going the way you want to go. Some levels that need a bit of love for the new platforming physics: * Tutorial 3.level
2021-10-08 01:24:18 +00:00
d.FlashError("Use this cheat in Play Mode to show hidden actors, such as technical doodads.")
Technical Doodad: Checkpoint Region The Checkpoint Region acts as an invisible checkpoint flag, remembering the player's location should they need to respawn there. New cheat: `show all actors` during Play Mode will make every hidden actor visible. Useful to see your technical doodads during gameplay! Developer shell: `Execute(command string)` is available to the JavaScript interpreter. It simulates another command being run on the developer console.
2021-10-03 04:12:57 +00:00
}
Centralize cheats, detect cheated player character * If the player runs the PlayAsBird cheat they shouldn't be able to win a high score on a level, so at level startup it detects whether the DefaultPlayerCharacterDoodad has changed from default on a level that doesn't use the Start Flag to set a specific doodad - and immediately marks the session as cheated
2022-01-09 02:27:37 +00:00
case balance.CheatGiveKeys:
The Window Manager Update * Take advantage of the new Window Manager feature of the UI toolkit. * Move the MenuScene's "New Level" and "Play/Edit Level" windows into stand-alone functions in new pkg/windows/ package. The 'windows' package is isolated from the rest of Doodle and communicates using config variables and callback functions to avoid circular dependency. * MenuScene calls the window constructors from the new package. * Add an "Options" button to the Menu Bar in the Editor Scene, which opens the "New Level" window to allow changing the wallpaper or bounding type of the level currently being edited. * Move the cheat codes into their own file, cheats.go
2020-04-07 06:21:17 +00:00
if isPlay {
Savegame and High Scores * Adds pkg/savegame to store user progress thru Level Packs. * The savegame.json is mildly tamper resistant by including a checksum along with the JSON body. * The checksum combines the JSON string + an app secret (in savegame.go) + user specific entropy (stored in their settings.json). If the user modifies their save file and the checksum becomes invalid the game will not load the save file, acting like it didn't exist, resetting all their high scores. Updates to the Story Mode window: * On the LevelPacks list: shows e.g. "[completed 0 of 3 levels]" showing a user's progress thru the level pack. * Below the levels on the Detail screen: * Shows an indicator whether the level is completed or not. * Shows high scores (fastest times beating the level) * Shows a padlock icon if levels are locked and the player hasn't reached them yet. Pops up an Alert modal if a locked level is clicked on. Scoring is based around your fastest time elapsed to finish the level. * Perfect Time (gold coin): player has not died during the level. * Best Time (silver coin): player has continued from a checkpoint. In-game an elapsed timer is shown in the top left corner along with the gold or silver coin indicating if your run has been Perfect. If the user enters any Cheat Codes during gameplay they are not eligible to win a high score, but the level will still be marked as completed. The icon next to the in-game timer disappears when a cheat code has been entered.
2022-01-03 00:28:43 +00:00
playScene.SetCheated()
The Window Manager Update * Take advantage of the new Window Manager feature of the UI toolkit. * Move the MenuScene's "New Level" and "Play/Edit Level" windows into stand-alone functions in new pkg/windows/ package. The 'windows' package is isolated from the rest of Doodle and communicates using config variables and callback functions to avoid circular dependency. * MenuScene calls the window constructors from the new package. * Add an "Options" button to the Menu Bar in the Editor Scene, which opens the "New Level" window to allow changing the wallpaper or bounding type of the level currently being edited. * Move the cheat codes into their own file, cheats.go
2020-04-07 06:21:17 +00:00
playScene.Player.AddItem("key-red.doodad", 0)
playScene.Player.AddItem("key-blue.doodad", 0)
playScene.Player.AddItem("key-green.doodad", 0)
playScene.Player.AddItem("key-yellow.doodad", 0)
Doodads: Small Key Door + Bigger Crumbly Floor * The crumbly floor doodad was made 50% larger. * New doodad: Small Key and Small Key Door. These work like the colored doors and locks except each Small Key is consumed when it unlocks a door. The door's appearance is of iron bars. * The inventory HUD displays a small quantity label in the lower-right corner of items that have a quantity, such as the Small Key. This is done as a Canvas.CornerLabel string attribute on uix.Canvas. * The "give all keys" cheat adds 99 Small Keys to your inventory.
2021-01-04 01:06:33 +00:00
playScene.Player.AddItem("small-key.doodad", 99)
The Window Manager Update * Take advantage of the new Window Manager feature of the UI toolkit. * Move the MenuScene's "New Level" and "Play/Edit Level" windows into stand-alone functions in new pkg/windows/ package. The 'windows' package is isolated from the rest of Doodle and communicates using config variables and callback functions to avoid circular dependency. * MenuScene calls the window constructors from the new package. * Add an "Options" button to the Menu Bar in the Editor Scene, which opens the "New Level" window to allow changing the wallpaper or bounding type of the level currently being edited. * Move the cheat codes into their own file, cheats.go
2020-04-07 06:21:17 +00:00
d.Flash("Given all keys to the player character.")
} else {
Async Giant Screenshot, Player Physics and UI Polish * The "Giant Screenshot" feature takes a very long time, so it is made asynchronous. If you try and run a second one while the first is busy, you get an error flash. You can continue editing the level, even playtest it, or load a different level, and it will continue crunching on the Giant Screenshot and flash when it's finished. * Updated the player physics to use proper Velocity to jump off the ground rather than the hacky timer-based fixed speed approach. * FlashError() function to flash "error level" messages to the screen. They appear in orange text instead of the usual blue, and most error messages in the game use this now. The dev console "error <msg>" command can simulate an error message. * Flashed message fonts are updated. The blue font now uses softer stroke and shadow colors and the same algorithm applies to the orange error flashes. Some other changes to player physics: * Max velocity, acceleration speed, and gravity have been tweaked. * Fast turn-around if you are moving right and then need to go left. Your velocity resets to zero at the transition so you quickly get going the way you want to go. Some levels that need a bit of love for the new platforming physics: * Tutorial 3.level
2021-10-08 01:24:18 +00:00
d.FlashError("Use this cheat in Play Mode to get all colored keys.")
The Window Manager Update * Take advantage of the new Window Manager feature of the UI toolkit. * Move the MenuScene's "New Level" and "Play/Edit Level" windows into stand-alone functions in new pkg/windows/ package. The 'windows' package is isolated from the rest of Doodle and communicates using config variables and callback functions to avoid circular dependency. * MenuScene calls the window constructors from the new package. * Add an "Options" button to the Menu Bar in the Editor Scene, which opens the "New Level" window to allow changing the wallpaper or bounding type of the level currently being edited. * Move the cheat codes into their own file, cheats.go
2020-04-07 06:21:17 +00:00
}
Doodads: Gems, Snake and Crusher Adds several new doodads to the game and 5 new wallpapers (parchment paper in blue, green, red, white and yellow). New doodads: * Crusher: A purple block-headed mob wearing an iron helmet. It tries to crush the player when you get underneath. Its flat helmet can be ridden on like an elevator back up. * Snake: A green stationary mob that always faces toward the player. If the player is nearby and jumps, the Snake will jump too and hope to catch the player in mid-air. * Gems and Totems: A new key & lock collectible. Gems have quantity so you can collect multiple, and place them into matching Totems. A Totem gives off a power signal when its gem is placed and all other Totems it is linked to have also been activated. A single Totem may link to an Electric Door and require only one gem to open it, or it can link to other Totems and they all require gems before the power signal is sent out.
2022-05-01 22:18:23 +00:00
case balance.CheatGiveGems:
if isPlay {
playScene.SetCheated()
playScene.Player.AddItem("gem-red.doodad", 1)
playScene.Player.AddItem("gem-green.doodad", 1)
playScene.Player.AddItem("gem-blue.doodad", 1)
playScene.Player.AddItem("gem-yellow.doodad", 1)
d.Flash("Given all gemstones to the player character.")
} else {
d.FlashError("Use this cheat in Play Mode to get all gemstones.")
}
Centralize cheats, detect cheated player character * If the player runs the PlayAsBird cheat they shouldn't be able to win a high score on a level, so at level startup it detects whether the DefaultPlayerCharacterDoodad has changed from default on a level that doesn't use the Start Flag to set a specific doodad - and immediately marks the session as cheated
2022-01-09 02:27:37 +00:00
case balance.CheatDropItems:
The Window Manager Update * Take advantage of the new Window Manager feature of the UI toolkit. * Move the MenuScene's "New Level" and "Play/Edit Level" windows into stand-alone functions in new pkg/windows/ package. The 'windows' package is isolated from the rest of Doodle and communicates using config variables and callback functions to avoid circular dependency. * MenuScene calls the window constructors from the new package. * Add an "Options" button to the Menu Bar in the Editor Scene, which opens the "New Level" window to allow changing the wallpaper or bounding type of the level currently being edited. * Move the cheat codes into their own file, cheats.go
2020-04-07 06:21:17 +00:00
if isPlay {
Savegame and High Scores * Adds pkg/savegame to store user progress thru Level Packs. * The savegame.json is mildly tamper resistant by including a checksum along with the JSON body. * The checksum combines the JSON string + an app secret (in savegame.go) + user specific entropy (stored in their settings.json). If the user modifies their save file and the checksum becomes invalid the game will not load the save file, acting like it didn't exist, resetting all their high scores. Updates to the Story Mode window: * On the LevelPacks list: shows e.g. "[completed 0 of 3 levels]" showing a user's progress thru the level pack. * Below the levels on the Detail screen: * Shows an indicator whether the level is completed or not. * Shows high scores (fastest times beating the level) * Shows a padlock icon if levels are locked and the player hasn't reached them yet. Pops up an Alert modal if a locked level is clicked on. Scoring is based around your fastest time elapsed to finish the level. * Perfect Time (gold coin): player has not died during the level. * Best Time (silver coin): player has continued from a checkpoint. In-game an elapsed timer is shown in the top left corner along with the gold or silver coin indicating if your run has been Perfect. If the user enters any Cheat Codes during gameplay they are not eligible to win a high score, but the level will still be marked as completed. The icon next to the in-game timer disappears when a cheat code has been entered.
2022-01-03 00:28:43 +00:00
playScene.SetCheated()
The Window Manager Update * Take advantage of the new Window Manager feature of the UI toolkit. * Move the MenuScene's "New Level" and "Play/Edit Level" windows into stand-alone functions in new pkg/windows/ package. The 'windows' package is isolated from the rest of Doodle and communicates using config variables and callback functions to avoid circular dependency. * MenuScene calls the window constructors from the new package. * Add an "Options" button to the Menu Bar in the Editor Scene, which opens the "New Level" window to allow changing the wallpaper or bounding type of the level currently being edited. * Move the cheat codes into their own file, cheats.go
2020-04-07 06:21:17 +00:00
playScene.Player.ClearInventory()
d.Flash("Cleared inventory of player character.")
} else {
Async Giant Screenshot, Player Physics and UI Polish * The "Giant Screenshot" feature takes a very long time, so it is made asynchronous. If you try and run a second one while the first is busy, you get an error flash. You can continue editing the level, even playtest it, or load a different level, and it will continue crunching on the Giant Screenshot and flash when it's finished. * Updated the player physics to use proper Velocity to jump off the ground rather than the hacky timer-based fixed speed approach. * FlashError() function to flash "error level" messages to the screen. They appear in orange text instead of the usual blue, and most error messages in the game use this now. The dev console "error <msg>" command can simulate an error message. * Flashed message fonts are updated. The blue font now uses softer stroke and shadow colors and the same algorithm applies to the orange error flashes. Some other changes to player physics: * Max velocity, acceleration speed, and gravity have been tweaked. * Fast turn-around if you are moving right and then need to go left. Your velocity resets to zero at the transition so you quickly get going the way you want to go. Some levels that need a bit of love for the new platforming physics: * Tutorial 3.level
2021-10-08 01:24:18 +00:00
d.FlashError("Use this cheat in Play Mode to clear your inventory.")
The Window Manager Update * Take advantage of the new Window Manager feature of the UI toolkit. * Move the MenuScene's "New Level" and "Play/Edit Level" windows into stand-alone functions in new pkg/windows/ package. The 'windows' package is isolated from the rest of Doodle and communicates using config variables and callback functions to avoid circular dependency. * MenuScene calls the window constructors from the new package. * Add an "Options" button to the Menu Bar in the Editor Scene, which opens the "New Level" window to allow changing the wallpaper or bounding type of the level currently being edited. * Move the cheat codes into their own file, cheats.go
2020-04-07 06:21:17 +00:00
}
Invincibility Cheat Add cheat `god mode` that toggles invincibility. Fire pixels and hostile mobs can't fail the level for you.
2022-01-18 06:02:27 +00:00
case balance.CheatGodMode:
if isPlay {
d.Flash("God mode toggled")
playScene.SetCheated()
playScene.godMode = !playScene.godMode
if playScene.godMode {
d.FlashError("God mode enabled.")
} else {
d.Flash("God mode disabled.")
}
} else {
d.FlashError("Use this cheat in Play Mode to toggle invincibility.")
}
Add cheat code to send power to all actors
2023-02-18 22:21:07 +00:00
case balance.CheatFreeEnergy:
if isPlay {
playScene.SetCheated()
d.Flash("Power toggle sent to all actors in the level.")
for _, a := range playScene.Canvas().Actors() {
// Hacky stuff here - just a fun cheat code anyway.
vm := playScene.ScriptSupervisor().To(a.ID())
value := vm.Get("__tesla")
if value == nil || !value.ToBoolean() {
vm.Set("__tesla", true)
value = vm.Get("__tesla")
} else if value.ToBoolean() {
vm.Set("__tesla", false)
value = vm.Get("__tesla")
}
vm.Inbound <- scripting.Message{
Name: "power",
SenderID: a.ID(),
Args: []goja.Value{value},
}
}
} else {
d.FlashError("Use this cheat in Play Mode to send power to all actors (chaotic!).")
}
Spit and polish UI improvements specifically for mobile (running the game with the `-w mobile` or `-w landscape` options) screen sizes. * Rework the Settings window to be mobile friendly to landscape oriented screens (`doodle -w landscape`) and migrate Options tab to magicform. * The toolbar in the Editor will be a single column of buttons on small screens, such as `-w mobile` (375x812) portrait mode smartphone. On larger screens the toolbar shows in two columns of buttons. * Fix tooltips not drawing on top. * Centralize the hard-coded references to specific font filenames * Add cheat code: `test load screen` to bring a sample loading screen up for a few seconds. It needs improvement on `-w landscape`
2022-03-06 06:44:54 +00:00
case balance.CheatDebugLoadScreen:
loadscreen.ShowWithProgress()
loadscreen.SetSubtitle("Loading: /dev/null", "Loadscreen testing.")
go func() {
var i float64
for i = 0; i < 100; i++ {
time.Sleep(100 * time.Millisecond)
loadscreen.SetProgress(i / 100)
}
loadscreen.Hide()
}()
Wait Modal * Add modal.Wait() that creates a global progress bar modal which is not dismissable by the user; the caller must Dismiss() the modal themselves when ready. * It will be useful in the future in case e.g. saving a Level needs to take a while to rebalance chunks and the modal prevents ALL interaction with the game so the user can't further modify the level while it's busy refactoring itself. * Cheat code: "test wait screen" to show the Wait modal for 10 seconds.
2022-09-25 01:39:02 +00:00
case balance.CheatDebugWaitScreen:
m := modal.Wait("Crunching some numbers...").WithTitle("Please hold").Then(func() {
d.Flash("Wait modal dismissed.")
})
go func() {
time.Sleep(10 * time.Second)
m.Dismiss(true)
}()
Flood Tool, Survival Mode for Azulian Tag New features: * Flood Tool for the editor. It replaces pixels of one color with another, contiguously. Has limits on how far from the original pixel it will color, to avoid infinite loops in case the user clicked on wide open void. The limit when clicking an existing color is 1200px or only a 600px limit if clicking into the void. * Cheat code: 'master key' to play locked Story Mode levels. Level GameRules feature added: * A new tab in the Level Properties dialog * Difficulty has been moved to this tab * Survival Mode: for silver high score, longest time alive is better than fastest time, for Azulian Tag maps. Gold high score is still based on fastest time - find the hidden level exit without dying! Tweaks to the Azulians' jump heights: * Blue Azulian: 12 -> 14 * Red Azulian: 14 -> 18 * White Azulian: 16 -> 20 Bugs fixed: * When editing your Palette to rename a color or add a new color, it wasn't possible to draw with that color until the editor was completely unloaded and reloaded; this is now fixed. * Minor bugfix in Difficulty.String() for Peaceful (-1) difficulty to avoid a negative array index. * Try and prevent user giving the same name to multiple swatches on their palette. Replacing the whole palette can let duplication through still.
2022-03-26 20:55:06 +00:00
case balance.CheatUnlockLevels:
balance.CheatEnabledUnlockLevels = !balance.CheatEnabledUnlockLevels
if balance.CheatEnabledUnlockLevels {
d.Flash("All locked Story Mode levels can now be played.")
} else {
d.Flash("All locked Story Mode levels are again locked.")
}
Spit and polish * New built-in wallpaper: "Dotted paper (dark)" is a dark-themed wallpaper. * New built-in palette: "Neon Bright" with bright colors for dark levels. * New cheat: "warp whistle" to automatically win the level. * In case the user has a VERY LARGE screen resolution bigger than the full bounds of a Bounded level, the Play Scene will cap the size and center the level canvas onto the window. This is preferable to being able to see beyond the level's boundaries and hitting an invisible wall in-game. * Make the titlescreen Lazy Scroll work on unbounded levels. It can't bounce off scroll boundaries but it will reverse course if it reaches the level's furthest limits. * Bugfix: characters' white eyes were transparent in-game. Multiple culprits from the `doodad convert` tool defaulting the chroma key to white, to the SDL2 textures considering white to be transparent. For the latter, the game offsets the color by -1 blue.
2022-05-04 04:15:39 +00:00
case balance.CheatSkipLevel:
if isPlay {
playScene.SetCheated()
playScene.ShowEndLevelModal(
true,
"Level Completed",
"Great job, you cheated and 'won' the level!",
)
} else {
d.Flash("Use this cheat in Play Mode to instantly win the level.")
}
The Window Manager Update * Take advantage of the new Window Manager feature of the UI toolkit. * Move the MenuScene's "New Level" and "Play/Edit Level" windows into stand-alone functions in new pkg/windows/ package. The 'windows' package is isolated from the rest of Doodle and communicates using config variables and callback functions to avoid circular dependency. * MenuScene calls the window constructors from the new package. * Add an "Options" button to the Menu Bar in the Editor Scene, which opens the "New Level" window to allow changing the wallpaper or bounding type of the level currently being edited. * Move the cheat codes into their own file, cheats.go
2020-04-07 06:21:17 +00:00
default:
New Doodad: Blue Bird * The blue bird follows the same base AI as the red bird (it has a target altitude that it tries to maintain, and it will dive at the player) but the blue bird flies in a sine wave pattern around its target altitude. It also has a longer scan radius to search for the player than the red bird. * The sine wave pattern of the blue bird means you may fly under its radar depending how high it is on average. Cheat codes that replace the player character are refactored to make it easier to extend, and new cheats have been added: * super azulian: play as the Red Azulian. * hyper azulian: play as the White Azulian. * bluebird: play as the new Bird (blue).
2022-05-01 00:59:55 +00:00
// See if it was an endorsed actor cheat.
if filename, ok := balance.CheatActors[strings.ToLower(c.Raw)]; ok {
d.Flash("Set default player character to %s.", filename)
balance.PlayerCharacterDoodad = filename
setPlayerCharacter = true
} else {
// Not a cheat code.
return false
}
The Window Manager Update * Take advantage of the new Window Manager feature of the UI toolkit. * Move the MenuScene's "New Level" and "Play/Edit Level" windows into stand-alone functions in new pkg/windows/ package. The 'windows' package is isolated from the rest of Doodle and communicates using config variables and callback functions to avoid circular dependency. * MenuScene calls the window constructors from the new package. * Add an "Options" button to the Menu Bar in the Editor Scene, which opens the "New Level" window to allow changing the wallpaper or bounding type of the level currently being edited. * Move the cheat codes into their own file, cheats.go
2020-04-07 06:21:17 +00:00
}
Optimize memory by freeing up SDL2 textures * Added to the F3 Debug Overlay is a "Texture:" label that counts the number of textures currently loaded by the (SDL2) render engine. * Added Teardown() functions to Level, Doodad and the Chunker they both use to free up SDL2 textures for all their cached graphics. * The Canvas.Destroy() function now cleans up all textures that the Canvas is responsible for: calling the Teardown() of the Level or Doodad, calling Destroy() on all level actors, and cleaning up Wallpaper textures. * The Destroy() method of the game's various Scenes will properly Destroy() their canvases to clean up when transitioning to another scene. The MainScene, MenuScene, EditorScene and PlayScene. * Fix the sprites package to actually cache the ui.Image widgets. The game has very few sprites so no need to free them just yet. Some tricky places that were leaking textures have been cleaned up: * Canvas.InstallActors() destroys the canvases of existing actors before it reinitializes the list and installs the replacements. * The DraggableActor when the user is dragging an actor around their level cleans up the blueprint masked drag/drop actor before nulling it out. Misc changes: * The player character cheats during Play Mode will immediately swap out the player character on the current level. * Properly call the Close() function instead of Hide() to dismiss popup windows. The Close() function itself calls Hide() but also triggers WindowClose event handlers. The Doodad Dropper subscribes to its close event to free textures for all its doodad canvases.
2022-04-09 21:41:24 +00:00
// If we're setting the player character and in Play Mode, do it.
if setPlayerCharacter && isPlay {
Spit and polish * New built-in wallpaper: "Dotted paper (dark)" is a dark-themed wallpaper. * New built-in palette: "Neon Bright" with bright colors for dark levels. * New cheat: "warp whistle" to automatically win the level. * In case the user has a VERY LARGE screen resolution bigger than the full bounds of a Bounded level, the Play Scene will cap the size and center the level canvas onto the window. This is preferable to being able to see beyond the level's boundaries and hitting an invisible wall in-game. * Make the titlescreen Lazy Scroll work on unbounded levels. It can't bounce off scroll boundaries but it will reverse course if it reaches the level's furthest limits. * Bugfix: characters' white eyes were transparent in-game. Multiple culprits from the `doodad convert` tool defaulting the chroma key to white, to the SDL2 textures considering white to be transparent. For the latter, the game offsets the color by -1 blue.
2022-05-04 04:15:39 +00:00
playScene.SetCheated()
Optimize memory by freeing up SDL2 textures * Added to the F3 Debug Overlay is a "Texture:" label that counts the number of textures currently loaded by the (SDL2) render engine. * Added Teardown() functions to Level, Doodad and the Chunker they both use to free up SDL2 textures for all their cached graphics. * The Canvas.Destroy() function now cleans up all textures that the Canvas is responsible for: calling the Teardown() of the Level or Doodad, calling Destroy() on all level actors, and cleaning up Wallpaper textures. * The Destroy() method of the game's various Scenes will properly Destroy() their canvases to clean up when transitioning to another scene. The MainScene, MenuScene, EditorScene and PlayScene. * Fix the sprites package to actually cache the ui.Image widgets. The game has very few sprites so no need to free them just yet. Some tricky places that were leaking textures have been cleaned up: * Canvas.InstallActors() destroys the canvases of existing actors before it reinitializes the list and installs the replacements. * The DraggableActor when the user is dragging an actor around their level cleans up the blueprint masked drag/drop actor before nulling it out. Misc changes: * The player character cheats during Play Mode will immediately swap out the player character on the current level. * Properly call the Close() function instead of Hide() to dismiss popup windows. The Close() function itself calls Hide() but also triggers WindowClose event handlers. The Doodad Dropper subscribes to its close event to free textures for all its doodad canvases.
2022-04-09 21:41:24 +00:00
playScene.SetPlayerCharacter(balance.PlayerCharacterDoodad)
}
The Window Manager Update * Take advantage of the new Window Manager feature of the UI toolkit. * Move the MenuScene's "New Level" and "Play/Edit Level" windows into stand-alone functions in new pkg/windows/ package. The 'windows' package is isolated from the rest of Doodle and communicates using config variables and callback functions to avoid circular dependency. * MenuScene calls the window constructors from the new package. * Add an "Options" button to the Menu Bar in the Editor Scene, which opens the "New Level" window to allow changing the wallpaper or bounding type of the level currently being edited. * Move the cheat codes into their own file, cheats.go
2020-04-07 06:21:17 +00:00
return true
}
Reference in New Issue Copy Permalink