Page 1 of 1

What Marshall should not do

Posted: Thu Nov 09, 2006 3:39 pm
by bOrIuM
I think Marshall should not listen to all propositions written down on that forum and just follow his own idea of the game instead of all the interpretations of the peoples here. This will surelly make the game better and comin out faster. It's sure we can place a critic on what we see, but its important to not take too much time on developping the game. I think only critics to improve the game should be taken (such like a future scenario editor).

As Im goin impatient to play at, I think it's the best idea to have a better et sooner game.
or perhaps my subject should be... what Marshall should do...

RE: What Marshall should not do

Posted: Thu Nov 09, 2006 8:02 pm
by Joisey
Nope, [:-] I don't think a game was ever worse off because it got player feedback during development.

RE: What Marshall should not do

Posted: Thu Nov 09, 2006 9:29 pm
by 1LTRambo
I agree. And if you could go back and read some of the very important posts form say two years ago, you would see that the feedback Marshall received definately changed the course of the game. Also, from this forum came beta testers who have no doubt speeded up the games development and will make for a better release.
I still say that I'm willing to wait for a quality game as opposed to some piece of garbage that was release quickly.

RE: What Marshall should not do

Posted: Thu Nov 09, 2006 10:03 pm
by MarshallEllis
Hey guys:
 
You're all right!
There's a medium.
Listen to the player community while not taking too much time (Wooops!).
I've listened to the player community and it has helped a lot! I've also taken way more time than expected BUT the game will be better for it.
I've learned a lot.
 
Thank you

RE: What Marshall should not do

Posted: Thu Nov 09, 2006 10:05 pm
by coregames
ORIGINAL: bOrIuM

I think Marshall should not listen to all propositions written down on that forum and just follow his own idea of the game instead of all the interpretations of the peoples here. This will surelly make the game better and comin out faster.
The game was close to finished when Marshall decided (I think wisely) to incorporate TMR into the leader ratings. Delays for important changes such as this will make the game better and satisfy long-time EiA fans; I think he has done well to take into account relevant input from these boards. Don't forget, this is based on a pre-existing board game, and many of the suggestions we have made were due to our passion for the game. Now we are on the home stretch, and I think in the final analysis most of us will be glad he was patient and open to ideas on how to improve MEiA.

RE: What Marshall should not do

Posted: Thu Nov 09, 2006 10:12 pm
by MarshallEllis
Hey all:
 
Let me expand on what Marshall should not do:
 
1. NEVER change directions in the middle of a project.
2. NEVER assume ANY code is final. Things change ... #### happens!
3. NEVER talk too much on the forums early. I've said a lot that have changed (See #2) thus creating that group of quoters out there "But you said...". This is the reason for me staying away form the forums for a while. You can't be quoted if you don't say anything.
4. NEVER take this too seriously. This is game ya know. I'm just lucky and happy to be able to code this thing.
 
Anyway, just a few additions to this thread from myself...
 
Thank you
 
 
 
 
 
 

RE: What Marshall should not do

Posted: Thu Nov 09, 2006 11:25 pm
by denisonh
Said well enough.

To paraphrase Al Davis - Just publish a winner baby
ORIGINAL: Marshall Ellis

Hey all:

Let me expand on what Marshall should not do:

1. NEVER change directions in the middle of a project.
2. NEVER assume ANY code is final. Things change ... #### happens!
3. NEVER talk too much on the forums early. I've said a lot that have changed (See #2) thus creating that group of quoters out there "But you said...". This is the reason for me staying away form the forums for a while. You can't be quoted if you don't say anything.
4. NEVER take this too seriously. This is game ya know. I'm just lucky and happy to be able to code this thing.

Anyway, just a few additions to this thread from myself...

Thank you






RE: What Marshall should not do

Posted: Fri Nov 10, 2006 4:19 pm
by Sonny
ORIGINAL: denisonh

Said well enough.

To paraphrase Al Davis - Just publish a winner baby
ORIGINAL: Marshall Ellis

Hey all:

Let me expand on what Marshall should not do:

1. NEVER change directions in the middle of a project.
2. NEVER assume ANY code is final. Things change ... #### happens!
3. NEVER talk too much on the forums early. I've said a lot that have changed (See #2) thus creating that group of quoters out there "But you said...". This is the reason for me staying away form the forums for a while. You can't be quoted if you don't say anything.
4. NEVER take this too seriously. This is game ya know. I'm just lucky and happy to be able to code this thing.

Anyway, just a few additions to this thread from myself...

Thank you






Other than John Madden did Al Davis ever have a coach last more than 2 1/2 years??[:D]

RE: What Marshall should not do

Posted: Fri Nov 10, 2006 6:08 pm
by anarchyintheuk
Tom Flores, but your point is well taken. [:)]

