Version 2023.12.31

github is a piece of shit and deleted the original description just because i went to a new tab by accident so i had to write it again. :'3

• Segstrate has been removed
• Removed some menu items that were redundant
• Actions have rewritten tooltips with better formatting
• The preferences menu is now tabbed
• New UI mode that removes shatter specific features
• Fixed a bug where segment strech would corrupt segment Z length property
• Rename "Lighting" -> "Advanced lighting"

Version 2023.12.27

• Add the ability to export current quick test config to a room lua file
  • I am hoping this will help to ease people into making room lua's since that can be hard
  • However this won't export confSegment()'s but I plan to do it, works best if you have multipule scenes in one file :3
• Add missing particle effect names to list
  • This should have been done a long time ago...
• Remove segstrate from the UI, should be fully removed by the new year
  • Segstrate is going away, all code will be removed by the next release (probably at the start of the new year)
  • The reason Segstrate is being killed is that while I originally made is as a solution to help against segment stealing the people who complained about it didn't accept this as a solution and kept complaining. Also, really it seems like no one uses it anyway and finally it's not even good protection. So, goodbye segstrate.

Version 2023.12.21

• Premium patching for 1.5.5 on ARM64
• Remove restrictions on room length in Quick Test
• Fixed a bug with auto length and using multiple scenes
• Code cleanup

Version 2023.12.14

Not a big release today

• Fix "uniform" and "per-axis" being swapped in UI
• Add soft limits to gradient colours (make the slider work properly) and change most colours to use soft limits (so you can now do colours with -1, 2 etc)
• Change Shatter discord to SHL discord

Version 2023.12.6

• Add ARM32 patches for removing antitamper, enabling premium, enabling lua io/os.clock/package and disabling save encryption.

Version 2023.12.1

This release is mostly some tweaks to support Smash Hit 1.5.2 from 28 Nov 2023. While 1.5.x has not officially relesed nor is it rolling out to any devices, it's helpful for modders to understand upcoming changes to SH.

• You can now disable segment XML compression when using auto export (1.5.2 does not compress segments)
• Premium and save encryption patch support was added for 1.5.2 on ARM64.
  • It should be noted that antitamper isn't needed because 1.5.2 does not have antitamper protection.
  • Additionally, the Lua corelib patch is not need because Lua isn't sandboxed in 1.5.2.

Again, remember that 1.5.2 is very buggy and was not meant for use, so you should only use to learn about the changes coming to Smash Hit in newer updates.

test release

testing the shl webhook

Version 2023.11.22

• We have a new Privacy Notice.
• This release removes the bad user ID checking as well as the user ID system altogether.

There are many reasons that I have removed user IDs, some of which happened today and some of which I've been thinking about since I created the feature.

The first is that it's just user hostile to track everyone because a few people have been stealing segments, or to track what people are doing in general in some hopes that it will solve your problem. I think I've realised that it never really does solve anything. People would still steal segments even if I/the community voted to ban them from using Shatter.

The second was that I recently read the very well-said complaints about modern Teardown by 1ssnl. It's not really relevant to this feature specifically, but in general it made me think about Shatter's position in this "drama." Do we really want Smash Hit to be just as bad as the now sold-out Teardown? I don't really think so and I felt this feature pulled us to something bad.

Additionally, people were starting to notice that this feature actually existed, and I think it only truly works if people don't know much about it. That's hard to do for an open source project! And since it's open source, anyone can just remove the checks or even see that there's a developer option to disable them. At this point, we only end up wasting some bandwith and time of actual users.

Finally, I've just wanted to switch to a only-defensive approach to segment protection in general. I don't like to punish people, and that's what this feature was essentially doing, and it was also doing it quite badly. I feel being only defensive and using (for its issues and weaknesses) "DRM" is more fair if we want to discourage segment stealing.

If you want to protect your segments from people just copying and pasting into a mod, then you really should use Segstrate and check the "Always disallow import" in Shatter settings. And in general, I would encourage you not to get too passionate about people stealing segments because it will always happen. I understand it can be demotivating but also try to remember that immitation is the best form of flattery.

Anyways, as usual, don't let mobile games die just because they're 10 years old. ❤️

Version 2023.11.18

• New patch tool that is built in to Shatter
• New progression.xml encryption and decryption tool

Version 2023.11.16

• Boxes can now have linear gradients instead of just solid colours
• Initial work on import mode to ignore small boxes