MekWars Operation Viewer

[Orca]

I've resisted Suggestions that required new code recently, as our coder resources are quite limited. However, I think this deserves at least discussion and an assessment of how hard it would be to implement.

Described: A new client menu item, "Help -> Operation Viewer" which would parse the available operations (would require method to refresh op data w/o excessive userlevel access) and display the enabled/configured values for the operation in an organized, human-readable manner.

Expectation: Greatly enhanced understanding of the Operations by the players, as well as a significant lessening of the learning curve for new players. Also probably much more informed and useful suggestions for Operations. Additionally, Operations descriptions in wiki/other docs would not have to be updated by hand each and every time an Operation was changed.

Reasons for Expectation: I'd think this would be self-evident. Being able to actually see and understand the limits/effects means less confusion. Having the documentation available in the client means more intuitive and useful access than having incomplete/stale information in a secondary or tertiary resource (forum, wiki etc).

Things that could go wrong: Could enable min/maxing in Operations. But it could also enable min/maxing opportunities, once identified, to be fixed.

How much it matters to me: As an admin player, not a lot - I have access to the raw data. As a non-admin player I'd think it would matter a lot, and as an admin I think it would increase the playability of any campaign.

[Tuco]

Supported, as it would be an auto-updating operation documentation. It would grab the operation parameters and make them readable while leaving out everything unused (or default setting, depending on what default really does).

[Bloodknight]

I think that is a good idea, and the thing that could go wrong "Could enable min/maxing in Operations." Isn't really an issue, IMO. Veteran players usually have most of the variables figured out relatively quickly and they'll minmax according to their knowledge anyway. If anything, it helps the casual players.

[BarukKhazad]

Since some operation values can be modified by the server parameters (such as payouts being modified by ELO), the server-side process should read in the CampaignConfig file along with the Operation files, then it can create a single xml file for distribution (the general consensus from chat in mod channel was that having the server create an xml for distribution would be better than having the data created on the client side).

[Anvilfolk]

As a newer player, I feel this could make quite a difference. Right now I haven't ventured past Mek or Vehicle Raids. A big part of that is that information on exactly what each operation does/requires isn't too readily available. Though I admit I haven't looked for it again since I got a few matches under my belt.

[Jackal]

I strongly support this idea. Even as an experienced player, I'm not always clear on the specs for certain missions (Overwatch? SuperOps?). Having an Ops viewer would eliminate a lot of confusion, asking around, etc.

[Padraig Tseng]

As an SO I would love this....

Sadly I have yet to win the lottery so I can hire Spork to just code MekWars full time....

[Spork]

Please fix that oversight, Paddy.

[motley_jester]

Is there a way/means for volunteering for this? I've a couple of weeks vacation and no relatives visiting this holiday, and this seems like a relatively easy way to help with code. Is there public and/or read-only SVN access? And/or a patch submission process?

I was going to throw together a perl script to auto write out wiki pages for Nastyogre as it was, might as well do it in game if possible.

[BeeRockxs]

Is there a way/means for volunteering for this? I've a couple of weeks vacation and no relatives visiting this holiday, and this seems like a relatively easy way to help with code. Is there public and/or read-only SVN access? And/or a patch submission process?

I was going to throw together a perl script to auto write out wiki pages for Nastyogre as it was, might as well do it in game if possible.

Here's the SVN repository:
svn://svn.code.sf.net/p/mekwars/code/trunk

Here's the patch tracker:
http://sourceforge.net/p/mekwars/patches/

[Nastyogre]

Is there a way/means for volunteering for this? I've a couple of weeks vacation and no relatives visiting this holiday, and this seems like a relatively easy way to help with code. Is there public and/or read-only SVN access? And/or a patch submission process?

I was going to throw together a perl script to auto write out wiki pages for Nastyogre as it was, might as well do it in game if possible.

Domenoth has something already. See what he has. Perhaps we can expand on it.
I would love to see one that showed all the options and settings, rather than just some.

[Kat]

I'd just like to add my support to this, as a new player. The learning curve CAN be very steep here.

[Spork]

Just as an FYI, this is in progress and nearing completion. I'll be looking for input on what fields should be viewable and which should not, and how to present them in a more user-friendly fashion than the OpEditor does.

[Orca]

Just as an FYI, this is in progress and nearing completion. I'll be looking for input on what fields should be viewable and which should not, and how to present them in a more user-friendly fashion than the OpEditor does.

Great news! Thanks Spork.

[Spork]

So, as any admin or op-designer knows, there is an absolutely bewildering array of options for Operations. I can't imagine that people would want *every* setting shown.

If you're not sure about that, download the opEditor (http://www.mekwars.org/files/MekWarsOpEditor.jar) and create an Operation.

Input, please. I've got xmls being created, requested, and transported to the user. I just need to figure out what to display.

[Nastyogre]

I will look tonight at the output of what domenoth made and see what I would suggest for additions or subtractions. I think that's a good starting point.

[Orca]

Ok, first the basics:

• Faction Limits
  Player Limits (XP, ELO etc.)
  Range
  Cost (Influence, CBills, RP)
  Minimum/Maximum units/types
  Max Army BV Spread

Then the more exotic stuff:

• Scenario Addons (artillery etc)
  Support unit settings
  Player Flags (yes I realize we're not currently using them)

Finally, Rewards (Meta and Player)

Probably not a complete list, but it should get us in the neighborhood.

[Tuco]

... grab the operation parameters and make them readable while leaving out everything unused (or default setting, depending on what default really does).

[Voidtraveler]

So I just downloaded the Ops Editor, and I have to say...wow. There is so much more than I expected, so many possibilities go unused. And I'm sure by that so many things to balance....yikes.

[Spork]

Committed

[Padraig Tseng]

That is awesome Spork!!! Very slick, very readable.