|
Post by nemesis on Feb 23, 2019 17:36:14 GMT -6
I'd like to see repods be allowed.
(I'm actually ambivalent about this suggestion. On the one hand, it's nice to be able to use the units I want. On the other hand, it's nice to see some variety in what gets fielded.)
I know that unlimited repods end in cheese, so perhaps make pods allowed except for the problem variants. For example, if you have a Nova you can freely pod it to any version except S. If you want a Nova S you'll have to get lucky and pull it from a factory.
|
|
Cloudy
Free Worlds League
Posts: 23
|
Post by Cloudy on Feb 24, 2019 2:34:36 GMT -6
I like the idea. Also we could ( wanted to do that anyway) review cheeseclanners (black python and friends) and refit them into (still strong) but not cookiecutter op cheesecake.
|
|
|
Post by ironboot on Feb 25, 2019 17:01:02 GMT -6
So the way repoding works... it can either force random, take your pick or both. The server can control the cost in cbills down to the weight class (eg light, medium, heavy, assault), components, flu and time on the factory refresh. Since the server components is set to 1... you take that factor out. Flu means nothing on here. Cbills... well, units cost 1 cbill.
|
|
|
Post by Enochissac on Feb 27, 2019 11:25:43 GMT -6
Here is a middle ground allow repoding on C- Minus meks. Hellbringer, pouncers and strider, owen, BJ. And see how it goes. None of those variants are that scary.
|
|
Cloudy
Free Worlds League
Posts: 23
|
Post by Cloudy on Mar 2, 2019 6:15:03 GMT -6
I'd like to activate random podding and disabling certain pod options. That possible? And make repodding expensive.
|
|
|
Post by ironboot on Mar 4, 2019 13:23:23 GMT -6
Repoding cost is any combination of the following... FLU, Cbills, RP and components.
|
|
|
Post by Enochissac on Mar 6, 2019 0:52:44 GMT -6
RP is the most limiting factor.
|
|
|
Post by nemesis on Mar 8, 2019 10:05:52 GMT -6
I think I've figured out an easy solution.
1 - Turn repods on, and make them cheap or free.
2 - Edit the MTF files for problem units like the Nova S so that they're no longer omnis. This can be done with a text editor, just change the entry 'Config:Biped Omnimech' at the top of the MTF to 'Config:Biped'. This should make the S a completely separate mech that just happens to share a name with the other Novas.
3 - Only put the Prime variant of each omni on the build tables, since people can freely repod to the one they want. This also makes the build tables easier to manage.
4 - Add the Nova S to the build tables as its own entry. This could be with a low percentage or as a reward mech, it all depends on how rare you want them to be.
Now we just need to figure out what all of the problem variants are so they can get the same treatment. This would include problem non-omnis as well, which should also be rare pulls.
|
|
|
Repodding
Mar 8, 2019 10:51:48 GMT -6
via mobile
Post by spanish on Mar 8, 2019 10:51:48 GMT -6
Cheese alarm. One point of the metagame is to develop the build tables. Repodding would take out the viability of that option. I think I've figured out an easy solution. 1 - Turn repods on, and make them cheap or free. 2 - Edit the MTF files for problem units like the Nova S so that they're no longer omnis. This can be done with a text editor, just change the entry 'Config:Biped Omnimech' at the top of the MTF to 'Config:Biped'. This should make the S a completely separate mech that just happens to share a name with the other Novas. 3 - Only put the Prime variant of each omni on the build tables, since people can freely repod to the one they want. This also makes the build tables easier to manage. 4 - Add the Nova S to the build tables as its own entry. This could be with a low percentage or as a reward mech, it all depends on how rare you want them to be. Now we just need to figure out what all of the problem variants are so they can get the same treatment. This would include problem non-omnis as well, which should also be rare pulls.
|
|
|
Post by entengummitiger on Oct 6, 2019 16:39:31 GMT -6
I don't like it, but I'm willing to try
|
|
|
Post by stnden on Oct 11, 2019 10:34:29 GMT -6
My 2 cents mixed with some past experience; allowing repodding, even with an adjusted table keeping the cheesiest units off the list, will result in only the best unit of the repod list being fielded a vast majority of the time. The mini-campaign will help with this once an economy is established, as you will only be able to repod until you run out of resources. That being said if you want to see the non optimal omni variants get used not allowing repodding is the best way to achieve this.
|
|
|
Post by ironboot on Oct 23, 2019 17:48:31 GMT -6
Sven is working on buildtable 3.0.
I don't think repodding will be turned on. The meks are set for 1 cbill, Components are set for 1, Flu is cheap. The next thing would be random table or you pick from the table.
|
|