Code: Select all
Champion:setHealth(0)Code: Select all
champion:setStat("health", 0)Well, all I did was use the command he gave me. Again, if I knew all the proper syntax, I wouldn't have to ask questions.Zo Kath Ra wrote: ↑Wed May 26, 2021 7:55 pmonly exists in LoG2.Code: Select all
Champion:setHealth(0)
In LoG1, it'sCode: Select all
champion:setStat("health", 0)
For a while, I thought about doing that for LoG2.
So it is equally understandable why scripters would look at some of these commands and not have a clue what to do with them or, don't know what their full capabilities are. Essentially what we have now is an appendix of commands. Hardly sufficient enough to actually learn how to code LoG.Zo Kath Ra wrote: ↑Wed May 26, 2021 8:11 pmFor a while, I thought about doing that for LoG2.
I even had a cool name for it... "Grimoire Two"
But it's an incredible amount of work, so I understand why the developers didn't do it.
I disagree, the Champion: functions in the LoG1 documentation have both the function prototypes and a short explanation, usually a few sentences.wagtunes wrote: ↑Wed May 26, 2021 8:17 pm So it is equally understandable why scripters would look at some of these commands and not have a clue what to do with them or, don't know what their full capabilities are. Essentially what we have now is an appendix of commands. Hardly sufficient enough to actually learn how to code LoG.
I don't see how that isn't enough information.Champion:damage(amount, type)
Deals damage to the champion. Type must be “physical”, “fire”, “shock”, “poison” or “cold”.
For that, yes. Should I now go list 100 commands that have no explanation at all? It's easy enough to do.Zo Kath Ra wrote: ↑Wed May 26, 2021 8:22 pmI disagree, the Champion: functions in the LoG1 documentation have both the function prototypes and a short explanation, usually a few sentences.wagtunes wrote: ↑Wed May 26, 2021 8:17 pm So it is equally understandable why scripters would look at some of these commands and not have a clue what to do with them or, don't know what their full capabilities are. Essentially what we have now is an appendix of commands. Hardly sufficient enough to actually learn how to code LoG.
For example:I don't see how that isn't enough information.Champion:damage(amount, type)
Deals damage to the champion. Type must be “physical”, “fire”, “shock”, “poison” or “cold”.
Code: Select all
CastSpellComponent:deplete()
CastSpellComponent:getCharges()
CastSpellComponent:getEmptyGfxIndex()
CastSpellComponent:getEmptyItem()
CastSpellComponent:getFullGfxIndex()
CastSpellComponent:getMaxCharges()
CastSpellComponent:getPower()
CastSpellComponent:getRequiredLevel()
CastSpellComponent:getSkill()
CastSpellComponent:getSpell()
CastSpellComponent:recharge()
CastSpellComponent:setCharges(number)
CastSpellComponent:setEmptyGfxIndex(number)
CastSpellComponent:setEmptyItem(string)
CastSpellComponent:setFullGfxIndex(number)
CastSpellComponent:setMaxCharges(number)
CastSpellComponent:setPower(number)
CastSpellComponent:setRequiredLevel(number)
CastSpellComponent:setSkill(string)
CastSpellComponent:setSpell(string)Code: Select all
Champion:addSkillPoints(amount)
Champion:addStatModifier(name, amount)
Champion:addTrait(name)
Champion:attack(number, boolean)
Champion:castSpell(number)
Champion:consumeFood(amount)
Champion:damage(dmg, damageType)
Champion:gainExp(xp)
Champion:getArmorSetPiecesEquipped(name)
Champion:getBaseStat(name)
Champion:getClass()
Champion:getConditionValue(name)
Champion:getCurrentStat(name)
Champion:getDualClass()
Champion:getEnabled()
Champion:getEnergy()
Champion:getEvasion()
Champion:getExp()
Champion:getFood()
Champion:getHealth()
Champion:getItem(slot)
Champion:getLevel()
Champion:getLoad()
Champion:getMaxEnergy()
Champion:getMaxHealth()
Champion:getMaxLoad()
Champion:getName()
Champion:getOrdinal()
Champion:getOtherHandItem(slot)
Champion:getProtection()
Champion:getRace()
Champion:getResistance(element)
Champion:getSex()
Champion:getSkillLevel(name)
Champion:getSkillPoints()
Champion:hasCondition(name)
Champion:hasTrait(name)
Champion:insertItem(slot, item)
Champion:isAlive()
Champion:isArmorSetEquipped(name)
Champion:isBodyPartWounded(slot)
Champion:isDualWielding()
Champion:isReadyToAttack(number)
Champion:levelUp()
Champion:modifyBaseStat(name, value)
Champion:modifyFood(amount)
Champion:playDamageSound()
Champion:playHealingIndicator()
Champion:playSound(name)
Champion:regainEnergy(amount)
Champion:regainHealth(amount)
Champion:removeCondition(name)
Champion:removeItem(item)
Champion:removeItemFromSlot(slot)
Champion:removeTrait(name)
Champion:setBaseStat(name, value)
Champion:setClass(class)
Champion:setCondition(name)
Champion:setConditionValue(name, value)
Champion:setEnabled(enabled)
Champion:setEnergy(energy)
Champion:setFood(food)
Champion:setHealth(health)
Champion:setName(name)
Champion:setPortrait(filename)
Champion:setRace(race)
Champion:setSex(sex)
Champion:setSkillPoints(points)
Champion:showAttackResult(any, string)
Champion:swapItems(slot1, slot2)
Champion:swapWeaponSets()
Champion:trainSkill(name, times)
Champion:upgradeBaseStat(name, value)Also, for that command above, how about an example of a practical application so we can see it in use and maybe get a better understanding of how to use it?wagtunes wrote: ↑Wed May 26, 2021 8:53 pmFor that, yes. Should I now go list 100 commands that have no explanation at all? It's easy enough to do.Zo Kath Ra wrote: ↑Wed May 26, 2021 8:22 pmI disagree, the Champion: functions in the LoG1 documentation have both the function prototypes and a short explanation, usually a few sentences.wagtunes wrote: ↑Wed May 26, 2021 8:17 pm So it is equally understandable why scripters would look at some of these commands and not have a clue what to do with them or, don't know what their full capabilities are. Essentially what we have now is an appendix of commands. Hardly sufficient enough to actually learn how to code LoG.
For example:I don't see how that isn't enough information.Champion:damage(amount, type)
Deals damage to the champion. Type must be “physical”, “fire”, “shock”, “poison” or “cold”.