10th March 2022, 12:05 AM
I feel like block skins are pretty limiting, since then you don't get the side level control that a lot of levels could really use (traps levels). You could maybe add both, and then have an indicator for when a level uses custom blocks with player-made functionality so that players have a heads up or whatever. That way, you allow a lot of innovative new ways to make a basic deathmatch with a gimmick that barely affects gameplay.
Lua (or just some sort of block scripting really) should absolutely be added if you do add some form of custom blocks, for reasons mentioned in the previous post and also it's better for level makers when they don't have to spend 8 hours making a weird mechanism to do something that can be done with 20 lines of code instead.
(Also, ideally you'd use LuaJIT rather than the interpreter, for the extra performance that 0.2% of projects will actually take advantage of. If you do go that route tho, remove player usage of FFI, since letting people run arbitrary C code on other people's computers isn't really a great idea I think.)
Lua (or just some sort of block scripting really) should absolutely be added if you do add some form of custom blocks, for reasons mentioned in the previous post and also it's better for level makers when they don't have to spend 8 hours making a weird mechanism to do something that can be done with 20 lines of code instead.
(Also, ideally you'd use LuaJIT rather than the interpreter, for the extra performance that 0.2% of projects will actually take advantage of. If you do go that route tho, remove player usage of FFI, since letting people run arbitrary C code on other people's computers isn't really a great idea I think.)
i failed the mario twitter challenge
