Jump to content
The Dark Mod Forums

Flanders

Campaign Dev
  • Posts

    1118
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Flanders

  1. tried again using the DOS command window. I noticed some lines flashing just before it exits. Captured it with a print screen, it says: error in state 2: expected '}'or '"spawnarg" "value"', but found 'no_random_headturning'in ..\def\tdm_ai_builder_guard.def at line 97
  2. In that case, when I run the script it does nothing with entities.js. It opens it but it makes no changes to it even if I made changes to the def files. When I run inspect.pl I get a flash screen that reads: inspect.pl v0.08 / Inspect entities and definitions and generate doc parsing definition files: def/ And when I open index.html it does not show the changes I made.
  3. Yes, I wasn't finished with that actually. I was trying to get that inspect.pl working for me. I got activeperl to run it, but it didn't create a new index.html, I thought it worked that way. The added editor_vars do show up in Dark Radiant, so I know they're working. But I wanted to check them with the documentation. Because I couldn't get it workin so far I was hoping you'd update the online documentation.
  4. I can get this error out of it: Line: 148 Character: 4 Error: 'length' is empty or not an object Code: 0
  5. Also, don't add models to the prefabs. This makes the building difficult to rotate as a whole. Mappers can add doors, awnings and such later themselves.
  6. Tels, http://bloodgate.com/mirrors/tdm/pub/doc/ does not work for me (I use internet explorer). Only this line at the bottom shows up: © 2008 by ... 0.06 (Tels). Does it work for anybody with ie? Or is it only temporarily unavailable?
  7. you can try the particle editor.
  8. For me it only happens when Doom3 is running.
  9. I understand a script cannot add descriptions, but can the script be made so that when it cannot find a description and the spawnarg is not inherited it adds to the def file: "editor_var <spawnarg_name>" "" That way, we don't have to search the entity document each time to find out what we should add and we only have to type a description between the two quotation marks.
  10. That cave map you've showed was good, not too big. I would improve that map.
  11. Yes, that's it. You might want to change this in your beginners tutorial on page 6: It does not say how to create a new response effect. great tutorial btw.
  12. Tested a little more today, no bugs yet. I noticed a small inconsistency: In the edit conversations menu to edit an actor you must click on it. Just underneath it in the commands box editing is done by a special button. Why not the same for both? Both an edit button or both an edit button and a possibility to edit it by clicking.
  13. I'm trying the stim/response editor, but it doesn't work for me. I made a stim and added it in the response tab. then, I can't make a response effect. Double clicking the window doesn't do anything, maybe I just don't get how it works.
  14. Yeah got that. So, to get it straight, what I should do for loot_base is this: search for atdm:loot_base in your entity documentation. For each spawnarg that has no description and that is not inherited add something like "editor_var snd_acquire" "Sound that is played when the loot object is acquired." to atdm:loot_base in the def file.
  15. Reading it shouldn't be a problem. Why not make a new 'Help request' thread for this and ask people to do a group of entities. I'm not going to do them all alone! I can do the loot entities to start with.
  16. All right then, lets get on with it. You can assign a group of entities to me, I'll be happy to help.
  17. damn, that's good. And it works, during my first test that is. I can test some more tomorrow. Possible improvements: a duplicate button or copy/paste buttons in the commands section of the edit conversation box would be nice. Maybe increase the size of the commands box a little and decrease the size of the actors box, there are usually more commands than actors.
  18. I agree with you Dave. It's really helpful for mappers to have all possible properties for entities in front of you like in DoomEdit. Why not use something similar as the DoomEdit entity inspector. It shows all properties in a list, all you need to do is give them a value and they become active. Or the add-property menu could have all properties listed.
  19. the same way you create a new entity but with the brush selected, rmb and create entity.
  20. the moveables that were statics could have fallen through the ground if they made contact with it.
  21. You even have a dead body to drag around?
  22. So we should add a message to Darkmod users that they should not use them for other things than the mod? Or should the files be locked somehow so they cannot be used for anything else?
  23. True. Clone is just a quick key for copy/paste. In doom 3 editor, cloning made a new brush with an offset of the old one. Since that's not the case in DR it does the same.
×
×
  • Create New...