: "I still think it's not that bad though."
: It is. I only recorded a little to prove it. If it wasn't a large issue, then
: I wouldn't be complaining about it as much. Nor would I have placed it at
: the end of the video, where it would be remembered the easiest.

OK, it is that bad for you, how about that? It's not that bad for me or anyone else I've talked to or heard from.

: Soooooo... Like we're already having to do now , to move a block that
: you've just spawned?

Has having to hold down a trigger made you do less accidental moves? (I really doubt it.) Does it not annoy you you have to do that now? With your suggestion, to move something, you'd have to hold down two buttons, and then hold down a trigger. That's getting into ridiculous territory to accomplish one action.

: I honestly don't understand how you're not getting this. The. More Time You
: Have To Select. The. More. Time. You. Have. To. Prevent. A. Accidental.
: Selection.

It would be a set, simple interaction, and once you got used to it it would be done very quickly with very little thought. People would definitely get in the habit of pressing both at once, unless they had to be pressed in order (which would be awful), then it would be one slightly before the other. You do not have time to make a decision during a button press, especially if it's immediately before or during another one.

: But it does count.

It does count-- it counts against high-level usability because it's another finger movement to get a task done. It should require as few as possible for efficiency and speed.

I guarantee you if they had it that way in the first place you'd still be complaining about selecting the wrong thing, because the aiming is finicky, the selection area is tiny, and you apparently can't read the text under the cursor.

What would you have them use for this? Every button and trigger on the controller already has a function and most of them have two.

I would also reiterate, you can not mess up your map by simply selecting an object. The most that can do is change the spawn point for an object that has moved, and you should be able to just move it back.

: Another glitch to add to the list. Greeeeeeeat. should be labeled as
: "Unison Physics" with a On or Off option. Not a entire separate
: category, different from grouping.
: Wielding does need to be change to not Unwield, when you Ungroup it from
: non-wielded items.

They would have to program it to have two kinds of groups, and not call one of them a group, and allow objects to be part of one group of each type at the same time. That's easy, in theory, but there might be issues with doing that, especially now. There's also still the question of how you would add things to a group and a welded group and how you should show the user membership in each separately and together.

: The more I think about it, the more glitches I remember to list.
: So I'll ask you, if you've encountered this one as well. When I have made a
: group, I change the parent item (something I've been doing in 3D for years
: now). It's needed for properly rotating with scripts. However, the change
: in parenting does not stick. It's clearly changed in the menu. But when I
: go to rotate or script a rotation, the parent jumps back to the original.
: I've tried selecting the desire parent first, but the feature seems to
: have a mind of it's own.

I haven't seen that, no.

: I sure hope so. There is a ton of people that, on Facebook, that feel the
: same way. Going so far as to say Reach's Forge is better. Which it's not,
: by a long shot. The menu system has most of them confused. And many just
: refuse to learn the new controls. Personally, I can get past the controls.
: It's just going to take me time. But with all of the great new options and
: features, these consistent errors and glitches are ruining the experience
: for me. My Delta map (now cut in half and renamed The Spider Pit) took me
: one afternoon to make in H2A. And that's with me nitpicking over dumb
: details just for a proof of concept map. The new controls aside, the Halo
: 5 version has taken me almost a week, just to get to where I am now. Once
: again, which I've cut in half due to frustration.

The glitches and wonkiness have been my big obstacle too. I almost gave up for a while at least five times over the last two days. In particular scripted rotation and spawning have the weirdest behavior. The rotation is jerky and doesn't use a reasonable center point a lot of the time, and I found out by accident if you're standing near scripted spawn items they won't spawn or despawn (which I took advantage of to fix items respawning when they shouldn't in a setpiece map).

: Correct me if I'm wrong, and I probably am. But didn't 343, or one of the
: community forgers, mention that we would be getting a spartan to place on
: our maps for size reference? I can't find it in the menu. I'll check the
: videos again and link to it, if I find the mention. It sure would help a
: great deal. I didn't realize just how large my map looked, next to a
: spartan, until I saw a buddy run through it. It feels much smaller in FPS
: and Edit mode, then it looks.

That kind of sounds familiar.
I placed various blocks and stood next to them and I'd say a Spartan in Halo 5 is about 7 Forge units tall, and a crouching Spartan is 4 units tall. The cover pieces being 4.5 units and there being 4 and 8 unit wall pieces support these estimates.