*What's all this? If you want the shoes to follow the player at all times, just use P_TeleportMove to teleport them to the player's exact location every tic instead of messing around with P_InstaThrust.
*I'm not sure what this is here for, but you probably don't need it.
*player.mo.hat isn't defined in your code. Instead, you should be using player.mo.shoe, which refers to the shoe object.
I'm pretty sure what that is there for, and he definitely needs it. Unless he, like, wants the shoe to always be in the standing frame, regardless of the player's actual frame.
As far as I've heard, that doesn't work in OpenGL. You may want to add that. If I'm correct, Shields use the A_CapeChase action to stay slightly in front of the player relative to camera angle in OpenGL.
...Oh. Damn, I forgot firstly if it's the frame, the sprite, or the object that is invisible during such circumstances, and as a result also secondly how to check for it as well as thirdly apply it on something else.
...You don't have to reset something to a variable. You can reset it to a constant, like SKINCOLOR_RED or something.
Hm. Well, it did work in 2.1.8, at least.
I think I know exactly how to make the secondcolor console command work (you're better off using a console command and setting player.secondcolor with it than using a console variable, especially when it comes to netplay, I think), I just can't format it in English nor Lua (at least not without probably days of testing). Just remember, the SKINCOLOR_RED string (stuff with quotes around) is not the same as the SKINCOLOR_RED constant (stuff without quotes around), and console stuff returns either strings or numbers, I believe.
An object's frame property is not the same as its state. As I said, I don't know what frame is, but it's pointless to use it. If Nomekop wants the shoe object to change its appearance based on the player's state while leaving the rest of the player's sprite visible beneath it, he'll have to create a separate set of sprites and states for all of Sonic's animations, but with everything except the shoes being transparent, and then change player.mo.shoe.state based on the value of player.mo.state. (That is, unless there's some Lua function that magically does all of that automatically, and I somehow haven't encountered it until now.)
That's true, but an object's frame property is its current frame. When an object changes state, the frame of the object gets changed to whatever is in the state definition. Setting the frame to the same as the player object is far far far more convenient and easier than setting if!player.shoe.state==(player.mo.state+S_PLAY_STND-S_SHOE_STND) player.shoe.state=player.mo.state+(S_PLAY_STND-S_SHOE_STND) end or something, while also defining each and every state of the vanilla player, but with the shoe sprite. Also, doing it that way will probably break the hook if used on (not-necessarily-)custom characters with custom states. Changing the frame property simply changes the rendered frame of the object.
I've never heard the term "subsprite" before, though.
