Please help us help you and fill where relevant:
Your LimeSurvey version: 5.3.25
Own server or LimeSurvey hosting: LimeSurvey Hosting
Survey theme/template: Fruity
==================
Good afternoon, 

I am trying to fix a certain number of answer options in a multiple choice question while doing randomization. Particularly I would like to fix answer options D, E & Other. I could manage to fix the Other option by implementing another code. However, I followed this manual  Workarounds: Manipulating a survey at runtime using Javascript - LimeSurvey Manual , implementing the randomization for multiple choice / radio list in the 3X version without success. The questions get randomized as I activated the randomization but none of the questions are fixed. 

Is there any update on that matter? 

Many thanks in advance.  

1. You didn't follow the instructions

LimeSurvey version 3.x:

1. Set up your survey to use JavaScript
2. Create a Multiple Options or List (radio) question with sequential response codes.

Sequential response codes means "1,2,3,4,..."

2. You should set "otherFixed" to TRUE

    // Set this to "true" if you want "Other" to be fixed in the last position
        var otherFixed = true;

  


Then everything is fine - without your first small script to move the "Other"

Joffm
 

Many thanks Joffm. It worked now. I was not aware of the sequential meaning.

However, is there any way to fix a given X number of questions at the bottom? Well, the ones I have currently at the bottom, without adjusting the question code? Or else I will change the conditions so no worries!

Nevermind, I will stick to that solution:)

without adjusting the question code?

Sorry, which question code do you adjust.

I hope, not the 
var qID = {QID};

{QID} is a placeholder that always keeps the actrual question ID
 

Hey Joffm,

I am referring to the answer options's codes (1,2,3...) Before I had non-sequential codes (001, 002). I have to replace them to make the code work.

I have not touched the var qID = {QID}; Thanks for the clarification though!