Can something be done about decorations that players can walk on so that looting is easier? Maybe a toggle in settings to hide decorations that players can step on in the looting window.

When I am using storms I'll try to make sure everything dies where there are no decorations. This isn't something that players can ignore as when they loot they have to move away from object first to be able to loot the corpse.

I know that players use the same window to examine decorations to see exactly what they are so it might be bad to have them removed completely but it makes looting worse, so that's why I think a setting could be a good solution.
Worth noting that a lot of decorations are self-explanatory like branch that don't need to be shown at all.

Please let me know of any other changes which should be made prior to the protocol update.

When jumping to 0.11.x perhaps it's interesting to build in a kind of multi-command like you said in past? Thinking of my waypoint logic, I still miss a good way to use sentience for non npc's. Would be cool, if we can extend sentience to non npc's. We could build dialogs not only for the waypoint idea, also looking on a bank sign, starting a script showing riches players using sentience mechanics, or showing rankings players reached level 110. I have thought about this some time. Perhaps a kind of multicommand sending command and extensionally text?

Like:
first apply on an item can start a script and also sentience (what is currently working fine), with our apply event but without extra message transfer.
Using this multicommand, client can send apply with extensionally msg, so script can interact with players like we can talk with npc's.
For my waypoints I mainly hacked the say event and used the magic ear to react at least on first sentience interaction, but this is ugly. That's reason I stopped there.
So it's mainly thinking first, how we could implemented such a kind of multicommand. Apply cmd always need the object count and server reaction on sentience need an alternate command to talk to do this. Perhaps we "only" go in apply logics for this.
like
mcmd "apply waypoint", "iluma"
mcmd "apply sign", "richest players"
dunno if we need multicommands to combine 2 commands, i think its mainly, we miss to send additionally informations behind our commands.

Whole help system could be wrapped in one script.

Additionally a command like "get all" could also be wrapped this way, like
mcmd "?M_GET" "all"
for example, for sure this syntax is only example, could be also something like
|?M_GET|all
could also lead to "apply all" for a kind of wardrobe logic to switch gear or full gear switches from containers with one command
going to drop all could also be possible, but could lead to dangerous situations.

So this is only to show, where we can go, when we design a good multi/extended command, mainly wrapping the command in a pack with an extensional string behind?