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.
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.
I like the option B. Though I believe there should be an intoductory paragraph at the top of the page giving a general summary of what actors/SOps are. Also the Actor types should be listed in the order they appear in the data editor when sorted by type. An alternative would be to have all SOps seperately but in a similar order.
The text inbetween the actor types was put in by some individual who had no clue about 75% of that he was typing and never has been seen in the wiki again. Just to please Avogadro I did not delete it and corrected any blatant errors (the guy didn't even know what the SOp (attachment) was used for even though I had already written the page for it).
The UI also seems to be an abandoned project for giving pics showing the various fonts and strings needed to reference the values of data fields which are useful for abilities which have upgrading stats.
The Events+ deserve their own pages because some really can become mountains out of molehills covering several data types like the Texture Select By Id or Model Event events. The Events+ page should be left as it is because it reflects the format of the event editor unlike the fields in the actors which are very confusing and cannot be directly edited without being in View Raw Data mode (though there are a few exceptions where this is needed with beams).
Why can the list of SOps not link directly to the specific types like the effects/behaviors section of the wiki? As for events I say we leave the layout as it is now though we could change the size of the text for the links to the individual event pages. The events+ page is currently in the format of how you create new events in the editor with Event>Terms>Action. Also several events do not need the target field.
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 section is an annoying section to create further. it might be good to split this up like this:
The content of these pages can be copy/pasted to quickly create the useable types. mention in the pages what types inherit from it.
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)
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.
And how many base types will there be? I am having trouble visualizing what they will look like
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg
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:
basicly what I suggest is that the base types contain these specific sets, while the types have the combination of the ones used.
And a few extra fields unique to them.
Otherwise cannot hurt since there are several unknown fields which are shared between actors.
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg
@DrSuperEvil: Go
ok so perhaps scrap the Base Types bit. So what would then be a good setup?
Currently:
Option A:
Like the Events+ page (Events-Send, Events-Target, Events-Terms)
Option B:
Like the Events+ page (Events-Send, Events-Target, Events-Terms)
other ideas??
I like the option B. Though I believe there should be an intoductory paragraph at the top of the page giving a general summary of what actors/SOps are. Also the Actor types should be listed in the order they appear in the data editor when sorted by type. An alternative would be to have all SOps seperately but in a similar order.
The text inbetween the actor types was put in by some individual who had no clue about 75% of that he was typing and never has been seen in the wiki again. Just to please Avogadro I did not delete it and corrected any blatant errors (the guy didn't even know what the SOp (attachment) was used for even though I had already written the page for it).
The UI also seems to be an abandoned project for giving pics showing the various fonts and strings needed to reference the values of data fields which are useful for abilities which have upgrading stats.
The Events+ deserve their own pages because some really can become mountains out of molehills covering several data types like the Texture Select By Id or Model Event events. The Events+ page should be left as it is because it reflects the format of the event editor unlike the fields in the actors which are very confusing and cannot be directly edited without being in View Raw Data mode (though there are a few exceptions where this is needed with beams).
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg
@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:
and for the events bit we have the following options:
Maybe have the following redirects
Why can the list of SOps not link directly to the specific types like the effects/behaviors section of the wiki? As for events I say we leave the layout as it is now though we could change the size of the text for the links to the individual event pages. The events+ page is currently in the format of how you create new events in the editor with Event>Terms>Action. Also several events do not need the target field.
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg
@DrSuperEvil: Go
I figured the Actor page would have a layout like this:
Siteops as single name for all the siteops variants.
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)
I presume you mean without the text inbetween but otherwise I agree.
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg
@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.
I favour 2 but with a space between the two lists. And dont forget the Banker SOps.
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg
Banker SOps?
There is a kind of SOp called Banker and Banker (Unit). It is mostly used by flying units to make them lean when turning a corner.
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg