EDITOR Feature Requests (not bugs!)
Re: EDITOR Feature Requests (not bugs!)
That's something similar to what I asked in another post. Excellent idea.
"Hey look! A dungeons and Dragons ride...!"
Re: EDITOR Feature Requests (not bugs!)
I would like the option for repelProjectiles to be applicable to alcoves optionally for alcoves that take up part of the floor.
This way, objects thrown at the alcove don't become hidden by the alcove model.
This way, objects thrown at the alcove don't become hidden by the alcove model.
"I'm okay with being referred to as a goddess."
Community Model Request Thread
See what I'm working on right now: Neikun's Workshop
Lead Coordinator for Legends of the Northern Realms Project
Community Model Request Thread
See what I'm working on right now: Neikun's Workshop
Lead Coordinator for Legends of the Northern Realms Project
- Message me to join in!
Re: EDITOR Feature Requests (not bugs!)
alias(original_name, new_name)
Change the displayed name of a stat or a skill.
Change the displayed name of a stat or a skill.
Re: EDITOR Feature Requests (not bugs!)
Probably already asked dozen of times...
setMonsterStat (index, value)
getMonsterStat(index)
Allow to get/set any useful monster property. (provide an indexed list of interesting properties)
setMonsterStat (index, value)
getMonsterStat(index)
Allow to get/set any useful monster property. (provide an indexed list of interesting properties)
Re: EDITOR Feature Requests (not bugs!)
Hmmm...Zyx wrote:Probably already asked dozen of times...
setMonsterStat (index, value)
getMonsterStat(index)
Allow to get/set any useful monster property. (provide an indexed list of interesting properties)
>> setMonsterStat ("perturbed", true)
>> setMonsterStat ("merchant", true)
>> setMonsterStat ("blinded", true)
>> setMonsterStat ("party_ally", true)
This could have a lot of potential if there was support for altering the default AI actions; (like setting destination tiles and attack target IDs ~even giveItem()/takeItem() methods).
>> green_Ogre:setMonsterStat ("party_ally", true)
>> green_Ogre:giveItem("magic_anvil_of_Crom")
>> follow = {party.level, party.x, party.y}
>> green_Ogre:setMonsterStat ("destination", follow)
Re: EDITOR Feature Requests (not bugs!)
Good ideas. Being able to set the target destination of a monster would increase the customization of their AI tenfold.
- cromcrom
- Posts: 549
- Joined: Tue Sep 11, 2012 7:16 am
- Location: Chateauroux in a socialist s#!$*&% formerly known as "France"
Re: EDITOR Feature Requests (not bugs!)
hello, any words about any possible patch bringing some features listed here ?
A trip of a thousand leagues starts with a step.
Re: EDITOR Feature Requests (not bugs!)
I would *really* like to make a new patch but unfortunately I'm still too busy with the mac version and another secret project I can't talk about yet
BUT i'm feeling a bit bored right now so how about if I go get a couple of beers and you tell me the top three new scripting functions I should make right now for the next version. I should have 2-3 hours before the missus comes home...the clock is ticking....
Going to get some beer, back in 15 mins.
BUT i'm feeling a bit bored right now so how about if I go get a couple of beers and you tell me the top three new scripting functions I should make right now for the next version. I should have 2-3 hours before the missus comes home...the clock is ticking....
Going to get some beer, back in 15 mins.
Re: EDITOR Feature Requests (not bugs!)
For me it would be:
- a way to set the target of a monster (party, item, monster, place...)
- a way to read/write all the characteristics of a monster (like health, evasion, etc.)
- anchorPos, anchorRotation, targetPos, targetSize and onInsertItem for Altars.
- a way to set the target of a monster (party, item, monster, place...)
- a way to read/write all the characteristics of a monster (like health, evasion, etc.)
- anchorPos, anchorRotation, targetPos, targetSize and onInsertItem for Altars.