[Is there a] Jan/Feb Preview[?]

[Copperknickers]

Just imagine what would apparently happen to you if we released EB2 straight away? That extended period of drooling suspense is just there to train you cope with it. And let us have some fun with it too beforehand.

I hope EB 2 waits at least a year from noiw bwfore it is released. The only forseeable thing that would occur if EB 2 was released now is that the drool that would have been released slowly iver a long period of time would all come out at once. So by all means, slow and steady so we get a good finished product.

[Teleklos Archelaou]

People are still complaining about how their Cpu's aren't fast enough to run EB1, how in the world are they going to run EB2 within the next two years?!

[Obelics]

two years is just the time i think i will change my comp.

[cmacq]

People are still complaining about how their Cpu's aren't fast enough to run EB1, how in the world are they going to run EB2 within the next two years?!

What would be the requirements for a not too slow, or a fast run, for EB2?

[Disciple of Tacitus]

Since I'm in the market for a new computer, I - too - would like to know if there are any ideas on system requirements ... or perhaps "preferences"?

[cmacq]

Since I'm in the market for a new computer, I - too - would like to know if there are any ideas on system requirements ... or perhaps "preferences"?

Indeed, I'm in the market as well.

[Tellos Athenaios]

Probably the future equivalent of an EB-Proof rig nowadays?

No, honestly how is anyone supposed to know? On one hand the M2TW engine comes with the assumption of a much more potent PC than does the RTW one. (AFAIK the optimization towards lower-end-of-the-market system isn't pursued as far as was the case with RTW which runs on minimum requirements comparable to that of an age-old semi-3D strategy game we all know as 'Age of Empires'... )

On the other hand the entire scripting department seems now much more smooth, and much more integrated design: no more fancy work-arounds for the lack of persistency with event-counters to name just one big obstacle which causes the reforms to be far more complexed in EB1 than would ever have needed to be the case with the improved support of scripting for M2TW. Another is that it appears at least one big chunk of movement code & spawning code for client rulers and similar events can be immensely simplified because of the support of abstract names (labels) and more abstract commands for controlling characters on the campaign map. (Think of this: you can name a character by a label, and let the enigne do the gruesome task of keeping track of his actual in-game name. Then you can move him by using the label, rather than the actual name.)

[cmacq]

I get the idea, thanks for th help.