Question - Good or bad practice?

[Soandso2]

Perhaps this is trivial, but I like to do things the right way, and will refrain from doing something "that works" but is considered to be bad practice.

Having to write mq.TLO.somethingorother makes my fingers bleed. I noticed that doing

local me = mq.TLO.Me works just fine (or at least it does in my very limited test)

However, is this considered bad? ( I cannot see how or why it would be, but I would like to know what the general consensus is anyway.)

 

[Sic]

Nope that is perfectly fine

 

[Amarth]

anything that makes QoL easier on you to repeat, is not bad practice; in fact, I believe Me.Class would expand on the Lua variable setting...? correct me if I'm wrong.

 

[Shadow]

Perhaps this is trivial, but I like to do things the right way, and will refrain from doing something "that works" but is considered to be bad practice.

Having to write mq.TLO.somethingorother makes my fingers bleed. I noticed that doing

local me = mq.TLO.Me works just fine (or at least it does in my very limited test)

However, is this considered bad? ( I cannot see how or why it would be, but I would like to know what the general consensus is anyway.)

Yep, IMHO always better to shorten and clean up the code. It just looks better, organized, and can follow the code better. You can always create a commonly used include too. So if you are writing multiple scripts, have common stuff in an include file and call the include.

local my_class = mq.TLO.Me.Class.ShortName()
if my_class == 'PAL' then