Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[sc0UT]

You can see some or all of these (depending on the boards) in action tonight at 19:00 UTC during my game against Stef.

Whatched it on Twitch and you struggled a bit with the positioning of the new buttons in the lower left corner in games with coin tokens. One solution for this is to move them to the upper left corner. There is much unused space except in games with 4 or more players. Then one doesn't need to change the window size or hide the buttons.

[jsh357]

Ran into (I assume) a bug. It seems some streams got crossed somehow here. After the Curses ran out, Torturer prompted me to trash Urchin even though I had the setting on, then the game froze. Free win for my opponent, I suppose.

http://i.imgur.com/BZ55YEE.jpg

I am also not fond of how the buttons cover the resign and trash buttons (in some games) but that's lesser.

[SCSN]

Thanks for the report. I managed to reproduce it and will release a fix later today.

If you want compensation for your loss I'd be happy to give you a free win either just before or just after my league match tonight (starting at 20:00 UTC).

[SCSN]

A bug fix for the client hanging when you play a Torturer with an Urchin in play after the Curses have run out is now available. It has replaced the old files so all previous links should work. A fix for the Mac version should appear soon.

[SCSN]

You can see some or all of these (depending on the boards) in action tonight at 19:00 UTC during my game against Stef.

Whatched it on Twitch and you struggled a bit with the positioning of the new buttons in the lower left corner in games with coin tokens. One solution for this is to move them to the upper left corner. There is much unused space except in games with 4 or more players. Then one doesn't need to change the window size or hide the buttons.

I agree with both you and jsh that the button placement is far from ideal, but I don't see an easy solution. I think in the same games where they now obscure coin tokens and the resign button, they would obscure the Province pile and some kingdom card(s) if you'd place them at the top.

One thing I'm considering is just moving the end actions/turn buttons a bit to the left (maybe only in games where they overlap other things?) and having just one settings button that would also cover autoplay and in the future blitz, and should thus be easier to place.

I'm very much open to other suggestions though.

[SCSN]

Bugfix for Mac is now available as well.

[sc0UT]

I agree with both you and jsh that the button placement is far from ideal, but I don't see an easy solution. I think in the same games where they now obscure coin tokens and the resign button, they would obscure the Province pile and some kingdom card(s) if you'd place them at the top.

No, they don't have to.

[Voltaire]

Doesn't work for 3/4 player games. That's where the other players would go.

[sc0UT]

Doesn't work for 3/4 player games. That's where the other players would go.

One solution for this is to move them to the upper left corner. There is much unused space except in games with 4 or more players.

I assume that most players who install MMF are active f.ds members and rarely play 4p (or more) games. But if they do, it's still possible to hide the buttons. In games with 3 players not a single avatar touches any new positioned button btw.

Maybe I'm wrong and multiplayer games are popular here. In this case and also if MMF shall be designed for multiplayer games, then you are totally right and my suggestion isn't worth it.

Another solution could be to place them next to the draw and discard pile. Do you think that's a problem with big hands?

[JW]

I agree with both you and jsh that the button placement is far from ideal, but I don't see an easy solution. I think in the same games where they now obscure coin tokens and the resign button, they would obscure the Province pile and some kingdom card(s) if you'd place them at the top.

Thanks again for the great work. I accidentally clicked the resign button and trash pile when I meant to click the End Actions/End Turn buttons in a kingdom that was very standard in terms of setup (Provinces, no coin tokens, no VP tokens), because they were on top of each other. I am not sure if the exact placement is impacted by the window size of the game (which took up almost the full screen).

As someone who never plays with >3 players, sc0UT's suggestion looks good.

[Chris is me]

Can the buttons go on the top of the log? It's where they were for Salvager and you can add some white space to the beginning of the log so that nothing is hidden. I guess the buttons need to keep existing when the log is not used.

[Fergesser]

Big thanks for this. The Autoplay options are adorable.

[SCSN]

Releasing MMF 0.45.29a for Windows. This version adds compatibility with Dominion Online 2.0.45.29 in addition to a bugfix. All other features are the same as in 0.44.2e.

The UI buttons will be moved in the future but it will take some more work.

[MdLC]

With the new release from Making Fun, my Linux install of Dominion is finally playable again (the last one crashed every time I tried playing a game). I can finally test and support the Linux version of MMF!

Barring unforeseen circumstances, MMF 0.45.29a for Linux will be released along with the Mac version soon.

[SCSN]

Thanks to MdLC again, MMF 0.45.29a is now available for OSX and Linux as well.

No special installation instructions apply for Linux. Just get the files into your Dominion_Data/Managed directory by whatever means necessary.

[SCSN]

Releasing MMF 0.45.29b for Windows. This version makes sure that the chat window is now, in the words of MF, "better placed". But this time for real:



Additional features include alternative button placement to avoid overlap with default GUI elements, resetting of autoplay settings at the beginning of each game, and autoplay for Curse discard against a Mountebank attack (optional, on by default).

One unfortunate side-effect of the new button placement is that the menus overlap with the kingdom, so if you're not careful you end up clicking on cards as well. The placement is not final and the old configuration is still available as an option, so for now this will have to do.

A supplementary tip: to avoid having to find the chatbar with your mouse, press [Tab] to select it and just start typing.

[Awaclus]

That's a crazy kingdom.

[SCSN]

Mac | Linux

[SCSN]

[Infthitbox]

I'd like to make an autoplay request: Don't trash Fool's Gold (not sure what the default should be).

[Dingan]

That's a crazy kingdom.

My thoughts exactly.

[SCSN]

I'd like to make an autoplay request: Don't trash Fool's Gold (not sure what the default should be).

I'll implement this with default off.

[sc0UT]

Ruins aren't colorized in the log. A shiny brown e.g. #a05000 can do it.

[ravi]

This is a bigger request and may not be possible but I'd love for the ability to decide which autoplays are opt-in and which are opt-out. Maybe you need a settings thing on the intro screen like Salvager had.

Another option may be to have the autoplay menu open up at the beginning of a game where there are autoplay options available so I am aware of them and just leave the defaults the way they are.

[SCSN]

Ruins aren't colorized in the log. A shiny brown e.g. #a05000 can do it.

Thanks. I'll probably pick something a bit darker and reserve this one for the Reserves, which are going to have to be brown as well.

This is a bigger request and may not be possible but I'd love for the ability to decide which autoplays are opt-in and which are opt-out. Maybe you need a settings thing on the intro screen like Salvager had.

A config file that stores your preferences (including autoplay defaults) between sessions and even between MMF releases is planned. Implementation will start once 0.45.29c is out. An optimistic ETA, to quote MF once more, would be "this year for sure".

Another option may be to have the autoplay menu open up at the beginning of a game where there are autoplay options available so I am aware of them and just leave the defaults the way they are.

I'll include this in the next release, and, if anyone would find this annoying (let me know!), an option to turn it off for the session as well (which once the config file is out would translate into turning it off indefinitely).