Forge Beta: 2-27-2015 ver 1.5.36
by mtgrares
Moderators: timmermac, Blacksmith, KrazyTheFox, Agetian, friarsol, CCGHQ Admins
Re: Forge Beta: 2-27-2015 ver 1.5.36
by pufthemajicdragon » 07 Mar 2015, 20:59
When I updated from 1.5.22 to 1.5.32, the way multikicker costs were paid was changed to include a pop-up that asks you to specify the kicker you'd like to pay before tapping the mana for it. Is this still the same in 1.5.36 or 1.5.37?
If so, I'm voicing my opinion that this new function is not an improvement. It makes paying a kicker cost horrendously difficult in any case where I'm paying more than just a handful of mana. In my green deck with 4 Elvish Archdruid and 4 Joraga Warcaller, it can be hard to know in advance how much mana I even have available to use. That's not even taking into account effects that reduce the casting cost of spells, making it even harder to know ahead of time how your mana will apply to casting a card with multikicker.
If there are people who prefer the new method, can I at least request that there be an option in preferences to switch to the old method of paying multikicker?
If so, I'm voicing my opinion that this new function is not an improvement. It makes paying a kicker cost horrendously difficult in any case where I'm paying more than just a handful of mana. In my green deck with 4 Elvish Archdruid and 4 Joraga Warcaller, it can be hard to know in advance how much mana I even have available to use. That's not even taking into account effects that reduce the casting cost of spells, making it even harder to know ahead of time how your mana will apply to casting a card with multikicker.
If there are people who prefer the new method, can I at least request that there be an option in preferences to switch to the old method of paying multikicker?
- pufthemajicdragon
- Posts: 23
- Joined: 08 Jan 2013, 04:17
- Has thanked: 7 times
- Been thanked: 2 times
Re: Forge Beta: 2-27-2015 ver 1.5.36
by drdev » 07 Mar 2015, 21:01
The problem with that old method is that it didn't work with the Auto button and it was buggy. That's why we switched to the new method. We now also use a similar dialog for X spells.pufthemajicdragon wrote:When I updated from 1.5.22 to 1.5.32, the way multikicker costs were paid was changed to include a pop-up that asks you to specify the kicker you'd like to pay before tapping the mana for it. Is this still the same in 1.5.36 or 1.5.37?
If so, I'm voicing my opinion that this new function is not an improvement. It makes paying a kicker cost horrendously difficult in any case where I'm paying more than just a handful of mana. In my green deck with 4 Elvish Archdruid and 4 Joraga Warcaller, it can be hard to know in advance how much mana I even have available to use. That's not even taking into account effects that reduce the casting cost of spells, making it even harder to know ahead of time how your mana will apply to casting a card with multikicker.
If there are people who prefer the new method, can I at least request that there be an option in preferences to switch to the old method of paying multikicker?
- drdev
- Programmer
- Posts: 1958
- Joined: 27 Jul 2013, 02:07
- Has thanked: 189 times
- Been thanked: 565 times
Re: Forge Beta: 2-27-2015 ver 1.5.36
by friarsol » 07 Mar 2015, 22:27
It also didn't work with cost reduction effects since the kicker values weren't locked in until after the cost was reduced
- friarsol
- Global Moderator
- Posts: 7593
- Joined: 15 May 2010, 04:20
- Has thanked: 243 times
- Been thanked: 965 times
Re: Forge Beta: 2-27-2015 ver 1.5.36
by saturnine » 08 Mar 2015, 04:36
Nope, didn't work. I've tried both the _C14 and that one now.Xitax wrote:Changing the name of the token to "c_stoneforged_blade" may fix it.
Re: Forge Beta: 2-27-2015 ver 1.5.36
by Xitax » 08 Mar 2015, 05:00
Ok, then the script needs a Tokenimage$ parameter. I submitted a scipt update recently - should be in next beta.saturnine wrote:Nope, didn't work. I've tried both the _C14 and that one now.Xitax wrote:Changing the name of the token to "c_stoneforged_blade" may fix it.
Re: Forge Beta: 2-27-2015 ver 1.5.36
by Mustanaamio » 08 Mar 2015, 11:56
Bug report:
My problem on late -09 macbook pro with Maverics is that I can not accept continue match if I win any achievement in one. Ie. the situation in quest mode duel is 1-1 then an achievement pops up. I can close the achievement window normally, but cannot continue the duel, since the 'Next match' button doesn't work. Same thing if I earn an achievement when winning/losing game.
My problem on late -09 macbook pro with Maverics is that I can not accept continue match if I win any achievement in one. Ie. the situation in quest mode duel is 1-1 then an achievement pops up. I can close the achievement window normally, but cannot continue the duel, since the 'Next match' button doesn't work. Same thing if I earn an achievement when winning/losing game.
- Mustanaamio
- Posts: 7
- Joined: 06 Mar 2013, 17:15
- Has thanked: 0 time
- Been thanked: 0 time
Re: Forge Beta: 2-27-2015 ver 1.5.36
by Mustanaamio » 08 Mar 2015, 19:14
Crash report (never did this before so don't know if this is the correct way):
Description: Played tournament in quest mode M12. After drafting got this crash.
Description: Played tournament in quest mode M12. After drafting got this crash.
- NullPointerException | Open
- Code: Select all
Forge Version: 1.5.31-r28300Mu (mixed revisions detected; please update from the root directory)
Operating System: Mac OS X 10.9.5 x86_64
Java Version: 1.8.0_40 Oracle Corporation
java.lang.NullPointerException
at forge.gui.CardDetailPanel.setCard(CardDetailPanel.java:181)
at forge.screens.match.controllers.CDetail.showCard(CDetail.java:53)
at forge.screens.match.controllers.CDetail.showCard(CDetail.java:48)
at forge.screens.match.controllers.CDetail.showCard(CDetail.java:67)
at forge.screens.deckeditor.CDeckEditorUI.setCard(CDeckEditorUI.java:70)
at forge.screens.deckeditor.CDeckEditorUI$8.valueChanged(CDeckEditorUI.java:258)
at forge.itemmanager.views.ItemView.onSelectionChange(ItemView.java:256)
at forge.itemmanager.views.ItemListView$ItemTableModel$1.valueChanged(ItemListView.java:571)
at javax.swing.DefaultListSelectionModel.fireValueChanged(DefaultListSelectionModel.java:184)
at javax.swing.DefaultListSelectionModel.fireValueChanged(DefaultListSelectionModel.java:164)
at javax.swing.DefaultListSelectionModel.fireValueChanged(DefaultListSelectionModel.java:211)
at javax.swing.DefaultListSelectionModel.changeSelection(DefaultListSelectionModel.java:405)
at javax.swing.DefaultListSelectionModel.changeSelection(DefaultListSelectionModel.java:415)
at javax.swing.DefaultListSelectionModel.addSelectionInterval(DefaultListSelectionModel.java:518)
at javax.swing.JTable.addRowSelectionInterval(JTable.java:2193)
at forge.itemmanager.views.ItemListView.onSetSelectedIndices(ItemListView.java:278)
at forge.itemmanager.views.ItemView.setSelectedItems(ItemView.java:194)
at forge.itemmanager.views.ItemView.setSelectedItems(ItemView.java:183)
at forge.itemmanager.views.ItemView.fixSelection(ItemView.java:149)
at forge.itemmanager.views.ItemView.refresh(ItemView.java:139)
at forge.itemmanager.views.ItemListView.setup(ItemListView.java:222)
at forge.itemmanager.ItemManager.setup(ItemManager.java:309)
at forge.itemmanager.ItemManager.setup(ItemManager.java:303)
at forge.screens.deckeditor.controllers.CEditorQuestLimited.update(CEditorQuestLimited.java:233)
at forge.screens.deckeditor.CDeckEditorUI.setCurrentEditorController(CDeckEditorUI.java:275)
at forge.screens.deckeditor.CDeckEditorUI.initialize(CDeckEditorUI.java:304)
at forge.control.FControl.setCurrentScreen(FControl.java:285)
at forge.control.FControl.setCurrentScreen(FControl.java:249)
at forge.view.FNavigationBar$NavigationTab$1.mousePressed(FNavigationBar.java:385)
at java.awt.Component.processMouseEvent(Component.java:6522)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3324)
at java.awt.Component.processEvent(Component.java:6290)
at java.awt.Container.processEvent(Container.java:2234)
at java.awt.Component.dispatchEventImpl(Component.java:4881)
at java.awt.Container.dispatchEventImpl(Container.java:2292)
at java.awt.Component.dispatchEvent(Component.java:4703)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4898)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4530)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4462)
at java.awt.Container.dispatchEventImpl(Container.java:2278)
at java.awt.Window.dispatchEventImpl(Window.java:2750)
at java.awt.Component.dispatchEvent(Component.java:4703)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:751)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:702)
at java.awt.EventQueue$3.run(EventQueue.java:696)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:75)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:86)
at java.awt.EventQueue$4.run(EventQueue.java:724)
at java.awt.EventQueue$4.run(EventQueue.java:722)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:75)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:721)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
- Mustanaamio
- Posts: 7
- Joined: 06 Mar 2013, 17:15
- Has thanked: 0 time
- Been thanked: 0 time
Re: Forge Beta: 2-27-2015 ver 1.5.36
by friarsol » 08 Mar 2015, 19:40
You seem to be on a very old version. Please take a look at the link in my signature and upgrade to the latest release.Mustanaamio wrote:Crash report (never did this before so don't know if this is the correct way):
Description: Played tournament in quest mode M12. After drafting got this crash.
- friarsol
- Global Moderator
- Posts: 7593
- Joined: 15 May 2010, 04:20
- Has thanked: 243 times
- Been thanked: 965 times
Re: Forge Beta: 2-27-2015 ver 1.5.36
by Marek14 » 08 Mar 2015, 21:45
I can't cast Avenger of Zendikar exiled through Psychic Intrusion.
Re: Forge Beta: 2-27-2015 ver 1.5.36
by Xitax » 08 Mar 2015, 22:16
.Nahiri, the Lithomancer: her +2 has a strange popup text "Do you want to attach Nahiri, the Lithomancer to Kor Soldier?" But it works correctly.
Last edited by Xitax on 08 Mar 2015, 22:20, edited 1 time in total.
Re: Forge Beta: 2-27-2015 ver 1.5.36
by Marek14 » 08 Mar 2015, 22:17
Mogg Infestation gave me tokens for my commander (who I put into command zone, so it didn't "die").
Re: Forge Beta: 2-27-2015 ver 1.5.36
by Rosieodonell » 09 Mar 2015, 04:00
Not sure if this was talked about yet but I was hoping to bump it to the front. Its making playing sealed games impossible. Let me know what information you need. cheers!Rosieodonell wrote:I am still getting the bug, where I play a sealed game (frf or even isddka) and if I mulligan the first card I have is black or is a manifest in my hand. Each time I mulligan the card doesn't change.
Kinda making it that you have to take the first hand you are dealt with or else. pretty poopy.
- Rosieodonell
- Posts: 66
- Joined: 11 Jun 2013, 04:26
- Has thanked: 2 times
- Been thanked: 10 times
Re: Forge Beta: 2-27-2015 ver 1.5.36
by nick012000 » 09 Mar 2015, 06:24
So, I've been playing on v.1.5.35, and I've been experiencing crashes after using Laboratory Maniac to win with this deck: http :// www (dot) starcitygames (dot) com/article/25582_Unveiling-Oops-All-Spells.html (I had to break the URL up because of your anti-spam filter getting twitchy). I get the "you won" screen, but the game freezes and I can't click the any of the buttons, and the tabs along the top bar grey out along with the "X" button to close the game. I have to open Task Manager and shut down the process to quit. I can't see anything about this bug being fixed in the new update, so I assume it's still broken in the new version?
- nick012000
- Posts: 5
- Joined: 21 Dec 2014, 22:20
- Has thanked: 0 time
- Been thanked: 0 time
Re: Forge Beta: 2-27-2015 ver 1.5.36
by friarsol » 09 Mar 2015, 12:11
That's never a safe assumption. Lots of bugs get fixed without being directly mentioned.nick012000 wrote:I can't see anything about this bug being fixed in the new update, so I assume it's still broken in the new version?
- friarsol
- Global Moderator
- Posts: 7593
- Joined: 15 May 2010, 04:20
- Has thanked: 243 times
- Been thanked: 965 times
Re: Forge Beta: 2-27-2015 ver 1.5.36
by Marek14 » 09 Mar 2015, 22:06
It seems that putting counters on permanents doesn't check whether the number of counters is nonnegative. I played Elesh Norn, Grand Cenobite and long story short, opponent's Murderous Redcap became 0/0, died, came back as -1/-1, died again, and actually REMOVED one +1/+1 counter from Kresh the Bloodbraided because AI put -1 counters on it.
Who is online
Users browsing this forum: No registered users and 108 guests