Lua 'and' function?

Hi

There is something wrong with this:

function self_command(command)
	if command == 'toggle TP set' then
		if sets.aftercast.TP == sets.engaged.TPnormal then
			sets.aftercast.TP = sets.engaged.TPacc and sets.aftercast.Ranged = sets.midcast.ranged.TPacc
			send_command('@input /echo ACC SET')
		elseif sets.aftercast.TP == sets.engaged.TPacc then
			sets.aftercast.TP = sets.engaged.TPnormal and sets.aftercast.Ranged = sets.midcast.ranged.TPnormal
			send_command('@input /echo NORMAL SET')
		end
	end
end

sets.aftercast.TP = sets.engaged.TPacc and sets.aftercast.Ranged = sets.midcast.ranged.TPacc

ignore the numbering of the lines too, didnt do what i expected lol

function self_command(command)
    if command == 'toggle TP set' then
        if sets.aftercast.TP == sets.engaged.TPnormal then
            sets.aftercast.TP = sets.engaged.TPacc
            sets.aftercast.Ranged = sets.midcast.ranged.TPacc
            send_command('@input /echo ACC SET')
        elseif sets.aftercast.TP == sets.engaged.TPacc then
            sets.aftercast.TP = sets.engaged.TPnormal
            sets.aftercast.Ranged = sets.midcast.ranged.TPnormal
            send_command('@input /echo NORMAL SET')
        end
    end
end
 

set_type = {'Normal','Acc'}
set_number = 1
sets.aftercast.TP = {}--leve blank
sets.aftercast.TP.normal = {}--put your tp normal set here
sets.aftercast.TP.acc = {}--put your tp acc set here
sets.aftercast.Ranged = {}--leve blank
sets.aftercast.Ranged.Normal = {}--put your Ranged normal set here
sets.aftercast.Ranged.Acc = {}--put your Ranged acc set here

function self_command(command)
    if command == 'toggle TP set' then
        set_number = (set_number % #set_type)+1
        send_command('@input /echo '..set_type[set_number]..' SET')
    end
end

to equip the sets use
equip(sets.aftercast.TP[set_type[set_number]])
equip(sets.aftercast.Ranged[set_type[set_number]])
 

The "and" statement does not work that way. It does not link successive statements together, but it just returns the logical combination of having two non-false values. It is only used in boolean logic (like in an if-statement), and sometimes as a ternary conditional, although that is more advanced and will not usually concern you.

You can adjust sdahlka's suggestion to include sets.aftercast.TP.current and always set the value inside the self_command function. That way you don't have to write equip(sets.aftercast.TP[set_type[set_number]]) but can instead just do equip(sets.aftercast.TP.current). But imo your solution is not bad to have the values elsewhere and not in the same namespace (sets.aftercast.TP for example), that makes most sense when assembling your rules and does not require you to think about the set_type and set_number everywhere you use it.

Cool, thank you both.  I'm trying not to have too much thought in it, so it's easily adaptable and usable even by a novice.  Much appreciated for your inputs.  I figured since 'or' was usable I could get away with 'and', haha.  Thanks!

"or" isn't usable in this context either They're both only for boolean expressions (or ternary conditionals).

arcon i think he was thinking of something like this

Usestaff = (Usestaff=='Atk' and 'Acc' or 'Atk')

but what this is Usestaff = (Usestaff=='Atk' and 'Acc' or 'Atk') is short hand for this
 

if Usestaff == 'Atk' then
    Usestaff = 'Acc'
elseif Usestaff ~= 'Atk' then
    Usestaff = 'Atk'
end

or even this
Changestaff = not Changestaff

which tells Changestaff to not be Changestaff

i.e.
 

if Changestaff ~= false then
    Changestaff = false
elseif Changestaff ~= true then
    Changestaff = true
end

then there is this one that a little more complicated

stopskill_count = (stopskill_count % #stopskilltyp) + 1

this one tells lua to get the remainder between stopskill_count and #stopskilltyp the +1

the complicated part is that #stopskilltyp counts how many thing are in the table stopskilltyp(thats what # does)

This one is bugging me at the moment... its not cycling through

function self_command(command)
	if command == 'toggle TP set' then
		if sets.aftercast.TP == sets.engaged.TPnormal then
			sets.aftercast.TP = sets.engaged.TPacc
			send_command('@input /echo ACC SET')
		elseif sets.aftercast.TP == sets.engaged.TPacc then
			sets.aftercast.TP = sets.engaged.TPtreasure
			send_command('@input /echo TREASURE SET')
		elseif sets.aftercast.tp == sets.engaged.TPtreasure then
			sets.aftercast.TP = sets.engaged.TPnormal
			send_command('@input /echo NORMAL SET')
		end
	end
end

it goes from normal to acc to treasure, but its not cycling back to normal  ><

I am wondering, and havent tried yet, if my others cycle back to the beginning.  i thought they did, which is why this one is baffling me

This one is bugging me at the moment... its not cycling through

 

function self_command(command)
	if command == 'toggle TP set' then
		if sets.aftercast.TP == sets.engaged.TPnormal then
			sets.aftercast.TP = sets.engaged.TPacc
			send_command('@input /echo ACC SET')
		elseif sets.aftercast.TP == sets.engaged.TPacc then
			sets.aftercast.TP = sets.engaged.TPtreasure
			send_command('@input /echo TREASURE SET')
		elseif sets.aftercast.tp == sets.engaged.TPtreasure then
			sets.aftercast.TP = sets.engaged.TPnormal
			send_command('@input /echo NORMAL SET')
		end
	end
end

it goes from normal to acc to treasure, but its not cycling back to normal  ><

 

I am wondering, and havent tried yet, if my others cycle back to the beginning.  i thought they did, which is why this one is baffling me

in one of my previous posts i already gave you the best option for this

The problem is the second elseif. There you have sets.aftercast.tp instead of sets.aftercast.TP. It's just a typo.

in one of my previous posts i already gave you the best option for this

That's debatable.