Advertisement
Guest User

Morph Discussion

a guest
Nov 3rd, 2014
333
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 39.63 KB | None | 0 0
  1. GoogleFrog - Klon as far as I can tell people want random slippery slope
  2. Klon - eh
  3. Klon - this is about unit morph?
  4. Klon - dont quite get what you want to say
  5. GoogleFrog - as in morph further rewards you for killing units with your units and surviving
  6. Klon - yeah it does add to the slippery slope a bit, but not much
  7. GoogleFrog - and it is fairly random
  8. Klon - on the other hand, it also gives the player with better survival skills and edge over the economically stronger, if the game develops that way
  9. GoogleFrog - as in you can't plan to raid their base with 5 glaives and then move back a bit and morph one to warrior
  10. GoogleFrog - who knows how the engadgement will go
  11. Klon - well, depends on the base
  12. Klon - but you can plan on other things, like killing a com with some mid sized unit and then morph it
  13. Klon - depends on the situation and involved units if its random or not
  14. Klon - for bigger units the only random part is which unit gets the vet, if there are more than 1
  15. GoogleFrog - I'll say that many things are somewhat randomish and important. Whether a commander dive works for example.
  16. GoogleFrog - But that I don't see the need to add extra randomness which has poor integration
  17. Klon - the random part is really only relevant for small units
  18. Klon - which usualy arent that powerful to morph anyway, some special cases like flea->glaive or glaive->scythe put aside
  19. GoogleFrog - those are most of the cases
  20. GoogleFrog - glaive -> warrior is powerful because warriors are slow
  21. Klon - everything from ravager size upwards is increasingly predictable
  22. GoogleFrog - you could get a warrior behind their base
  23. Klon - well ok
  24. Klon - i never did that
  25. GoogleFrog - I've farmed for Zeus -> Crabe and it is not that predictable
  26. GoogleFrog - you've got to manage who gets the last hit
  27. Klon - well
  28. Klon - zeuses are fairly easy to keep alive
  29. Klon - sure it doesnt always work, but its pretty predictable
  30. GoogleFrog - it can mean the difference of minutes
  31. Klon - ofc you cant pinpoint it, sometimes the wrong unit gets it, but if you got a couple of zeuses and keep them alive, you will get morphs
  32. Klon - yeah it can
  33. Klon - idk, i dont see a problem with that amount of random really
  34. GoogleFrog - so I we've got this extra mirco game where selectively forcing your units to not fire is required to implement your large scale plan of morphing to something
  35. Klon - but thats not realistic, does anyone do that?
  36. GoogleFrog - yes
  37. Klon - besides this is still only applicable for small to mid units, large units dont need that
  38. GoogleFrog - I've tried on occasion
  39. GoogleFrog - now we've hit on the Owling argument
  40. Klon - well ok, but its not really worth it imo
  41. Klon - its costly in terms of micro and risk
  42. GoogleFrog - that the morph-proponents want a system so weak that people can safely ignore it exists if they want to
  43. Klon - compared with the tradeoff you get for morphing small units
  44. GoogleFrog - a so-called "optional feature"
  45. Klon - i dont see why it should be owled either
  46. GoogleFrog - if morph is optional then it has been owled
  47. Klon - its optional right now because morph doesnt offer anything you cant get otherwise
  48. GoogleFrog - yes it does
  49. GoogleFrog - it offers you a unit at a wider range of locations without paying for the factory or the BP
  50. GoogleFrog - If I want 1 Crabe then the cheapest way to do it is morph a Zeus
  51. Klon - yeah, ok. but its not mandatory, and there are no units that you can only get from morph
  52. GoogleFrog - if I want 1 Warrior behind their base the fastest way to do it is morph Glaive
  53. Klon - right
  54. GoogleFrog - that isn't what mandatory means
  55. Klon - mandatory means necessary?
  56. GoogleFrog - it's not necessary to use every unit type all the time though
  57. GoogleFrog - if a morph-only unit was actually really really bad to have then the morph to it isn't necessary either
  58. Klon - well no, but using morph at all isnt something that gives you a huge edge, its something you can easily forgo entirely
  59. GoogleFrog - idk how you can say that
  60. GoogleFrog - what about warrior in the back of their base?
  61. Klon - that was my point, there is no meta for morphing things
  62. GoogleFrog - zeus -> crabe to counter all those rockos which are attacking my zeus?
  63. GoogleFrog - there is no meta for a lot of stuff
  64. Klon - a com can kill a warrior 1v1, dies to llt+defender, while annoying a warrior in the back of the base can be dealt with
  65. GoogleFrog - lots of people have to do it a realize it can be done to make up a meta
  66. Klon - well hammers do counter a crabe, and if he morphs a crabe, he needs time and money
  67. Klon - i just dont see it as such a huge advantage, even the fabled crabe morph
  68. Klon - just keeping the zeus and making more often enough is better
  69. GoogleFrog - no it's not
  70. GoogleFrog - and I am not saying that morph was always a good thing to do
  71. GoogleFrog - if your new unit would get countered like that easily then don't do it
  72. GoogleFrog - but there are situations (common ones) where it would not get countered easily and then it is good
  73. Klon - yeah but so could any other suprising unit or combo
  74. GoogleFrog - but as long as you realise you are designing for slippery slope and keep it in mind then some morph could be good to implement
  75. GoogleFrog - what?
  76. GoogleFrog - other surprising units or combos are either more expensive or impossible
  77. GoogleFrog - you can't move a warrior across the map that quickly
  78. GoogleFrog - crabe is more expensive to build from factory, 600 more metal and energy and about 2k more BP required
  79. Klon - well yeah, it wasnt specific to any particular morph, its just that getting suprised with something thats impossible to counter is part of the game
  80. GoogleFrog - except there are limits on what you can be surprised with
  81. GoogleFrog - you've got an idea of your opponents economy
  82. GoogleFrog - they can't dante drop you 5 minutes in
  83. Klon - well morph is pretty limited too, even more so, is just a bit of game knowledge thats needed, and people might not exspect it as readily as say a plane switch or something
  84. GoogleFrog - yea I agree there
  85. GoogleFrog - although another thing is that people can play factories such as hovercraft and not feel the lack of morphs
  86. Klon - there is scalpel-pene which was pretty strong
  87. GoogleFrog - oh that, perhaps
  88. GoogleFrog - I only did that when factories were still tierd
  89. Klon - the lack is felt with the things that cant morph anymore tho, because some things had been part of my regular play
  90. GoogleFrog - which?
  91. GoogleFrog - which things?
  92. Klon - think it was a reaper that i wanted to morph to a goli today
  93. Klon - dante - bantha was also something i would do sometimes
  94. GoogleFrog - I don't think Reaper needs that power
  95. GoogleFrog - the ability to absorb the exess metal you are reclaiming
  96. GoogleFrog - but I can see it being ok on Ravager
  97. GoogleFrog - same for Warrior -> Zeus
  98. Klon - it synergizes well with the overall idea of a reaper, because you generally keep them alive, so morphing them to the bigger tank is natural
  99. GoogleFrog - should it be fairly even between factories?
  100. GoogleFrog - Dagger -> Mace would just be brutal
  101. Klon - what do you mean? that all factories have about the same amount of morphs, with similar sizes and powers?
  102. GoogleFrog - Mace can already just barge into territory
  103. GoogleFrog - yes
  104. Klon - yeah dagger mace would be awesome
  105. GoogleFrog - it would win games
  106. Klon - i would think that all facs should have most of their units morph
  107. GoogleFrog - people already like to barge into territory with lone maces
  108. GoogleFrog - but they are speed limited
  109. GoogleFrog - dagger -> Mace would be massive slippery slope
  110. Klon - yeah that would really be a nasty one :D
  111. Klon - but then theres the risk that the enemy catches it while it morphs
  112. GoogleFrog - is there?
  113. Klon - sure
  114. GoogleFrog - what if you find a puddle?
  115. GoogleFrog - what if you defend it with your other few daggers?
  116. Klon - well if you find a puddle, i guess it might be safe
  117. GoogleFrog - daggers beat many raiders
  118. GoogleFrog - you effectively gain the ability to force them to attack your dagger ball
  119. Klon - if you have a number of daggers, enemy probably got some stuff too and mace morph isnt that strong anymore
  120. Klon - he wont be alone in his base with just an llt
  121. GoogleFrog - if you have daggers enemy may only have equal cost in dagger
  122. Klon - raiders can kill mace too if necessary
  123. GoogleFrog - and that doesn't beat daggers
  124. Klon - needs like 8 glaives, dont know about daggers
  125. GoogleFrog - certain raiders can kill a lone mace for cost
  126. GoogleFrog - well morph could take a lot longer
  127. Klon - a lot would be too much
  128. GoogleFrog - old morph could boost out units if you had the storage
  129. Klon - could be based on some formula tho, right now its tiered
  130. Klon - yeah its quite a lot of bp for some units, especially striders get a ton, but you can rarely supply the metal
  131. GoogleFrog - it was definately able to drain your entire economy
  132. Klon - yup
  133. GoogleFrog - that makes ordinary BP worse you know
  134. GoogleFrog - you can spend less metal on cons or send more cons to reclaim
  135. GoogleFrog - so being able to morph means you can spend less on your economy
  136. Klon - yeah but you can only use the bp for one thing
  137. GoogleFrog - perhaps it is the right thing
  138. GoogleFrog - perhaps the bonus is sufficient
  139. Klon - ?
  140. GoogleFrog - well not having exactly the right unit type is ok if you can spend more on it
  141. Klon - spending is seldomly an issue tho
  142. Klon - well it sometimes is, when you get a lot of reclaim, in which case morph is strong
  143. GoogleFrog - then maybe you have too many constructors and should have built units instead?
  144. Klon - but otherwise you mostly dont have too little bp, but too little metal
  145. Klon - idk, i guess most people have more bp than they can spend anyway, so they can reclaim when needed
  146. Klon - or build things when the reclaim comes in
  147. GoogleFrog - but if they plan on the a morph and know the game really well so they think they will get it then they should make less constructors
  148. GoogleFrog - that is a general problem with morph I have
  149. GoogleFrog - that now when nobody really knows what to do it is seen as an ok random feature
  150. Klon - if it works out that way which is a bit of a gamble
  151. GoogleFrog - but if you plan with it you probably get all this stupid stuff like farming
  152. GoogleFrog - raiding isn't really a gamble
  153. GoogleFrog - you'd do it anyway
  154. GoogleFrog - you might just do it in such a way (with high mircomangement) such that you get a morph out of it
  155. Klon - idk, if the hypothetical meta gamer tries to figure out if he should rather farm for xp and morph things or just steamroll the enemy, i think option number 2 wins
  156. GoogleFrog - I can invisage a 1v1 meta that requires you to be able to last hit with units to get the morphs
  157. GoogleFrog - imagine Daggers doing it
  158. Klon - that would suck, i agree, but im not sure it could ever develop to that point
  159. Klon - because after all you can just build a mace
  160. GoogleFrog - a mace that takes a minute to put preassure on your opponent's base
  161. Klon - and trying to last hit stuff will invariably lead to failure at times, and thus metal cost
  162. GoogleFrog - and what we have at the moment is just approximating the last-hit requirement meta
  163. Klon - maybe the last hit thing is op
  164. Klon - its a bit silly anyway if you think about it :D
  165. GoogleFrog - this "invariably lead to failures" is the type of thing that leads you to a starcraft clickfest
  166. Klon - well its not only the risk but also added time cost
  167. Klon - not only micro but actual game time rearranging units and so on
  168. GoogleFrog - time cost sounds like it can be minimised
  169. GoogleFrog - hold fire and settarget?
  170. Klon - hmm
  171. GoogleFrog - run 4 daggers by a mex and organise them such that the same one always gets the last hit?
  172. Klon - idk, it might be possible
  173. GoogleFrog - that would be no time cost as they are all in range for a fair period of time
  174. GoogleFrog - or say you are attacking a normal expansion
  175. Klon - as i said, maybe the xp formula should consider the damage done primarily
  176. Klon - last hit could be a bonus
  177. GoogleFrog - have your swarm of glaives kill the LLT then single one out and have it kill the mexes. That is a time cost but not major
  178. GoogleFrog - that is with a non-last hit system
  179. Klon - yeah i might do that, but it doesnt require terrible clickfest micro
  180. GoogleFrog - it is still a bunch of attention spent
  181. Klon - yup
  182. GoogleFrog - I think the formula is hardcoded into the engine
  183. GoogleFrog - you get some XP for damage and the same XP for killing
  184. Klon - hm
  185. Klon - still, i think thats ok, if somebody wants to do that he can
  186. GoogleFrog - I can imagine a gadget which removes the last hit bonus by giving negative XP when a unit kills another unit
  187. GoogleFrog - to counteract the bonus
  188. GoogleFrog - so how do you readd morph with this in mind?
  189. GoogleFrog - do you accept that a required skill for some level of play will be the ability to last-hit or at least give most of the damage dealt to a certain unit?
  190. Klon - im not sure this is what will happen because i dont consider morph to be that powerful overall
  191. Klon - i can imagine that it may give people a major edge at times where this series of events plays out as planned
  192. GoogleFrog - the thing is the tradeoffs are low
  193. Klon - but then there are a number of things that can go wrong, most of which arent in the players control
  194. GoogleFrog - you want to kill things and have your units survive
  195. Klon - well tradeoff is time, risk and attention
  196. GoogleFrog - so people would only need to modify their behaviour slightly and input a lot more micro to do the same overall goal while attempting to get units with the required XP
  197. GoogleFrog - attention is not so much a risk as a skill level limiter
  198. Klon - plus the question if its worth it, because you just get some unit in a potentially neat place
  199. Klon - i would say this would require some major testing to find out if there is any real advantage to be gleaned from this, but seeing that morph is around since ever, if it was that powerful, that may have already happened
  200. GoogleFrog - there is obviously an advantage
  201. GoogleFrog - as in, being able to morph gives you more options so that is an advantage
  202. GoogleFrog - the advantage of one of these early game raider morphs would be the time spent moving an expensive unit across the map and the delayed constructor
  203. GoogleFrog - as in early game you need a constructor to assist your factory at some point, morph lets you delay this and focus on expanding
  204. Klon - huh
  205. Klon - how?
  206. GoogleFrog - because with morph you can spend more on units without tieing up a constructor assisting your factory
  207. Klon - anyway my point before was that if the advantage was that big, it probably would have found its way into the meta already, it probably isnt that great, which also means that it could be balanced by small steps later on if it would develop to a problem
  208. GoogleFrog - it did
  209. GoogleFrog - before Redback Godde would farm xp on fleas to get glaives and warriors
  210. Klon - ok
  211. Klon - well but thats more of a problem with the spider fac design :D
  212. GoogleFrog - it can work around it
  213. GoogleFrog - the factory can work in spite of the raider weakness
  214. Klon - ok
  215. GoogleFrog - that is the point of having distinct factories
  216. GoogleFrog - Zeus -> Crabe seems to be a good idea most of the time
  217. GoogleFrog - it's an accepted thing
  218. GoogleFrog - in the meta
  219. GoogleFrog - hover and amph lack morphs
  220. GoogleFrog - there are no air morphs
  221. Klon - hm
  222. GoogleFrog - shieldbot has fairly sparse morphs
  223. GoogleFrog - veh has a progression which is used
  224. GoogleFrog - a lone koda from a scorcher is quite powerful due to their different approaches to raiding
  225. Klon - well ok. the thing is, people arent really microing for last hit, or not much, which leads me to believe that the advantage of doing do wouldnt be so great
  226. GoogleFrog - people aren't skilled enough
  227. Klon - not so great as to make it mandatory in competetive games
  228. Klon - could be
  229. GoogleFrog - they are definately not as skilled as they could be
  230. GoogleFrog - I don't think you can say that it can be balanced around
  231. GoogleFrog - as in the core of the XP morph system is the fact that units get XP and then morph for som bonus
  232. Klon - not some bonus but into another unit
  233. GoogleFrog - as in some bonus to the player
  234. GoogleFrog - potentially
  235. Klon - potentially
  236. GoogleFrog - they get a cheaper unit in a different location
  237. Klon - unless he morphed into something stupid
  238. GoogleFrog - as in when something has a broken core mechanic and you try to balance it what you are really doing is owling it
  239. Klon - well morph could be based on something else but xp, tho it seems the most logical thing aside from no requirement at all
  240. GoogleFrog - well apart from XP what else is there?
  241. Klon - tax, reclaim
  242. GoogleFrog - Also most people seem to require XP
  243. GoogleFrog - as in they want the coolness of playing pokemons with their units
  244. Klon - just a 10% on unit cost for free morphs for example, lets you morph stuff always anywhere, but costs more than facs (turns whole game around tho :) )
  245. GoogleFrog - if you're trying to make people happy then implementing a replacement which doesn't depend on XP would not work, I think
  246. Klon - well i wouldnt want to change anything, i dont think of it based on xp as beeing broken
  247. GoogleFrog - 10% of what?
  248. GoogleFrog - you couldn't make Glaive -> warrior cost 800 metal
  249. GoogleFrog - I think that would be an owling
  250. Klon - 10% of the target units cost as an example
  251. Klon - in addition to the difference, which is used now
  252. GoogleFrog - so glaive -> warrior cost 220-65 + 22?
  253. Klon - basically
  254. Klon - otherwise, it could use regular buildpower as a last resort, but that would be massive nerf
  255. GoogleFrog - would it be a nerf to the RPG aspect though?
  256. GoogleFrog - if it required BP you could still have your strider morphs
  257. GoogleFrog - but you wouldn't be able to do it behind enemy lines
  258. Klon - well strider morph behind enemy lines is not that common :)
  259. Klon - but yeah
  260. Klon - kinda defeats the point of morph a bit unless there are more options in that case, so there is an actual reason to do it if you have to pay for everything in the first place
  261. GoogleFrog - as in you could still have morphs but not the offensive kind
  262. GoogleFrog - you still get a unit away from a factory
  263. GoogleFrog - what is the point of morph?
  264. Klon - there is not one point i guess
  265. GoogleFrog - the point seems to be for cool RPG mechanics
  266. Klon - i guess so
  267. GoogleFrog - the fact that your economy gets a boost because you get free BP is just a side effect of the implementation
  268. Klon - but if its about getting rid of those you need to take a long, hard look at com morphes
  269. Klon - well true, but having your unit sit around as a nanoframe waiting to get upgraded is a bit weak with the current options
  270. GoogleFrog - I don't see anyone arguing for morph from the point of view that they like the ability to spend less on normal BP
  271. Klon - but the fact that the unit doesnt require any additonal input to do its thing is certainly important
  272. GoogleFrog - that is weird, is it really?
  273. Klon - i would say so? i mean the unit undergoes a metamorphosis, so it just sits there in its cocoon and at some point its done
  274. GoogleFrog - what if constructors had an "upgrade" command that they could use on units
  275. GoogleFrog - when started it becomes immobile and waits for the upgrade to finish
  276. GoogleFrog - this doesn't give the cocoon impression
  277. Klon - then it would be like building a unit at the front line, a bit like athena would do, and reclaiming some other unit you have, except you dont have to actually reclaim it
  278. GoogleFrog - reclaim is only 50% though
  279. Klon - yeah
  280. GoogleFrog - but the point is that the morph maintains the unit and rewards it for doing stuff well
  281. Klon - right
  282. GoogleFrog - as in the requirements for morph seems to be in psychology more than anything else
  283. Klon - its fun
  284. GoogleFrog - it was accidentally implemented as one of those addictive reward things on facebook games
  285. GoogleFrog - use unit well -> click buttons -> reward
  286. GoogleFrog - I think it would be cool to have something like the Glaive -> Warrior morph
  287. GoogleFrog - as in a unit designed as something which runs around rapidly in a light version but can beef up to be a slow powerful unit
  288. GoogleFrog - that sounds like an interesting mechanic for a raider to have
  289. Klon - sounds like starcraft
  290. GoogleFrog - but if you base it on XP it gets all these farming and micromanagment problems eventually
  291. GoogleFrog - baneling, lurker?
  292. Klon - idk i didnt play it much tbh
  293. Klon - i think the farming isnt not so much an issue because the bonus isnt big enough, and its situational on top of it
  294. Klon - you could incorporate it into a strategy to eventually morph, maybe you could then try to farm for it, but its not like you could just level up units that automatically get better doing so
  295. GoogleFrog - the thing is that as people get better the meta would get closer to a game where the farming is a problem
  296. Klon - well we are talking from the perspective that its already taken out, otherwise i would have said you can take it out when it becomes a problem
  297. GoogleFrog - that seems like a poor thing to do
  298. GoogleFrog - I really don't like that idea
  299. Klon - it would also be a very complicated process of finding out what to morph, when to morph, i am unsure there would ever develop a definite meta over morph
  300. GoogleFrog - that you leave in things which are going to be broken because they are not now
  301. GoogleFrog - it really doesn't sounds that complicated to me
  302. Klon - but youre based the assesment that its broken on the assumption that eventually a meta would develop that would be bag
  303. Klon - bad even
  304. Klon - its not obviously broken when such a meta doesnt exist yet, and you dont know if it really is worth farming for
  305. Klon - maybe it just plain isnt
  306. GoogleFrog - I already said. Morph is not some great tradeoff
  307. GoogleFrog - it rewards you for doing well independantly of whether you aim for it
  308. GoogleFrog - but you could game it to get the rewards faster
  309. GoogleFrog - that gaming is farming
  310. GoogleFrog - and it would mostly be an attention based thing
  311. Klon - also greatly impacted by unit choice
  312. Klon - and slows you down a good deal. even randy can only do so many things at a time
  313. Klon - i dont know if its worth it, randy for one could probably not very often morph units because he would just bludgeon people to death and rarely even make cost
  314. GoogleFrog - I don't think it is infeasible for people to manage
  315. GoogleFrog - remember if you get better at a game you are also able to do actions efficiently
  316. GoogleFrog - exactly
  317. GoogleFrog - if there is only one person as good as rAndy then they don't need to get these small advantages
  318. Klon - k maybe
  319. GoogleFrog - but if you consider many people that good then whether you farm a morph would be the game changer
  320. GoogleFrog - as in a warrior near your base is a pretty big threat and would take resources to counter
  321. Klon - could be
  322. Klon - but then why is it a problem? because it only impacts people that are that good
  323. Klon - hypothetically speaking, we dont even know if it would be worth it, even among even matched opponents
  324. GoogleFrog - I think it would be that worth it
  325. Klon - they most likely still have better things to do than to farm xp
  326. GoogleFrog - and if it only impact people who are that good it matters for scalability
  327. GoogleFrog - but there is also the fact that there is a cost for keeping morph in
  328. GoogleFrog - https://github.com/ZeroK-RTS/Zero-K/issues/165
  329. GoogleFrog - and that morph on a unit adds 2 buttons to the UI (the morph button and morph priority)
  330. Klon - the latter two dont seem so terrible to me
  331. Klon - idk about the bugs, second one seems to apply to comms as well, both look pretty grim, but surely there is some way to fix it?
  332. GoogleFrog - sure but someone has to do it
  333. GoogleFrog - immunity is not a problem for commmorphs because they have a fix already
  334. GoogleFrog - comms are not stunned during morph but other units are. this stun is simply an application of a large amount of emp which is removed at the end
  335. GoogleFrog - the resource generating bug was fixed
  336. Klon - hm
  337. GoogleFrog - also I would want improved UI
  338. GoogleFrog - a unit which is able to morph might have it's rank icon flash
  339. Klon - sure why not
  340. GoogleFrog - at least for several seconds after it gains the rank
  341. GoogleFrog - and it needs to be visible to enemies
  342. GoogleFrog - and perhaps the last hit bonus should be removed as well
  343. Klon - you could just make ranks visible on all known units
  344. Klon - if thats not too complicated, as in let a xp counter run for each team for all enemy units
  345. GoogleFrog - and then you have the issue of explaining this seperate economy system to new players
  346. GoogleFrog - the 1:1:1 system has an exception with morph
  347. Klon - 1:1:1?
  348. Klon - understood
  349. Klon - where is the exception?
  350. GoogleFrog - well there is no BP spent
  351. GoogleFrog - the morph speed is not regulateable or balanceable in the usual way
  352. Klon - its pretty straightforward tho, dont remember having any trouble figuring it out
  353. Klon - you could also, as a balance measure, have it build with a very low base bp and make it assistable
  354. GoogleFrog - which is more work
  355. Klon - so morphing in enemy bases is less powerful
  356. Klon - yeah
  357. GoogleFrog - but a balance lever for the base morph is morph time
  358. GoogleFrog - anyway so say you have the bugs fixed, rank flash + enemy rank and lasthit removal
  359. GoogleFrog - and you're going to implement morphs with the idea that high level play may involve some strats where you raid with the intention of morphing
  360. GoogleFrog - but deem that to be an ok thing
  361. GoogleFrog - then what do you implement as morphs?
  362. GoogleFrog - Glaive -> Warrior -> Zeus? I like the first one but Warrior -> Zeus sounds like your unit mix will eventually turn into pure zeus
  363. Klon - well most of those that exist are ok, otherwise we had discussed some guidelines like upgrade along role, same fac, etc
  364. GoogleFrog - maybe that is ok, it would mean you are not stuck with warriors
  365. GoogleFrog - Ravager -> Reaper -> Golly?
  366. Klon - ye
  367. Klon - sure that one is classic, dont see a reason why not
  368. GoogleFrog - what about dart and flea?
  369. GoogleFrog - and dirtbag
  370. Klon - flea -> infi
  371. GoogleFrog - such cheap units that killing almost anything is the 3x cost requirement
  372. Klon - flea -> roach would also be good fun
  373. GoogleFrog - but you have to kill something left alone by itself
  374. GoogleFrog - the flea would really be the farming factory
  375. Klon - well, how can you farm with fleas other than you already do? you try to kill anything without dying, and youre good to go
  376. GoogleFrog - the way to play against spiders would be the never let fleas kill anything
  377. GoogleFrog - so lone mexes, cons, power generators
  378. GoogleFrog - but is the current farming with fleas a good mechanic?
  379. Klon - that shouldnt happen too often anyway
  380. GoogleFrog - the current xp limit is set to 3x cost
  381. GoogleFrog - so a flea would need to kill 2 mexes
  382. GoogleFrog - or 1 constructor
  383. Klon - thats more of a question about if flea is a well designed unit i think
  384. GoogleFrog - but itself
  385. GoogleFrog - *by
  386. GoogleFrog - currently it scouts, kills lone things like arty and prevents naked expansion
  387. Klon - it also gets xp for shooting stuff, its pretty quick at gaining xp from anything really
  388. GoogleFrog - morph just punishes naked expansion more
  389. Klon - true
  390. Klon - well in this case
  391. GoogleFrog - and the cost difference is so massive
  392. GoogleFrog - from flea to almost anything
  393. GoogleFrog - I am unhappy with flea -> Glaive
  394. GoogleFrog - imo factories should at least retain their iconic raiders
  395. GoogleFrog - flea to infiltrator is actually sounding good
  396. Klon - flea infi seems fine from a style and role point of view, theyre both spies in essence
  397. GoogleFrog - then what else?
  398. GoogleFrog - ahh
  399. GoogleFrog - that is another thing about morph
  400. GoogleFrog - the way of assigning xp is so silly
  401. GoogleFrog - eg, wolverine cannot gain XP
  402. GoogleFrog - it doesn't actually do damage
  403. Klon - yeah
  404. GoogleFrog - Venom could gain XP really really slowly
  405. Klon - but racks could gain xp now right`?
  406. GoogleFrog - Raketerr - nope
  407. Klon - venom gets from ae damage?
  408. GoogleFrog - yes
  409. GoogleFrog - 20 or so damage
  410. GoogleFrog - but if you did gain XP from other types of damage venom would get so much
  411. GoogleFrog - just keep the unit stationary and farm it
  412. Klon - maybe just a fraction of emp damages? would make the most sense
  413. GoogleFrog - so the Venom -> Redback morph may as well never be added
  414. GoogleFrog - but a fraction of EMP damage would still let you keep the unit around forever for farming
  415. GoogleFrog - oh hey
  416. GoogleFrog - you know how you can repair your opponents units?
  417. Klon - but you want to do that anyway dont you? i mean there is no reason to constantly emp something if you can, even if its a solar
  418. Klon - nope
  419. GoogleFrog - well you can
  420. Klon - to not*
  421. GoogleFrog - exactly
  422. GoogleFrog - you want to constatly emp stuff already
  423. Klon - but this is what people do anyway
  424. GoogleFrog - farming tonnes of xp from doing so would be an added bonus
  425. Klon - right
  426. GoogleFrog - yes
  427. Klon - doesnt need to be tons, but yeah
  428. Klon - if it doesnt work for racks i guess it wouldnt be so much of a problem
  429. Klon - venoms need to expose themselves to do so
  430. GoogleFrog - racketeer would get XP constantly
  431. Klon - yeah racks would xp a lot
  432. Klon - and then morph to firewalkers for example
  433. GoogleFrog - and stuff with high DPS gets a lot of XP
  434. Klon - but then, maybe keep the racks, theyre so good
  435. GoogleFrog - as in felon probably gets a lot
  436. GoogleFrog - stuff like Halberd doesn't get much
  437. Klon - yeah
  438. GoogleFrog - because halberd is for tanking
  439. GoogleFrog - it's just that XP rewards units for dealing damage not taking it
  440. Klon - could keep that in mind and hand out special morphes for things that have a hard time getting xp
  441. GoogleFrog - so you've got a lopsided easyness to morph
  442. Klon - not every single unit has to be able to morph i guess
  443. GoogleFrog - the unusual factories are a bit sparse for morphs that make sense
  444. Klon - some units just are more supplementary than others
  445. GoogleFrog - does anything morph to Crabe? Hermit or Recluse are the things that would make sense
  446. GoogleFrog - that is still 1k metal though
  447. GoogleFrog - Hermit -> Recluse -> Crabe?
  448. GoogleFrog - that really does jump around the roles
  449. Klon - hermit -> jack
  450. GoogleFrog - that doesn't make much sense
  451. Klon - :P
  452. Klon - hermit is too small
  453. GoogleFrog - the thing is you could monospam some unit type and then get the support units you need via morph
  454. Klon - i mean it wouldnt be so tragic to remove some of the less popular morphes so in the end each factory has a select few options
  455. GoogleFrog - 1 or 2 per factory?
  456. Klon - yeah that would be possible, but that would need more inter role morphs than we had
  457. Klon - nah more like 3 to 4 imo
  458. GoogleFrog - that is a morph for half the units
  459. Klon - yeah
  460. GoogleFrog - you could predictably replace some constructor BP with morph
  461. Klon - morph doesnt actually build anything
  462. Klon - doesnt reclaim or repair either
  463. GoogleFrog - yes it does
  464. Klon - well kinda, but it needs an existing unit
  465. GoogleFrog - you spend money on armies
  466. Klon - ok
  467. GoogleFrog - spending some of that army money can go to increasing the expense of a single thing
  468. GoogleFrog - it can be equivelent
  469. Klon - but taking bp off cons would somewhat enforce people to use morph just to make up for it
  470. GoogleFrog - I mean they would be able to get away with making less constructors
  471. Klon - not really, they still need them to reclaim
  472. Klon - that would only work if morph was much better than it is
  473. Klon - so people could reliably use it in a meaningful way, right now you cant always morph to something sensible
  474. GoogleFrog - being better can simply be having more options
  475. Klon - hm
  476. GoogleFrog - but I guess the XP requirement can modulate the rarity
  477. GoogleFrog - except when people then intentionally farm it
  478. GoogleFrog - because if it were balanced for that it would be very rare of the "optional" level players
  479. Klon - i wouldnt fiddle with the cons just because morph gives some bp
  480. GoogleFrog - that is not what I said
  481. GoogleFrog - wait
  482. GoogleFrog - ambiguity
  483. GoogleFrog - I would not fiddle with the cons attributes because of a morph system
  484. GoogleFrog - but I can imagine players fiddling with their con production because they can morph for the BP
  485. GoogleFrog - that is why the nanoframe system sounds good
  486. Klon - its too situational to plan for it
  487. Klon - if you fail, youre in double trouble because you didnt make enough cons
  488. GoogleFrog - except when you hone your composition and tactics such that it isn't situational
  489. Klon - its still a gamble
  490. GoogleFrog - sure, many things are
  491. Klon - so maybe they would yeah, but then its not a problem is it
  492. GoogleFrog - so I'd want a list before I am convinced that it is worthwhile coding or fixing anything
  493. Klon - what kind of list
  494. GoogleFrog - because the normal way of coming up with morphs leads to weird stuff or cloakybot lopsidedness
  495. GoogleFrog - Recluse -> Crabe sounds good to me
  496. GoogleFrog - they sort of beat the same things (skirmishers)
  497. Klon - you mean a complete list of all morph options there shall be? i would do such a thing
  498. GoogleFrog - with good reasons
  499. Klon - good reasons for what?
  500. GoogleFrog - each of the morphs
  501. Klon - sounds feasible
  502. GoogleFrog - also morph is a system which softens your bad descisions
  503. GoogleFrog - as in if you make a poor mix then a morph can fix it
  504. GoogleFrog - you may be beaten by rockos because you made too many Hermits
  505. GoogleFrog - but if you can morph on of them you are ok
  506. Klon - and you dont want this to happen a lot
  507. GoogleFrog - while recluse may take too long to reach the front
  508. GoogleFrog - Glaive -> Warrior * Potential for raiding them Warrior morph. Could be an interesting tactic but has farming problems. Increases Warrior use.
  509. GoogleFrog - Warrior -> Zeus * Increases Warrior use because it allows for a transition to Zeus. Perhaps Warrior should be
  510. GoogleFrog - Ravager -> Reaper * Spearheading? Similar role.
  511. GoogleFrog - Reaper -> Goliath * Further spearheading. Beats other Reaper so could turn the tide of a Reaper war.
  512. GoogleFrog - Recluse -> Crabe * Both have range and beat similar thing (skirmishers). Crabe does a lot more though.
  513. Klon - hmhm
  514. GoogleFrog - I'm not so sure about complementary morphs
  515. GoogleFrog - as in Zeus -> Crabe was a perfect complementary morph because Crabe deals with those ligh skirmishers that outrange Zeus
  516. GoogleFrog - but ones that walk a bit around are nicer
  517. GoogleFrog - Warrior -> Zeus are still beaten by skirmishers
  518. GoogleFrog - also what of the untouched air?
  519. Klon - idk, does morph properly with fliers?
  520. GoogleFrog - there are only two fighters and by the cost ordering the only morph is Swift -> Hawk
  521. GoogleFrog - idk
  522. GoogleFrog - if you morph mid air they probably crash
  523. GoogleFrog - not sure
  524. GoogleFrog - maybe they float there
  525. Klon - avenger to vamp and vulture seems reasonble, bombers could morph into one another maybe
  526. Klon - phoenix-stiletto seems fitting
  527. GoogleFrog - double morphs seems like too much
  528. GoogleFrog - as in one thing morphing to two things
  529. GoogleFrog - say we have that glaive morph strategy with Scythe and Warrior
  530. Klon - why not? avenger is both fighter and scout
  531. Klon - plus is the cheapest unit in the fac, seems logical it has the most options
  532. GoogleFrog - you get raided, see that they gained enough XP and they retreat
  533. GoogleFrog - now you have to prepare for Scythe (make glaive) or Warrior (make some turrets or rocko)
  534. Klon - hm
  535. GoogleFrog - whereas if you know what they could do (say, only warrior) then it is easier to prepare
  536. GoogleFrog - and it reduces UI complexity
  537. GoogleFrog - on the other hand scouting the morph would then be important
  538. GoogleFrog - but also Scythe is fairly fast
  539. Klon - said situation wouldnt be a problem for the avenger morph tho, vulture is hardly a threat to prepare for :)
  540. GoogleFrog - and it seems a bit uneven when some units have no morphs
  541. GoogleFrog - I'd not have any morphs to vulture
  542. GoogleFrog - it is a support thing
  543. Klon - otherwise, ye i get the point, never seemed much of a problem, in that case taking out the warrior morph might be better tho since scythe is still a raider
  544. GoogleFrog - warrior sounds less annoying though
  545. GoogleFrog - and more counter-y
  546. Klon - ofc one could also consider to give each factory 2 morphs on their raider
  547. GoogleFrog - although scythe is fairly fast by itself
  548. GoogleFrog - so then when you get raided in this morph-raid strategy you also have to scout for which morph they are doing?
  549. GoogleFrog - which you should do given you have radar
  550. GoogleFrog - and if they go out of radar range the heavy takes longer to reach you
  551. GoogleFrog - so what of bandit, it has few things which make sense
  552. Klon - well i dont know if you really have to scout for it, since most people probably prefer keeping their raiders
  553. GoogleFrog - bandit -> Thug would be fairly nifty utility because you can hide under the shield
  554. Klon - but yeah i guess you would somehow have to deal with the different possibilities
  555. Klon - ye
  556. GoogleFrog - there are often two slightly more expensive and complementary units for raiders to morph to
  557. GoogleFrog - ravager, leveler. Warrior rocko, thug outlaw
  558. GoogleFrog - but that would be putting a lot on the mechanic
  559. GoogleFrog - I think it is better to leave them with one
  560. Klon - it happens too rarely to really be a problem for raiders
  561. Klon - imo
  562. GoogleFrog - raiders are high DPS and clash with things of similar weight early in the game
  563. GoogleFrog - and they get in and kill defenceless mexes and windgens
  564. Klon - i morphed a bunch of glaives to glaive or warrior sometimes, but cant say if it was worth it
  565. GoogleFrog - and it seems like the difference in situation is a bit too extreme
  566. Klon - yeah but theyre good at what they do already, unless you really need a riot you might just keep em
  567. GoogleFrog - as in if there is no morph availible to you then your opponent can relax
  568. GoogleFrog - but if you can morph they need to find out and prepare for any of two units which could come at them
  569. GoogleFrog - if the morph is only one unit type then at least they know what to expect, if anything
  570. GoogleFrog - a riot with your raiders is really good
  571. GoogleFrog - it gives you a retreat zone
  572. GoogleFrog - you can force conflicts with it instead of being stuck in standoff
  573. Klon - but enemy has a fac that can build some 8 kinds of units, which may come too - depending on unit it may take slightly more than 20 seconds for them to show
  574. GoogleFrog - it takes a long time for slow units to reach you
  575. GoogleFrog - even across something like red comet
  576. Klon - bit longer, guess at most a minute or so?
  577. GoogleFrog - a minute is a lot
  578. Klon - sure but the morph takes some time too, 20 for the small ones i think
  579. GoogleFrog - that is probably going to be 600 extra metal to defend with? more time to scout
  580. Klon - so its an advantage that you have to prepare for something, but its not like something couldnt just come anyway
  581. GoogleFrog - it also takes up a lot of space on the UI
  582. Klon - :D
  583. GoogleFrog - hey that is important
  584. Klon - why?
  585. GoogleFrog - the UI has to be understandable and usable
  586. Klon - its just 1 or 2 greyed out buttons
  587. GoogleFrog - what if you select 5 unit types?
  588. Klon - if you dont know what it does and its greyed out, you move on to something else
  589. GoogleFrog - it overflows
  590. Klon - hm
  591. Klon - never noticed that happening
  592. Klon - at most its like 4
  593. Klon - hm ok i just checked in game, it actually seemes to overflow even without morph buttons when you select a ton of units
  594. Klon - but thats not so much a problem of the morph buttons but the ui itself and the habit of displaying all options for all units no?
  595. GoogleFrog - so why increase the problem?
  596. Klon - is it a problem? does anyone want to select all his units and then do stuff in the menu?
  597. Klon - well maybe that does happen
  598. GoogleFrog - if you select a few units it could overflow if they all have a bunch of morphs
  599. Klon - probably happens a lot with builders and other types of units
  600. Klon - idk, scale buttons down? make some options disappear when many units are selected?
  601. GoogleFrog - that seems very disruptive
  602. Klon - gonna have to sleep now, its really late here :) so gnite
  603. GoogleFrog - ok
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement