10 replies to this topic

[LeKrisser]

I want tp be able to take the Loadout from Smurfy and import it in a command line in the MWO Mechlab via Copy and Paste, where it is validated.

[Fut]

That would be handy.
MWO should have a fully functional Smurfy-Lab integrated into the Mech Lab.
One that allows you to build and save multiple loadouts for each of your Mechs - including the ability to simply click on one of these saved load-outs, and have your Mech instantly swap out parts for the ones in the new build (providing you have all the weapons/equipment...etc).

[mansquid]

Or even better, they simply adopt the smurfy code into the overall mechlab and utilize it, but UI 2.0 might require another 6 months of consulting with crytek as they try and debug the existing cavalcade of "features" they're attempting to introduce. Apparently the mantra of: It's broken,why fix it?

just like SRM hit registration, LB10xAC and the entirety of the shitty shitty ghost heat implementation.

[Troopie]

Import/export api would be nice.
Im just not sure with profile security...

[nonnex]

No. Rather I would like to see a ingame Mechlab that works similar to LiSong or Smurfy's in conjunction with a WebMechlab which is directly connected (but can also go without, just nice to have) to the Loadouts ingame on this Website. Plus the possibility to create and save different Loadouts (directly synched Web<->ingame) for a MechVariant for example SCR-D (Stock), SCR-D (PUG), SCR-D (League), SCR-D (Batchall). So I have just to mark one as "active" to change a loadout.

Posting and sharing loadouts on this website should also be possible of course.

I know thats a lot of wishes

Edited by nonnex, 28 August 2014 - 04:53 AM.

[Celtic Warrior]

great idea!

[ApolloKaras]

I just want to be able to SAVE a loadout....

[Ancient Demise]

As handy as this would be (and as good of an idea it is) it avoids / lets PGI avoid some of the underlying issues with UI "2.0".
Yes it would be a wonderful workaround but maybe they should fix the core problem to avoid the need of a workaround (and THEN add this feature).

[n r g]

LeKrisser, on 04 April 2014 - 11:44 AM, said:

I want tp be able to take the Loadout from Smurfy and import it in a command line in the MWO Mechlab via Copy and Paste, where it is validated.

Of course, good luck getting them to implement it though.

[nonnex]

It is not needed to say (and it has been said for 1000 times) that the ingame Mechlab needs more love to userbility. I'm sure the makers of the ML UI 1.0 and 2.0 had the best purposes while concepting, but had to much focus on the "look" without touching the "feel" (userbility).

Since it it much more easy to develop Web Frontends, we can use this as a playground till the most players are confortable with and migrate the concept to the ML ingame then.

How ever, a own PGI WebLab synched with the server data would be nice, basta!

Edited by nonnex, 03 September 2014 - 06:17 AM.

[Aidan Crenshaw]

well, we have https://mech.nav-alpha.com/
which is not maintained by PG, but grabs from the client data. You can also export build codes and import them in-client.