I don't know why this is voted as Best Practice. If you just call Array.Sort and return the element at index pos-1, benchmarking shows it will run over 10 times faster, without any allocations or garbage generation, and will be just as readable.

I like how you incremented 'rot' when iterating the rotors instead of additionally iterating the remaining characters for every rotor like I did.

Only thing I don't like about it is that you concatenate the result strings in every rotor iteration. Would have been more performant to allocate char arrays and replace the elements then create a string from it when it's finished.

Seems like people are so obsessed with making a one-line solution that they have no regard for sensibility or performance.

I couldn't tell if you were being sarcastic at first