PDA

View Full Version : Chapters, Scenarios & maps index

Pyros
August 2nd, 2005, 10:40 AM
Gentlemen,

Sooner or later, everyone is going to present scenarios and maps, so it would be better if everyone works on a predetermined field of index (concerning maps & scenarios).

I will think about this later,
In the meanwhile do you have any suggestions?

Should the separation of the index would be connected with the chapters or with the designers; should the index follow the chapters or should everyone receive 20-30 slots for personal use?)

What is better, do use slots 320, 321, 367, 368, 421, 422, 546, 547...etc (for example), or
from 320 to 340 belongs to Davide, ...etc (for example)

Each method has advantage and disadvantage, the prior helps the organization of the project (scenarios and maps will be in the proper order), while the later make the task easier for the designers...

We shall see! http://forum.shrapnelgames.com/images/smilies/happy.gif

cheers,
Pyros

p.s this (index) is part of the coding process and is related with the cloning scenarios...
wulfir
August 2nd, 2005, 10:51 AM
Pyros said:
Should the separation of the index would be connected with the chapters or with the designers; should the index follow the chapters or should everyone receive 20-30 slots for personal use?)

What is better, do use slots 320, 321, 367, 368, 421, 422, 546, 547...etc (for example), or
from 320 to 340 belongs to Davide, ...etc (for example)



I have no special preferences at this time. I'm ok with whatever you guys think is best.
FJ_MD
August 2nd, 2005, 11:18 AM
Right now I'm using a block of slots in sequential order. But I'm open to whatever the choice will be!


Davide
Weasel
August 16th, 2005, 12:15 AM
I would go with assigning each designer a bank of slots to prevent confusion and mingling of different campaign areas.
Double_Deuce
August 19th, 2005, 09:17 PM
Weasel said:
I would go with assigning each designer a bank of slots to prevent confusion and mingling of different campaign areas.

I would 2nd that. Assign the blocks, then we all know where we can work in and we won't be accidently writing over anyones work if we send files back and forth to be tested, reviewed, etc.