Author Topic: new MegaMek development & experimental releases 0.37.12  (Read 9925 times)

martian

  • Lieutenant Colonel
  • *
  • Posts: 8311
Re: new MegaMek development & experimental releases 0.37.12
« Reply #30 on: 25 June 2014, 09:36:52 »
I thought it was explicitly defined under the Behavior heading, but instead it's left implied in the description of the Replace Player command.  Basically, all you need to do is change the name of the Behavior before you click the Okay button.  That will save the behavior settings under that Behavior name in the princessBehaviors.xml file.  After that, when you use the replacePlayer command, you can give that Behavior name to have Princess use those settings.  It will also appear in the dropdown when you next open the dialog.
Okay, thank you. I think I understand.
1) So if I uncheck the Forced Withdrawal option, write martian in the "Behavior" window and Save it (to create a new profile),
I can use -c:martian the next time I kick out and then reload Princess?

2) There is one thing that confuses me: If I have unchecked the Forced Withdrawal and saved it (in the Default profile), why the reloaded Princess returned to "factory settings Default profile" and not to the "my/changed Default profile"?
Does that mean that there were two "Default profiles" with the same name - one original and one changed?

Netzilla

  • Warrant Officer
  • *
  • Posts: 590
    • Facebook
Re: new MegaMek development & experimental releases 0.37.12
« Reply #31 on: 25 June 2014, 10:01:50 »
Okay, thank you. I think I understand.
1) So if I uncheck the Forced Withdrawal option, write martian in the "Behavior" window and Save it (to create a new profile),
I can use -c:martian the next time I kick out and then reload Princess?

Yes.  It should also appear in the drop-down next time you start a new game.

Quote
2) There is one thing that confuses me: If I have unchecked the Forced Withdrawal and saved it (in the Default profile), why the reloaded Princess returned to "factory settings Default profile" and not to the "my/changed Default profile"?
Does that mean that there were two "Default profiles" with the same name - one original and one changed?

You can't have 2 behaviors with the same name.
"Everything starts as someone's daydream." -- Larry Niven

MM Bug & Feature Requests:
https://sourceforge.net/p/megamek/_list/tickets

MHQ Bug & Feature Requests:
https://sourceforge.net/p/mekhq/_list/tickets

martian

  • Lieutenant Colonel
  • *
  • Posts: 8311
Re: new MegaMek development & experimental releases 0.37.12
« Reply #32 on: 25 June 2014, 10:20:32 »
Yes.  It should also appear in the drop-down next time you start a new game.
It seems that it works. How can I delete a profile?

You can't have 2 behaviors with the same name.
But it seems to me that exactly this is happening.
I use the Default profile with Forced Withdrawal option disabled and saved, but when I kick the Princess and then reload her - with the Default profile -, the Princess starts following the Forced Withdrawal rule.

Netzilla

  • Warrant Officer
  • *
  • Posts: 590
    • Facebook
Re: new MegaMek development & experimental releases 0.37.12
« Reply #33 on: 25 June 2014, 10:40:01 »
It seems that it works. How can I delete a profile?
Right now, it needs to be manually deleted out of the princessBehaviors.xml file.  It's an oversight that needs to be corrected.

Quote
But it seems to me that exactly this is happening.
I use the Default profile with Forced Withdrawal option disabled and saved, but when I kick the Princess and then reload her - with the Default profile -, the Princess starts following the Forced Withdrawal rule.

Are you seeing two Default entries in the drop-down?  Do you see two Default entries in the princessBehaviors.xml file?  If the answer to both is no, then you don't have two Default configs.
"Everything starts as someone's daydream." -- Larry Niven

MM Bug & Feature Requests:
https://sourceforge.net/p/megamek/_list/tickets

MHQ Bug & Feature Requests:
https://sourceforge.net/p/mekhq/_list/tickets

martian

  • Lieutenant Colonel
  • *
  • Posts: 8311
Re: new MegaMek development & experimental releases 0.37.12
« Reply #34 on: 25 June 2014, 10:53:21 »
Right now, it needs to be manually deleted out of the princessBehaviors.xml file.  It's an oversight that needs to be corrected.
Good.