RE: What Marshall should not do

Posted: Fri Nov 10, 2006 7:47 pm
by Camile Desmoulins
ORIGINAL: bOrIuM

I think Marshall should not listen to all propositions written down on that forum and just follow his own idea of the game instead of all the interpretations of the peoples here. This will surelly make the game better and comin out faster. It's sure we can place a critic on what we see, but its important to not take too much time on developping the game. I think only critics to improve the game should be taken (such like a future scenario editor).

As Im goin impatient to play at, I think it's the best idea to have a better et sooner game.
or perhaps my subject should be... what Marshall should do...

I think that you think that some people (me, for instance), are advising to Marshall for change, in the last moment, some features of the game.

This idea is far from the reality

First, I'm talking about the original game, some features that i'd like change (home rules). This is not a suggestion to change the actual work of Marshall. Only a desideratum, or a brainstorming, as you like.

Second, I don't think that it can be a good idea to change a projec almost in the finish line. It would be a fool's idea, after some years of waiting.

Third, I ever support Marshall's work (even in the hardest momments, when some people was criticized Marshall's project, hard critics that Marshall, today, with elegancy, "forget" to join everybody around this project), my suggestion and constructive critics was made in 2003-2004, not in 2006.

For me, now is the time of enjoy with the game. After played, if it's necessary, I'll make again new constructive suggestions. And I hope that this projet would be as good as it seems.

And of course, fight against you in the battleground or in the lounges of the Palaces or Embassys, diplomacy fighting [:)]

Camille


RE: What Marshall should not do

Posted: Fri Nov 10, 2006 10:22 pm
by Sonny
ORIGINAL: anarchyintheuk

Tom Flores, but your point is well taken. [:)]

I knew there would be some wise guy who knew Raiders coaches.
Wasn't Art Shell there for more than 2 1/2 years also (the first time)?

RE: What Marshall should not do

Posted: Sat Nov 11, 2006 1:20 pm
by pzgndr
1. NEVER change directions in the middle of a project.
3. NEVER talk too much on the forums early. I've said a lot that have changed (See #2) thus creating that group of quoters out there "But you said...". This is the reason for me staying away form the forums for a while. You can't be quoted if you don't say anything.

I've been monitoring this development and looking forward to release. Ever since David Heath provided a short demo of way back in 2004 at WBC. Yes, I saw EIA working with my own eyes! And waiting patiently ever since.

Despite the delays, IMHO these forum exchanges HAVE been useful and should result in a much better game than what might have been released if #1 and #3 above had been followed. Developers SHOULD discuss their game ideas and get some feedback, and if/when necessary make adjustments. That's a win-win strategy. The "quoters" need to realize that changes and delays are usually in their best long-term interest and refrain from whining.

RE: What Marshall should not do

Posted: Sat Nov 11, 2006 11:57 pm
by bOrIuM
This will be "un grand plaisir" to fight against or with you on the battleground of this game once it will be released.
ORIGINAL: Camile Desmoulins

And of course, fight against you in the battleground or in the lounges of the Palaces or Embassys, diplomacy fighting [:)]

Camille


RE: What Marshall should not do

Posted: Tue Nov 14, 2006 7:38 am
by Norden_slith
What Marshall should not do:

Staying quiet for too long at a time [;)].

Come on, pictures, AAR, anything....


Norden

RE: What Marshall should not do

Posted: Tue Nov 14, 2006 9:25 pm
by MarshallEllis
Norden:
 
We're trying. Hang tight.
 
Thank you

RE: What Marshall should not do

Posted: Wed Nov 15, 2006 3:01 pm
by Joisey
Yeah, show us another screen shot on another aspect of the game we haven't seen yet.

Suggestions:

Naval combat
Unit build menu
Paying expenses
Siege Combat
Trivial Combat
Forage Rolls
Peace Condition Menu

[8D]

RE: What Marshall should not do

Posted: Wed Nov 15, 2006 7:38 pm
by Ursa MAior
ORIGINAL: Joisey

Yeah, show us another screen shot on another aspect of the game we haven't seen yet.

Suggestions:

Naval combat
Unit build menu
Paying expenses
Siege Combat
Trivial Combat
Forage Rolls
Peace Condition Menu

[8D]

Second to that. Please.

RE: What Marshall should not do

Posted: Wed Nov 15, 2006 11:39 pm
by 1LTRambo
ORIGINAL: Ursa MAior
ORIGINAL: Joisey

Yeah, show us another screen shot on another aspect of the game we haven't seen yet.

Suggestions:

Naval combat
Unit build menu
Paying expenses
Siege Combat
Trivial Combat
Forage Rolls
Peace Condition Menu

[8D]

Second to that. Please.

Third that. [:)]