hmm. The language is a huge barrier when you're looking at the tools. There's alot of info infront of you, but you have to learn what tools are, how they are used, and the definitions of things in the tutorials will give you clues in how to use them.

There are settings and attributes to things.. you have to learn how to create them within the parameters of deedit.. it's not easy, and I hope it is better explained for you soon.

I wish I could help, but I'm blind as a bat with this at the moment. I know how to understand things you describing, but I don't have it infront of me.

I guess some people know everything and wont tell you what you need to know, or haven't read your post.. yet.

xistence Wrote:The problem might not be the fact that the people won't help at all, more that the place where you ask in particular might not be the best. Some sites are more dedicated into editing then other (also for Tron2.0 stuff).

This. Much as I love Tron-Sector, it's not the ideal place to ask for map making advice. For example, over at LDSO we have several members who have made maps but don't frequently visit here and won't see your posts.

Also, I know you might not like what I'm about to say or won't want to hear it tron_man. But I'm going to say it anyway.

From what I can tell, you're trying to go too complicated too soon. AI, moving objects, and effects on your first map . . . you need to learn to crawl, before you can fly or even walk. Start simple. Just make a simple map, to get the hang of map making.

Every one of us who released maps, first made a simple test map that we never released. Once we'd gotten the basics down, we moved on to more complicated things. It was only after I'd made a test map, and then my first real map, that I raised my ambition toward making something more complex with AI and lots of special effects.

This message isn't meant to discourage you. Just the opposite. Set aside the map you're currently working on, for now. Do another really simple map first, and get it working. You can always come back to the other map and finish it, once you've perfected your first simpler map. And if you need any help, consider asking members over at LDSO for advice.

Just as a 'guiding line' (how you can begin, at least you're free to decide if you want to do it that way):

-Have a plan/concept/sketch/script/whatever. They better you know -what- you want to get at the end, the -better- you can get ideas how to reach your target (and the more you understand the engine itself step by step for yourself -> you'll get better solutions). It makes it even simplier for you to ask the right question if you need help or advice.
-Then start understanding the different gamemodes, some need objects and those have to be set up correctly for maps like DiscArena. They are great obstacles at the begin and can crash your map.
-Then try to understand the work with 3D-stuff like geometry, brushes, textures. They're also great resources to do things wrong. Do it in small steps, so you can reverse your work to locate -where- your mistake might be. Save often, save early, make backups of your maps at major points. There are great tutorials already how to do 'good' architecture, this is a general way hot to do it so many 3D-tutorials can help or give you ideas about that stuff.
-Then experiment with objects. Create sorts of 'testing'-maps, small rooms with just a spawnpoint or similar, to test out an object with all its setting. The better you know them, the easier you can avoid problems with them.
And finally: know your tools, check out all menus, settings, remind what you have done, so you can reverse your steps in case something went wrong. Check out your key-settings in DEdit. This program has much more options and functions than it reveals through the mouseclicks or menus. The better you can handle your tools, the easier is your workflow and the better the quality of your result.

I personally think this might be a good order to understands things step by step. Also the frustration-level will be lower if you keep yourself a 'backdoor' open with things like backups and small work-steps, because nothing is more worse then to lost hours of work just because of a small mistake.