Are you seeing two Default entries in the drop-down?  Do you see two Default entries in the princessBehaviors.xml file?  If the answer to both is no, then you don't have two Default configs.
Then why Princess doesn't follow the Forced Withdrawal rule in the first part of the game and then (after being kicked and reloaded) starts to folow that rule, while using still the same Default profile?

scJazz

  • Captain
  • *
  • Posts: 1828
Re: new MegaMek development & experimental releases 0.37.12
« Reply #35 on: 25 June 2014, 12:08:23 »
Good.
Then why Princess doesn't follow the Forced Withdrawal rule in the first part of the game and then (after being kicked and reloaded) starts to folow that rule, while using still the same Default profile?
Because during the first session the change was made in memory. After the kick and launch Princess reads her Config file from the hard disk. Which still has the option checked.

Netzilla

  • Warrant Officer
  • *
  • Posts: 590
    • Facebook
Re: new MegaMek development & experimental releases 0.37.12
« Reply #36 on: 25 June 2014, 12:42:40 »
Then why Princess doesn't follow the Forced Withdrawal rule in the first part of the game and then (after being kicked and reloaded) starts to folow that rule, while using still the same Default profile?

First, did you get a popup message asking if you wanted to save your changes?  If you clicked Yes to that prompt, then the princessBehaviors.xml file should have gotten updated with your changes.  If you clicked No, then you'll play the current game with the configured options, but the changes won't be saved to the file.
"Everything starts as someone's daydream." -- Larry Niven

MM Bug & Feature Requests:
https://sourceforge.net/p/megamek/_list/tickets

MHQ Bug & Feature Requests:
https://sourceforge.net/p/mekhq/_list/tickets

martian

  • Lieutenant Colonel
  • *
  • Posts: 8311
Re: new MegaMek development & experimental releases 0.37.12
« Reply #37 on: 25 June 2014, 13:06:03 »
I have always clicked Yes.

Netzilla

  • Warrant Officer
  • *
  • Posts: 590
    • Facebook
Re: new MegaMek development & experimental releases 0.37.12
« Reply #38 on: 25 June 2014, 14:15:20 »
Then you should open up a bug ticket on the tracker (see my sig for the URL) and attach the log file and your princessBehaviors.xml file to the ticket.
"Everything starts as someone's daydream." -- Larry Niven

MM Bug & Feature Requests:
https://sourceforge.net/p/megamek/_list/tickets

MHQ Bug & Feature Requests:
https://sourceforge.net/p/mekhq/_list/tickets

Kovax

  • Captain
  • *
  • Posts: 2421
  • Taking over the Universe one mapsheet at a time
Re: new MegaMek development & experimental releases 0.37.12
« Reply #39 on: 27 June 2014, 08:34:51 »
The really sad part is, half of the reason for using Princess is to avoid the silly "fight to the death" behavior that "Forced Withdrawl" prevents.  Unfortunately, with Princess locking up fairly regularly* during forced withdrawls, I'm stuck using Testbot more often than not.

*Since I don't have the latest release, I'm assuming that it hasn't been fixed recently.

Netzilla

  • Warrant Officer
  • *
  • Posts: 590
    • Facebook
Re: new MegaMek development & experimental releases 0.37.12
« Reply #40 on: 27 June 2014, 12:26:02 »
It probably won't get fixed without a bug ticket being created with a log file attached.  Attaching a save game as well would be even better.
"Everything starts as someone's daydream." -- Larry Niven

MM Bug & Feature Requests:
https://sourceforge.net/p/megamek/_list/tickets

MHQ Bug & Feature Requests:
https://sourceforge.net/p/mekhq/_list/tickets

martian

  • Lieutenant Colonel
  • *
  • Posts: 8311
Re: new MegaMek development & experimental releases 0.37.12
« Reply #41 on: 29 June 2014, 15:07:04 »
Then you should open up a bug ticket on the tracker (see my sig for the URL) and attach the log file and your princessBehaviors.xml file to the ticket.
It probably won't get fixed without a bug ticket being created with a log file attached.  Attaching a save game as well would be even better.

Okay, bug report posted. But as it seems that with the bug report I can add only 1 attachment,
I am posting the gamelog, megamek log, PrincessBehaviors and saved game here:

princessBehaviors.xml
megameklog.txt
autosave.sav.gz
gamelog.html

scJazz

  • Captain
  • *
  • Posts: 1828
Re: new MegaMek development & experimental releases 0.37.12
« Reply #42 on: 29 June 2014, 18:10:42 »
Okay, bug report posted. But as it seems that with the bug report I can add only 1 attachment,
I am posting the gamelog, megamek log, PrincessBehaviors and saved game here:

princessBehaviors.xml
megameklog.txt
autosave.sav.gz
gamelog.html

Reference this post in the bug report on SourceForge.

arlith

  • BattleTech Volunteer
  • Warrant Officer
  • *
  • Posts: 698
Re: new MegaMek development & experimental releases 0.37.12
« Reply #43 on: 29 June 2014, 19:42:23 »
There is probably a "right" way to post multiple attachments on SF.  I do not know what that way is.  I have noticed that if you make a post with one attachment, then edit/modify the post you have the ability to make an additional attachment.  I assume this works more than once but I haven't tested it.  Another alternative is to compress all three files into one and post that.
Member of the MegaMek Team.

Netzilla

  • Warrant Officer
  • *
  • Posts: 590
    • Facebook
Re: new MegaMek development & experimental releases 0.37.12
« Reply #44 on: 05 July 2014, 10:36:38 »
Okay, bug report posted. But as it seems that with the bug report I can add only 1 attachment,
I am posting the gamelog, megamek log, PrincessBehaviors and saved game here:

princessBehaviors.xml
megameklog.txt
autosave.sav.gz
gamelog.html

Which player was Princess in this scenario?
"Everything starts as someone's daydream." -- Larry Niven

MM Bug & Feature Requests:
https://sourceforge.net/p/megamek/_list/tickets

MHQ Bug & Feature Requests:
https://sourceforge.net/p/mekhq/_list/tickets

martian

  • Lieutenant Colonel
  • *
  • Posts: 8311
Re: new MegaMek development & experimental releases 0.37.12
« Reply #45 on: 05 July 2014, 10:39:51 »
Which player was Princess in this scenario?
9th Lyran Guards

Netzilla

  • Warrant Officer
  • *
  • Posts: 590
    • Facebook
Re: new MegaMek development & experimental releases 0.37.12
« Reply #46 on: 05 July 2014, 12:29:29 »
The only unit on Princess's side in this game is a single ejected Mechwarrior. As they are not useful combat units, they always attempt to flee, no matter what the Forced Withdrawal setting is.

Can you reproduce this behavior with crippled combat units (mech, tank, etc)?
"Everything starts as someone's daydream." -- Larry Niven

MM Bug & Feature Requests:
https://sourceforge.net/p/megamek/_list/tickets

MHQ Bug & Feature Requests:
https://sourceforge.net/p/mekhq/_list/tickets

martian

  • Lieutenant Colonel
  • *
  • Posts: 8311
Re: new MegaMek development & experimental releases 0.37.12
« Reply #47 on: 05 July 2014, 12:43:14 »
The only unit on Princess's side in this game is a single ejected Mechwarrior. As they are not useful combat units, they always attempt to flee, no matter what the Forced Withdrawal setting is.

Can you reproduce this behavior with crippled combat units (mech, tank, etc)?
PrincessBehaviors shows that the ForcedWithdrawal is set to False and yet ...

Open that gamelog and find Round #18.
9th Lyran Guards: Archer ARC-6S (9th Lyran Guards) is crippled and withdrawing.

Movement Phase
-------------------

Archer ARC-6S (9th Lyran Guards) flees the battlefield.

Netzilla

  • Warrant Officer
  • *
  • Posts: 590
    • Facebook
Re: new MegaMek development & experimental releases 0.37.12
« Reply #48 on: 05 July 2014, 14:03:27 »
I can't play from round 18 when the game is already over.  I need to recreate this to be able to solve it.
"Everything starts as someone's daydream." -- Larry Niven

MM Bug & Feature Requests:
https://sourceforge.net/p/megamek/_list/tickets

MHQ Bug & Feature Requests:
https://sourceforge.net/p/mekhq/_list/tickets