Page 18 of 32

Re: EDITOR Feature Requests (not bugs!)

Posted: Wed Oct 17, 2012 7:16 am
by Lollgramoth
that was extremly fast petri, thanks :)

Re: EDITOR Feature Requests (not bugs!)

Posted: Mon Oct 29, 2012 11:05 am
by JohnWordsworth
An old thread I know, but incase @petri gets some free time to do an update one day in the future, I think the following additions would be cool additions...

1. Automatically rename .tga to .dds and .model/.animation to .fbx when loading defineObject/cloneObjects from .lua files. This seems to be a common error that new modders stumble into but, unless I've missed something, just doing a quick str_replace in the last X characters of any texture/model/animation fields on import would make this problem go away.

2. Give items 'onProjectileHit', 'onMeleeHit' and 'onProjectileLand' hooks. Then we could easily make a whole host of spells that spawn items that look like spell effects and then do something when they land somewhere, hit a wall or hit a bad guy.

Sorry to dig up an old thread - I naturally have loads of ideas, but these are ones I thought might be small enough to sneak into a minor update one day! ;)

Re: EDITOR Feature Requests (not bugs!)

Posted: Sat Nov 03, 2012 4:21 am
by HaunterV
I NEED when i click on a door or secret door or anything with active/inactive or open/closed state to be able to hit a hotkey instead of manually changing it's state. like o to open a door c to close it.

OR

when placing multiple doors i need to be able to select if they are all going to be open or closed.

Re: EDITOR Feature Requests (not bugs!)

Posted: Sat Nov 03, 2012 4:35 am
by Xaxus
Kill blockages with the kill command in Preview mode, instead of having to damage it.

Re: EDITOR Feature Requests (not bugs!)

Posted: Sat Nov 03, 2012 11:53 am
by Komag
For doors that you want many of them to be open, just make one, set it to open, then copy paste it a few times for your other doors.

For blockages, you can make a starting script to make your characters (or one of them) extremely strong so one hit always kills the blockage, or give them a custom sword that hits for 500 damage or something. (But I agree that if K would kill blockages too that would be nice.)

Re: EDITOR Feature Requests (not bugs!)

Posted: Sat Nov 03, 2012 3:01 pm
by cromcrom
:arrow: A throwable = false boolean for items (would make the item fall in the same square as the party, party.facing);
:arrow: Possibility to setItemProperty(property,amount)/getItemProperty(property) for spawned items would incredibly facilitate some modding stuff (like set the attackPower/accuracy/protection/weight/coolDownTime.... of items, when appropriate).
:arrow: Some new ways to "tell things to the player". Right now, AFAIK, you can use note items, hudPrint, and wall text to transmit informations to the player. Maybe some kind of log or anything else like it so people can gain more informations.
:arrow: Some insights into creatures brains, or at least a few more brain types (cowardly, neutral...)
:arrow: In the onAttack for party, add a "what was hit if it was hit" parameter. Right now, I can't connect a monster taking damage to the party or a champion.
Or it could be a onDamage from the monster, that returns not only the type, but also the weapon/champion doing the damage (or nil)

Re: EDITOR Feature Requests (not bugs!)

Posted: Sat Nov 03, 2012 6:38 pm
by Periodiko
It would be really cool if you could turn off light flickering on light-source objects. The way to do this now is to use fx objects, which generate a steady light, but as far as I can tell fx objects don't get saved in saved game files.

Re: EDITOR Feature Requests (not bugs!)

Posted: Sun Nov 04, 2012 3:47 am
by cougardod
When crashing due to missing assets (whether from misspelling or a forgotten copy/paste) getting the error is perfect, but it would be nice if it would only prevent the map from loading and not make the dungeon editor crash.

Re: EDITOR Feature Requests (not bugs!)

Posted: Thu Nov 08, 2012 6:23 am
by Isaac
** Anchored 'Region copy & Layout copy' that allows duplication of mapped areas, or just the map layout without the objects.
Image

** Additional (dependent) Option: 'Copy to file' export/import that writes the data to a standard lua script. This would allow modders to quickly create a library folder [or zip file] of completed modular levels without having to manually write the scripts to do that themselves. Three click results that create copies of individual rooms (or floors) for later import and/or upload as a community resource.

Re: EDITOR Feature Requests (not bugs!)

Posted: Thu Nov 08, 2012 1:05 pm
by Komag
It's a good idea, I like it :)