MephistoRoss

It was gone when battleforge was shut down in 2013. The good thing is that the game is completely free now, so you will be able to earn new cards by playing.

Wait what? How are the devs supposed to fix things in beta if people dont report issues during beta?

Both try to re-login please.

As long as you only make 'fair' trades and don't give everything to one account you are fine. Playing on each other's account is not allowed.

Could you try to redownload the client? Maybe on of the files got corrupted.

Could you try to redownload the client? Maybe one of your files is corrupted.

Good suggestion. Preferably with the option to assign one deck to multiple maps. @Ladadoos @John

Guns or lyr solo 22:59.5

You should view this bigger than just the bug Halis used. A lot of things might or might not change in the future, we just don't know atm. Maybe nothing will get changed. Maybe in the future amii monument will be nerfed, maybe decomposer will only be able to decompose own units, maybe treasure fleet will be fixed so you can't let wagons start leaving faster or maybe porting through gates will be stopped. All these things can have big impact on speedrunning of one or more maps which will never make anyone able to do new records. Halis bug is just one example that might or might not be changed in the future. I don't see why it should be treated any differently. Imo, the only way to deal with this and to still keep competition in the all-time rankings is to evaluate each patch to see what the impact is. If the impact affect speedrunning on several maps than the whole rankings should be archived and started all over. If it just impacts one map (because just the map got changed) just the rankings of that map should be archived and started over. With archived, I mean keep a frozen list of the (old) rankings which will never be changed again. So the best time at that point in time will still have credit. Of course it should also be mentioned until which date the rankings was active and what got changed for the rankings to become archived. In the past the bloodhorn stampede fix, the second chance fix and the furnace + embalmer fix would all have been examples of when the rankings should be archived and started over again.

I'm also still looking to form a team or become part of a team. My time to play the game is a bit unstable though, mostly just in weekends.

Interesting. I noticed in rpve that sometimes after killing a spawn building, a new wave would still spawn 1 or 2 seconds later. I never encountered this as the last building I killed though, but I am not surprised that the client crashed because the win condition is met and while the client is doing its final 'ticks' the win condition is not met anymore.

Please all calm down before this gets more out of hands and Ill have to lock this thread. So lets get back to topic: New record for Bad Harvest solo 25.24.1.

We havent discussed this. Please help me understand, why is it any different than killing a goldwagon in Treasure Fleet to let the next one leave faster? Or when everyone in RPvE used the second chance bug to get an almost instant t4 army? Using this bug also will let you finish way faster than any experienced player who doesnt use the bug. Speedrunners in all games always used these 'glitches' to finish a game really fast, so why would we treat them any different? https://en.wikipedia.org/wiki/Speedrun

The rule against bug abuse is intended for situations like when there was a bug in the AH where the seller would get the card (and the bfp) back instead of the buyer. There were some people actively abusing this bug to scam other players. The rule is not meant against ingame-bug-abuse for bugs that were also existing in the old 'EA' Battleforge. Like you mentioned yourself, there are already a lot of bugs that speedrunners use to complete maps and imo this is part of the speedrunning-game. So if it is an ingame-bug that was also possible in the old Battleforge, than it should be counted.

A disconnected player should still count as a player imo. So if 4 people start a map and two players disconnect, it should still be counted as 4 players (else it could be easy to cheat by letting others disconnect just before the end).