SC2Mapster

Quote from DrSuperEvil: Go

I favour 2 but with a space between the two lists. And dont forget the Banker SOps.

Banker SOps?

@DrSuperEvil: Go

now to consider what would look good.

Option 1:

Actors

Action

....

Site Operations

Site Operation - 2D Rotation

Site Operation - Action

...

Snapshot

Sound

Option 2

Actors

Action

....

Site Operation - 2D Rotation

Site Operation - Action

...

Snapshot

Sound

...

Site Operations

2D Rotation

Action

...

Option 3

Same as option 2 but then without the "Site-Operation - ... " listed in between the other types.

Option 4

An idea someone else might have ;p

Suggestion

my suggestion would be either option 2 or 3.

@DrSuperEvil: Go

I figured the Actor page would have a layout like this:

• General Info area
• List of Actor Types
  Siteops as single name for all the siteops variants.
  • sublist below the Siteops header which contain all the seperate siteops actor types.

So basicly all the siteops links are on the Actor page, including a link to the Site Ops General Page.

and for the Site Ops General Page: (Linked to from pages that are related to any siteops actor)

• General Siteops info
• List of Siteops Actors (Example)

@DrSuperEvil: Go

Well we have a general Actors page, and we could make a generic siteops page.
So siteops would end up at the following location:

• Actors
  • Site Operations (General explanation Site operations + list of Site Operation Types)
    • Specific Site Operation Types (eg. Actors / Site Operations / 2D Rotation)
  • Other Actor Types (eg. Actors / Unit)

and for the events bit we have the following options:

1. Actors / Event / Event (as it is now)
2. Actors / Events (my suggestion)
   Maybe have the following redirects
   1. Actors / Events / Send (redirect to Actors/Events or Send specific info)
   2. Actors / Events / Target (redirect to Actors/Events or Target specific info)
   3. Actors / Events / Terms (redirect to Actors/Events or Terms specific info)
   4. Actors / Event (redirect to Actors/Events)
   5. Actors / Event / Event (redirect to Actors/Events)
3. Other Idea's?

@DrSuperEvil: Go

ok so perhaps scrap the Base Types bit. So what would then be a good setup?

Currently:

• Actors
  • Type
    • Fields of the Actor data type
  • Event
    • Event - Events+ bit explained here
  • UI
    • Highlight Tooltip

Option A:

• Actors
  • Types
    • Specific Actor Types
  • Fields that are complex appear at multiple actor types and require their own page
    Like the Events+ page (Events-Send, Events-Target, Events-Terms)

Option B:

• Actors
  • Specific Actor Types (No Type in between)
  • Fields that are complex appear at multiple actor types and require their own page
    Like the Events+ page (Events-Send, Events-Target, Events-Terms)

other ideas??

Quote from DrSuperEvil: Go

And how many base types will there be? I am having trouble visualizing what they will look like

I'd think there would be like 10-15 base types(maybe less), compared to the 30+ types

basicly a base type will contain the core information for that base type.
look in the editor in raw data mode, and you will see that a doodad actor for example has fields which start with:

• CActor
• CActorBase
• CActorBearings
• CActorDoodad
• CActorModel

basicly what I suggest is that the base types contain these specific sets, while the types have the combination of the ones used.

The current setup is not optimal in my opinion, so I'm just throwing this in the group to see what the rest thinks.

Currently the Actor data-type has the following structure:

• Actors
  • Type
    • Fields of the Actor data type
  • Event
    • Event - Events+ bit explained here
  • UI
    • Highlight Tooltip

Actors section is an annoying section to create further. it might be good to split this up like this:

• Actors
  • BaseTypes
    • Specific Base Type
      The content of these pages can be copy/pasted to quickly create the useable types. mention in the pages what types inherit from it.
  • Types
    • Specific Actor Types
      The content of these pages are made up by combining the Specific Base Types. (eg. the Doodad actor is made up out of: default, base, bearings, doodad, model)
  • Pages which are complex that require their own page
    Like the Events+ page (Events-Send, Events-Target, Events-Terms)

So when creating a Type, you add references to the BaseTypes, incase that the info isn't listed yet at that Type.
At the BaseTypes you add references to the Types, so you can update those when a BaseType is adjusted.
From both you can link to the Complex Pages like the Events+ page.

This is entirely open for discussion at this moment. So if anyone thinks he has a better idea or improvements to the current idea, post it here and let us discuss it.