@AtikLYar: Go uuuhhh... oohhh... mom just let me sleep for another 10 minutes ok?
Now seriously, How is the blueprint going? This thread has accumulated huge amounts of ideas and we've been away from it for some time, its kind of hard to define where exaclty we stand and go on.
I have tried to get everything from this thread into the blueprint. I recall you mentioning that you would take a look at it, and decided to let you before I messed it up any more.....
@AtikLYar: Go Yeah, I said I'd work on it. But since the beginning of this project I'm the one updating the map file, and right now I dont have time to work on both tasks, so feel free to go on and abuse it :-)
@AtikLYar: Go Ok, so you can tell what exactly we should be discussing here. I know many aspects were left undecided, like details of the high tier tech tree. We need to decide more things, some of them could have been already added to the map file.
@AtikLYar: Go From those the Scout Drone, the SCU and very early versions of the Drillbot and Clanker are already in game. I can work on some of the others but we still havent fized the structures yet. And DrSuperEvil's merge system isnt included so merged units will have to be trained normally for now.
We never did decide how merged units should be unlocked I don't believe.
I think the two idea were they become available by building certain structures, or you researched they 'blueprints' at either the barracks-buildings or the egineering bay-buildings.
Look, I have been spending my limited free time making rather heafty SC2 game mechanics systems. Do I really have to do all the thinking around here data wise?
Also some merges could be rearched as other troop enabling structures.
@DrSuperEvil: Go You have to do all the thinking for the data mechanics only you can understand :-D For all the mortal-level data issues I'm sure we can work on it as well.
AtikLYar didn't include my transport unit idea in the blueprint.
Well, if it was "out-voted" as you say, then it was out-voted... moving on. I'm working on some placeholders, right now I have a "spaceport" strcuture and the Walker unit.
I was actually thinking on the Liner and the Walker.
iirc, we had made the clanker a combination of the SCU and either scout or drillbot.
I was wondering if the liner or the walker should be a fused unit. Perhaps the liner is a walker and scout hybrid? (The scout would be most of the body, with the walker becomming the thing it drags?)
Thought drillbot was also meant to be a fused unit while the walker was something like 2x SCUs for the 4x legs. For the liner maybe 2-3x scouts and something T1?
With the exception of the most basic units and the T3 ground unit all the more complex units are fused. Also ideally using multiple basic units and where possible avoiding merge trees where the products of previous merges are requirements.
Maybe we could convert the T1.5 flying fan into the base unit for merging most air units.
While in teory all that works, I still want to see how those ideas are going to be created visually, when we finally get to the point of using custom models. Right now I can't imagine 2 scout drones forming anything useful, and that goes for all our units right now. But maybe just because my mnid is stuck with their current models.
Read the race blueprint.
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
WAKE UP!
@AtikLYar: Go uuuhhh... oohhh... mom just let me sleep for another 10 minutes ok?
Now seriously, How is the blueprint going? This thread has accumulated huge amounts of ideas and we've been away from it for some time, its kind of hard to define where exaclty we stand and go on.
I have tried to get everything from this thread into the blueprint. I recall you mentioning that you would take a look at it, and decided to let you before I messed it up any more.....
@AtikLYar: Go Yeah, I said I'd work on it. But since the beginning of this project I'm the one updating the map file, and right now I dont have time to work on both tasks, so feel free to go on and abuse it :-)
The thing is, like I said, I think I have everything.....
The thing is that the discussion suddenly stopped... there hasn't really been anything left to update....
@AtikLYar: Go Ok, so you can tell what exactly we should be discussing here. I know many aspects were left undecided, like details of the high tier tech tree. We need to decide more things, some of them could have been already added to the map file.
Well now, for one thing, I know we were trying to cut down unit roles, so we know which ones to include for melee maps.
The scout drone was the marine.
The SCV was the marauder.
I believe either the Clanker or Drillbot was going to be the Reaper.
The repair detector was going to be the Raven.
The liner was going to maybe be like the seige tank.
The walker was going to be the Hellion.
The bomber bot was going to be the banshee.
The Ariel ace was going to be the viking.
The hauler was going to be the Medivac
And the Powerhouse Ground/Air would be the Thor/Battlecruiser
(Using Terran becaue it is easiest for me to remember.....)
@AtikLYar: Go From those the Scout Drone, the SCU and very early versions of the Drillbot and Clanker are already in game. I can work on some of the others but we still havent fized the structures yet. And DrSuperEvil's merge system isnt included so merged units will have to be trained normally for now.
Alright, sounds good.
We never did decide how merged units should be unlocked I don't believe.
I think the two idea were they become available by building certain structures, or you researched they 'blueprints' at either the barracks-buildings or the egineering bay-buildings.
Look, I have been spending my limited free time making rather heafty SC2 game mechanics systems. Do I really have to do all the thinking around here data wise?
Also some merges could be rearched as other troop enabling structures.
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 You have to do all the thinking for the data mechanics only you can understand :-D For all the mortal-level data issues I'm sure we can work on it as well.
AtikLYar didn't include my transport unit idea in the blueprint.
@SoulFilcher: Go
Which one was that?
I remember a discussion about an air transport, and I believe we got out-voted as most of the others liked the Hauler better....
Yeah, two transports would be excessive and all other races use an air transport so having a leaping land based one would be unique.
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
Well, if it was "out-voted" as you say, then it was out-voted... moving on. I'm working on some placeholders, right now I have a "spaceport" strcuture and the Walker unit.
I was actually thinking on the Liner and the Walker.
iirc, we had made the clanker a combination of the SCU and either scout or drillbot.
I was wondering if the liner or the walker should be a fused unit. Perhaps the liner is a walker and scout hybrid? (The scout would be most of the body, with the walker becomming the thing it drags?)
Thought drillbot was also meant to be a fused unit while the walker was something like 2x SCUs for the 4x legs. For the liner maybe 2-3x scouts and something T1?
With the exception of the most basic units and the T3 ground unit all the more complex units are fused. Also ideally using multiple basic units and where possible avoiding merge trees where the products of previous merges are requirements.
Maybe we could convert the T1.5 flying fan into the base unit for merging most air units.
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
While in teory all that works, I still want to see how those ideas are going to be created visually, when we finally get to the point of using custom models. Right now I can't imagine 2 scout drones forming anything useful, and that goes for all our units right now. But maybe just because my mnid is stuck with their current models.
Scout drone has a nice barrel like body that could be retrofitted to act as a tank or cylinder.
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 still have this idea of the SCU being able to open up when it fuses, like cracking an egg or something.
And I thought the Scout, SCU, Drillbot, and Detector were all built units, used for fusions....