[Sheekel wrote]:
> It's beta...
... hence the specific suggestions for the beta.
> Anyway, i doubt anyone is going to bother changing a bunch of
> source because your girlfriend accidentally blew up her
> commander once.
Oh. Ok. I had assumed the general aim here was to get people to like and play TA:Spring, and to use the game. I must have been wrong. My bad.
Besides, if you keep reading, you'll see I was wrong on this point.
> A lot of the thing you listed are all part of the learning
> process, like the click-interface. After a game or two you
> get used to it.
No, but you don't understand: What you're effectively learning is to work around the UI issues. If you want to create an insanely great game, then the answer is to smooth out the UI issues, not to force your users to compensate for them.
[Nemo wrote]:
> Well...I like FPS mode myself. Of course its not really useful for
> current games, but its a mighty neat gimmick, why remove it?
It's very a neat gimmick. I don't think the feature should be removed, I think that *maybe* the default key bindings to switch to 3D mode should be removed.
> The message box *does* display the commander countdown. You
> weren't looking closely enough =)
You're quite correct, it does. Sorry, I was simply wrong about this.
> Edit: Actually...its possible for a modder to change the self destruction
> countdown time. So if you *really* wanted to you could give the commander
> a 20 second self destruct countdown.
No, the 20 seconds was just an example, the current 5 seconds is fine.
> There is a way to change from the default view out of the box - ctrl+j or ctrl+mouse wheel click.
OK, but it's users (particularly new users) getting stuck in the other view modes and not knowing how to get out that I'm commenting on, and suggesting that maybe something can be done to prevent that (e.g. different key bindings).
> The nick %, and number at the bottom of your screen are your name,
> cpu usage %, and ping. To turn it off type .info in the message box.
Ah, thank you. Is there any chance it could maybe be off by default?
> Right click on the minimap is move there.
This doesn't work for me. I selected the commander, right clicked once on the minimap, and it changed the view to that location, but did not move the unit. What I am suggesting is the exact opposite: that right clicking on the mini-map should move the unit, but not change the view.
> F3 goes to source of last message.
Again, you're quite correct, there is a key for this that I missed.
However, the F3 function doesn't seem to work very well. To see what I mean, select your commander, press Ctrl-D to activate self-destruct, then cancel it with Ctrl-D again. Now press F3. It should stay focussed on your commander, since he was the source of the last message, but instead (for me at least) it flies off to the top left of the map. So, yes, there is a function for this, but it doesn't seem to work.
> Left/Right click confusion will go away soon, I was all set
> after about 2 hours in-game.
I completely disagree with you on this point - not because what you say is wrong, but because it's the wrong approach. Effectively, you're pushing the game's inconsistency onto the user. The hidden cost of doing this is that many users will give up in frustration. It's much better to just make the click interface consistent, so it doesn't take each user 2 hours of their life to learn to work around TA:Spring's inconsistent user-interface.
> To your points at the end:
> FPS mode should stay, if you don't like it, don't use it >_>
Fair enough. I was suggesting maybe it should be disabled in the default key bindings, but I agree it's not something you have to use, so point taken.
> Free Look mode is ideal for screenshot taking. Why remove it?
Let me rephrase: Free look mode per-se is fine, it's that free look mode is selected when jumping out of FPS mode that I have the problem with. If free look mode was like FPS (don't have to use it if you don't want to) then I would have not really have a problem with it. But if you get out of FPS mode, you *have* to use Free Look mode. That's what I object to.
> Last two are GUI issues that will be sorted when CEGUI is implemented into
> spring (currently being worked on)
>
> Actually, most of the things you mention will be solvable once real GUI
> work is done. The current GUI is really just a placeholder.
Fantastic - that's great to hear.
[smoth wrote]:
> that was a pretty shitty
review.
Why, thank you, sir/madam/immature child, for your oh-so-constructive comment. You could have been specific and constructive, as others were, but I suppose that would require some thought on your behalf. ;-)
Lastly, I'll update the
review page shortly with the above stuff to correct my mistakes, and add explanations from the above for items where I wasn't clear.
All the best,
Nick.
-----------
Edit: Those updates have now been applied:
http://nickj.org/index.php?title=Review ... oldid=1939