الخميس، 23 مايو 2019

July Scrum Rnd2 - Madrak2 Vs. Baldur1


Last night I got my round two of the July Scrum league in vs. Jordan and he was kind enough to allow me to pause the clock between rounds to take a picture to write a detailed report.  I am extremely excited to be writing this match up because it was one of the best kinds of game: it swung wildly back and forth, with the game ending on Turn 7 with me at 40 seconds and Jordan at 30 seconds.  I'm very grateful to Jordan for the match and look forward to other matches in the future.

Jordan's Lists

Baldur1 Bones of Orboros
-Megalith
-Wold Guardian
-Woldwarden
-Woldwatcher
-Woldwyrd
-Woldwyrd

Stoneshaper
Stoneshaper
Stoneshaper
Blackclad Wayfarer
Sentry Stone & Mannikin
Shifting Stones
Celestial Fulcrum

Kaya2 - No Theme
-Laris
-Feral
-Gnarlhorn
-Warpwolf Stalker
-Argus
-Druid Wilder
Feralgeist
Lord fo the Feast
Reeves of Orboros (min)
Shifting Stones + Stone Keeper
Tharn Ravagers (min) + Chieftain

Matchup Analysis

So it's a Bones list and Kaya2 out of theme, my initial thoughts are "look at the stones on this guy!".  Trolls have always been a bit of a bad matchup for Circle in the game and it seems immediately obvious my drop is going to be Madrak2 and Jordan will be forced into Baldur1.  Simply put both of my lists can run over Kaya's list without breaking a sweat, particularly Grim2.  Conversely out of the two I'm probably better off with Madrak into Baldur.  This is exactly what happened, Jordan didn't even bring his Kaya list with him when he arrived to play our game.

For reference my Madrak2 list is:

Trollblood - Madrak2 Toughallo

Theme: Band of Heroes
3 / 3 Free Cards     74 / 75 Army

Madrak Ironhide, World Ender - WB: +28
-    Trollkin Runebearer - PC: 0
-    Dire Troll Mauler - PC: 15 (Battlegroup Points Used: 15)
-    Dire Troll Bomber - PC: 19 (Battlegroup Points Used: 13)

Fell Caller Hero - PC: 0
Fell Caller Hero - PC: 0
Eilish Garrity, the Occultist - PC: 5

Krielstone Bearer & Stone Scribes - Leader & 5 Grunts: 9
-    Stone Scribe Elder - PC: 3
Trollkin Long Riders - Leader & 4 Grunts: 20
Trollkin Long Riders - Leader & 4 Grunts: 20
Kriel Warriors - Leader & 9 Grunts: 11

Our Scenario was The Pit 2.

Deployment


I wont the roll off to go first and Jordan picked his table side. Since we both had an extra 2" of deployment we were starting off really close to each other.

My Turn 1


I respected the output of the Woldwyrds to murder Longriders with Blood Fury on them, so I simply dump all my Fury onto the stone and run forward, keeping everything except one Long Rider under the aura and sing for no continuous effects.

Jordan Turn 1



Since I had zero chill, Jordan was forced to feat turn 1.  This sees him kill a Longrider from my left flank with a Woldwyrd, Fulcrum, and Woldwatcher finally finishing it off and creating a forest out of its corpse. On the right flank Jordan takes some Geomancy shots at my Longriders doing minimal damage, but he makes a mistake by running the Manikins to jam before taking his shots with the Woldwyrd.  He misses my Longrider and kills his Manikin furthest to my right.

Of note - I forgot to deploy Eilish and Jordan was kind enough to allow me to put him at the back of my lines, so I had him hide in a trench.

My Turn 2


After some careful measurements, I am able to get one Longrider over the wall and into the Woldwyrd on my right flank and one Longrider can engage it over the wall - all without entering Baldur's control area.  Madrak puts Bloodfury on the right most Longriders and then fills the stone, sitting on 1 after a Harmonious Exaltation. I was careful to stay more than 2" from the forest, respecting Baldur's assassination.

The Fellcaller gets puppet master from Eilish and then activates (after the stone!) and sprays off one of the Manikins to clear my charge lane, and then sings Pathfinder on the Longriders (they were out of Baldurs feat). Luckily I do no damage to my Longrider.

I'm able to kill the right Woldwyrd with the Long Riders and while I am able to get a single rider to the Sentry stone, it leaves it on one box.

On the left flank I call pathfinder to allow the Longriders to shift left and I'm able to just toe my Bomber into Baldur's forest to see through to the other side to kill a Shifting stone. Jordan shield guards the first shot, but the second shot is able to kill a stone and take teleportation off the table.

Jordan's Turn 2


Jordan decided that murdering Trolls was his fucking job and it was time to go to work. The left Woldwyrd shifts right and shoots two Longriders off the table thanks to them having an upkeep on them. The Blackclad gets hunters mark on the unit and then Megalith and a Woldwarden decide to kill the other riders, with more than enough fury to Earth Spikes and knock down the right Fell Caller, then kill my Runbearer, with his crit knocking down Madrak, my left Fell Caller, and a Kriel Warrior.

Jordan uses his still alive Sentry Stone to make a Manikin who then sprays down part of my Krielstone. He then runs and Jams up my stuff with shifting stones and the Woldguardian has the +2STR/ARM spell on it (which I forget about).

To top it off he's also able to kill two more Longriders from my left flank with his Fulcrum and the Watcher, scoring 1 point.

Overall, I'm astonished I'm still able to sit comfortably as I write this after the ass beating Jordan laid down here. Suffice it to say I didn't at all expect to lose nearly that much. On the plus side, Jordan was not able to kill my objective and score more than 1 VP.

My Turn 3


My initial plan was to have the Longriders and Fell Caller kill the Woldwarden, the Mauler kills Megalith, and then the Bomber kills the Woldguardian. Simple, right? Turns out this was less simple and more of a "I'll try to do too much and as a result accomplish nothing for $500, Alex."

Since my Runebearer was dead, I should have noticed my plan was utterly doomed to failure since I couldn't upkeep Blood Fury and so would need to cast it and then two Rage's to properly achieve my goals. I similarly couldn't actually charge the Woldguardian and so would need Madrak's feat to et into him, burning 1 attack off the Bomber. I also forgot the Guardian had the +2 ARM spell.

Madrak stupidly goes first, sacrificed movement to stand, feats, then throws his axe to kill the Manikin in the Longriders way.  I put Bloodfury on the riders, and then Rage on the Bomber.

My left Fell Caller sacrificed action to stand and then walks 5" and calls to stand up the other Fell Caller.  Eilish gives that Fell Caller puppet master (another mistake, it should have gone on the Mauler). The Stone activates for +1 STR, and then the right Fell Caller charges into the Warden, doing decent damage and not even needing the Puppet Master.

The Longriders charge and impact attack and I kill it between two impact attacks and one charge attack, they Reposition out of the Maulers way.

The Mauler is dice off 2 from Megalith since he didn't have Rage and I decide the extra attacks are better.  I charge in, missing my second initial and losing the chain attack. I proceed to roll a bunch of 5's for damage and leave all of Megaliths systems up.  The Bomber similarly fails to do too much to the Woldguardian, though he kills two Stones for my trouble due to Feat.

On the bright side my Kriel Warriors with near zero buffs on them decide to charge in and utterly annihilate the Woldwatcher.

If I wasn't hell bent on making mistakes I would have Jammed up the Woldguardian with 2-3 Kriel Warriors and used the Bomber to possibly kill the objective and if I had enough Kriel Warriors left maybe I score a point by killing the Woldwatcher anyway.  Rage and Puppet Master goes on the Mauler who would then murder Megalith and then I'm way ahead on the piece trade and at least tying scenario.

Jordan Turn 3


If you remember Turn 2, you'll know that Fucking Murdering Trolls is Jordan's job description.  Megalith gets +2 STR from a Stonekeeper and walks to be able to kill the Mauler and hopefully kill the Objective.  Luckily for me he has to focus everything on killing the Mauler and isn't able to kill the Objective.  I pulled the 5 Fury off the Mauler when it dies.

The Sentry Stone spawns a new Manikin who then kills my right Fell Caller. The Woldguardian gets an additional +2 STR from another Stonekeeper and trivially murders my Bomber.

The Woldwyrd starts gunning down Longriders, but isn't able to kill them all. In fact he's only able to force a Tough on one rider, who gets charged and killed by a Blackclad who then Battle Wizards to kill some more of my Kriel Stone.

The only area where Jordan didn't completely meet his Troll Murder Quota was with the Fulcrum who only killed a few Kriel Warriors.  The other bit of good news is that no one scores anything on Scenario this turn, so I'm only down 0-1.

My Turn 4


This turn I finally decided that Sticks and Stones have broken enough of my bones and the best way to make them never hurt me again is to annihilate them.

Madrak upkeeps Bloodfury on the single Longrider.  The Fell Caller activates and puts +2 MAT on the Krielstone unit.  The Stone spends a fury for +1 STR and then declares a Charge/Run to kill the goddamn Blackclad who sprayed them down.

The Longrider has similarly had enough of the shit out of the Woldwyrd and Sentry Stone. I charge the Woldwyrd and am able to get impact attacks on both the Woldwyrd and the Sentry Stone. The Sentry Stone dies and I miss the Woldwyrd with my impact.  I roll like goddamn FIRE on the charge attack and leave it on like two boxes. Madrak activates, casts Blood Fury on the Kriel Warriors.

The Kriel Warriors decide to continue to be bosses, two charge the Stonkeeper and CMA to get a hit and kill him.  The others charge into the Woldguardian, and then rip it to shreds. I'm able to redirect a charge attack into the Woldwyrd, I hit, and then take the last points off.  As such I score the center zone.  Score is now tied, 1-1.

Jordan's Turn 4


Here is where things start going bad for Jordan.  He's only able to kill a few of the Kriel Warriors, notably failing to clear the left zone and score due to dice keeping one contesting Warrior alive.

He is able to kill my objective and clear the right zone, scoring two VP's here. He also sacrifices a Stonekeeper to prevent me from scoring the center.  Score is now 3-1 for Jordan.

My Turn 5


Madrak gets his two free Fury from the dead beasts and upkeeps Blood Fury on the Kriel Warriors.  The Stone activates and sings for +1 STR and I move the one model to contest the left zone. He misses the Stone Shaper.

Eilish gives Madrak Puppet Master.  Madrak activates, aims, and boosts to hit the Shaper, killing him and clearing the center zone.  The Kriel Warriors charge into the Fulcrum and carve off damage. The Fell Caller charges in, and fails to kill. The Long Rider has to charge in and is finally able to kill the Fulcrum.  I made a mistake in forgetting to reposition the Long Rider and turn him to face Jordan's models coming into the center zone.

Clock is getting low. Score is now 3-2, sill in favor of Jordan.

Jordan Turn 5

I forgot to take a picture here, though what occurred should be apparent in the next picture.

Megalith moves up and kills the contesting Stone model in melee, then Geomancies and kills my Stone Scribe Elder and the last grunt in the Stone unit, leaving only the Bearer itself. Jordan puts a forest up to block LOS to Megalith who is now contesting the center zone.  Jordan scores my left zone and the score is now 4-2 in favor of Jordan.

My Turn 6


Madrak gets his two fury and upkeeps Blood Fury on the Kriel Warriors.  The Warriors and Fell Caller charge the objective and kill it, with the two Kriel Warriors who couldn't get in taking position to contest the center zone. Madrak and the Stone run to the right zone and I make a critical error, I leave Madrak within 2" of the forest, forgetting about Baldur's threat.

I position the Fell Caller just outside of Megalith's 9" threat.

Eilish decides to sacrifice himself for the cause and contests the left zone. 

I score two points, tying the game 4-4.

Jordan's Turn 6


Jordan decides to go for the assassination I dutifully gave him.  Megalith moves up and then misses Madrak with his Geomancy.  Baldur doesn't upkeep the forest, casts it on himself, then teleports to within 2" of Madrak.  He's got 4 Fury.

He boosts to hit Madrak (3 Fury left) and hits, but I sacrifice it to the Stone, who suffers the Weight of Stone effect, and then decides to pass his Tough check. Baldur buy's the attack on the stone and kills it (2 Fury left).  He buys on Madrak again (1 Fury left), misses, and then he decides to camp his last Fury.

I score on Jordan's turn, bringing the game 5-4 in favor of me.

My Turn 7


Given that I'm under two minutes on clock, I decided to avoid the assassination and just play it safe. Fell Caller gives +2 MAT to the Kriel Warriors who charge into Baldur, one hits doing 8 damage. More importantly they get within 3" of Madrak who runs away from Baldur, taking the free strike and then killing the Kriel Warrior because Grim Salvation lets you sacrifice even free strikes.  I run to the other corner of the zone thinking there's no way Baldur can get to me and that's game.

What I should have realized was that he could teleport to me again and that to cement the game I could just surround Madrak with Kriel Warriors to really make sure I can't die, but I just try to put them in the way.

Still, I score yet another VP for the left zone and bring the score to 6-4, thinking I've won the game. I clock back to Jordan with only 40 seconds left on my clock. I didn't even activate the Longrider.

Jordan's Turn 7


Jordan decides to pull yet another Surprise Motherfucker! He teleports Baldur to Madrak and I think I've lost the game. Baldur is down to 4 Fury for this assassination run.

He boosts to hit Madrak and hits (3 Fury left). He rolls a 5 for damage, Madrak takes 2.  Jordan proceeds to buy his next three attacks and after everything is said and done his damage rolls are so poor that Madrak is left with 10 health when Baldur is out of fury and only 30 seconds left on his clock.  Jordan does run to contest, leaving the score 6-4 and I win by scenario at the end of turn 7.

Conclusions

This game was insane! I managed to survive two assassination runs, and while that's normally not very surprising with Madrak2, in these situations it is very surprising.  Dice saved my ass when I made two mistakes that gave Jordan two assassination runs I didn't have to give him.  I also was able to recover from a critical set of mistakes on Turn 3 on my part and the late game idea of weapon master Kriel Warriors really came through.


Clock was extremely tight and was definitely forcing us to move very quickly so that's definitely a factor towards the end of the game where possibly better decisions could have been made. Still, I won this game through a series of critical dice rolls: Jordan failing to kill a contesting Kriel Warrior on Turn 4 was massive, and then my passing the tough check on my Stonebearer on  his Turn 6 assassination run ate through enough of his fury to keep me alive.

Overall it was an incredible game, the kind that really makes you appreciate Warmachine.  I look forward to playing Jordan again.

My conclusions going forward is to take notice of exactly how fucking good higher model count lists are in scenario. I remember that from the last Scrum in 2017 and it seems just as true today.  Looking forward and knowing that I want to play Convergence, primarily in Destruction Initiative, I'm going to start having the kinds of large attrition swings in my games if I can't mitigate my opponents.  The model count and unit buff on the late game Kriel Warriors really saved me here.  I'm going to need to keep that in mind as I move forward.

الثلاثاء، 2 أبريل 2019

Episode 37: The Power Of Positive Larding Is LIVE!

Ep 37: The Power of Positive Larding

https://soundcloud.com/user-989538417/episode-37-the-power-of-positive-larding

Nick Skinner, Richard Clarke and I talk about What a Tanker and all things Lard.
Join the conversation at https://theveteranwargamer.blogspot.com, email theveteranwargamer@gmail.com, Twitter @veteranwargamer

Follow Nick @dozibugger and Richard @TooFatLardies on Twitter! The Too Fat Lardies Website Blog and Forum https://toofatlardies.co.uk/

What a Tanker Pre-Order
https://toofatlardies.co.uk/product/what-a-tanker-complete-advanced-order-bundle/

Sailor Malan's 10 Rules of Air Combat
http://ww2today.com/27th-august-1940-raf-ace-sailor-malans-ten-rules

YouTube Crack That Tank
https://www.youtube.com/watch?v=3PL2HFLRMI0

US Army professional wargaming https://www.army.mil/article/202457/cgsc_tests_board_based_strategy_game

S.L.A. Marshall Men Against Fire
https://www.amazon.com/Men-Against-Fire-Problem-Command/dp/0806132809

M40 105mm Recoilless Rifle
https://en.wikipedia.org/wiki/M40_recoilless_rifle

TFL Kriegsspiel
https://toofatlardies.co.uk/product-category/kriegsspiel/

US Army professional wargaming https://www.army.mil/article/202457/cgsc_tests_board_based_strategy_game

Music courtesy bensound.com. Recorded with zencastr.com. Edited with Audacity. Make your town beautiful; get a haircut.

Assassin's Creed Odyssey | Review, Trailer, Gameplay | Pro-GamersArena



Quick Facts :

  • Initial release date: 5 October 2018
  • Series: Assassin's Creed
  • Developer: Ubisoft Quebec
  • Platforms: PlayStation 4, Xbox One, Nintendo Switch, Microsoft Windows
  • Genres: Action role-playing game, Stealth game.


Assassin's Creed Odyssey is just about to release. The game trailer has a great deal of constructive responses from individuals. What's more, such a couple of days from the arrival of Assassin's Creed Odyssey, Ubisoft has discharged the official dispatch trailer for the activity RPG. For past trailers, Ubisoft either made two varieties to feature the amusement's two heroes - like the Gamescom realistic trailer or included the two characters in a single video. In any case, this time it's unique. 

For the release trailer, Ubisoft generally centered around Alexios and his development from a youthful youngster into an unbelievable Spartan warrior. The trailer flashes through the conceivable arrangements that you'll have the capacity to use to determine the contentions you'll look in Odyssey, for example, utilizing a bolt storm against moving toward watchmen or indicating sympathy towards somebody who's sincerely battling.


Like Assassin's Creed Origins, Odyssey dives into the most punctual clashes between the people that would in the end move both the Templar Order and Assassin Brotherhood. Be that as it may, without precedent for the establishment, you have the decision between two characters to play as, Alexios and Kassandra. Regardless of who you pick, you'll be given a similar generally story, exchange decisions, sentimental choices, and side journeys. 

What About The Gameplay?

Following a short cutscene you will be promptly requested to pick between two characters: Kassandra or Alexios, relatives of the scandalous Leonidas. Once your decision is made, you'll be dropped into 431 BCE. 




Here's the place your first taste of battle comes in. The center segments are to a great extent unaltered from Origins as you bolt onto foes and perform assaults utilizing the shoulder catches. Battle is available and genuinely lenient, albeit larger amount adversaries won't be reluctant to squander you in two or three hits (Not for my situation, 😜😜). 

The majority of encounters can be outperformed effortlessly. That is, insofar as you aren't imprudent. One of the principal moves you're educated is the repel. Accomplished by squeezing RB+LB, when utilized at the opportune time it leaves foes powerless against assault. I discovered this basic when managing which enemies whose watch wasn't effectively broken, which means I'd need to consider unheard of options to get a few slices in (where i mostly fail, 😝).


Avoiding is additionally vital, and doing as such seconds previously an assault results in a couple of valuable seconds of moderate movement, giving the ideal chance to strike. Everything feels astounding, regardless of whether early gear leaves a great deal to be wanted, doesn't make a difference around then. 



Dialogues are now a pervasive piece of Assassin's Creed, advising how you'll approach missions and connections all through Ancient Greece. This additionally stretches out to connections, with both Kassandra and Alexios ready to handbag sentimental undertakings of any gender. I worship this portrayal in such a blockbuster title, giving players a chance to be spoken to in a medium that is yet to really grasp inclusivity. 

It isn't nosy either, surfacing as discretionary discourse alternatives all through my few hours with Odyssey up until now. It's as yet vague to what expand picked exchange will affect the general plot or on the off chance that it'll just have a say in side missions, however even without this present it's as yet a long ways from the conventional structure past games received. Voice acting is tragically a blended pack outside of the primary cast, in spite of the fact that this could enhance sometime later. 


Ancient Greece is absurdly colossal. Comprised of many islands of changing sizes, you'll investigate the universe of Assassin's Creed by foot, steed and vessel. The last will be utilized to swap between island.


Trailer Impression :

I'll let you to decide this. Here's the trailer below, you can watch it and tell me in the comment box, what you think of it?



About Pre-Order :

You can pre-order Assassin's Creed Odyssey at best price from here. Just click on the Buy button.



الاثنين، 1 أبريل 2019

Battle Of Albuera 1811 - AAR


A big Napoleonic Game with bags of figures on an unfeasibly cramped table was the beginning of my gaming journey nearly 40 years ago and I am so glad to have that back in my locker.

A few months ago I posted a Scenario post for the battle, a combination of my holidays, shift work and illness meant that it took ages to finish, but with a permanent set up and a Yarkshire outlook, there's no need to rush lad.

https://yarkshiregamer.blogspot.com/2018/09/battle-of-albuera-1811-set-up.html


It was also the first real test of my Quarrie version of GdeB and it was a very positive experience, everyone got it straight away. After the game we all agreed they were the way forward and other than a couple of tweeks (some of which were rule based rather than National Characteristics (NC) based).

There were some anti NC comments on the previous post however I find them the most flexible way of representing troop types, for some reason some people can't get past the base stat line, it's a guide, if a particular regiment performed well increase the stats, if it's a Marie Louise battalion reduce them. A link to the original rules post is below.

https://yarkshiregamer.blogspot.com/2018/10/quarrie-to-general-de-brigade.html


Back to the battle itself, things started as you would expect with this battle with a French assault on the Alled right, specifically on the Spanish troops lining a number of hills. As per the scenario the French had 6 moves to "get on with it"

Vistula Legion Lancers make a hole in the Spanish Line
The French Cavalry didn't muck about and went straight at the Spanish Cavalry on the flank, it was no match and it wasn't long before the Spanish Brigade broke, first spoils to the French.

Godinots Brigade advance
In the meantime whilst the British and Portuguese were waiting for the signal to move out the French had redeployed Godinots Brigade to attack the Spanish above Albuera. The remaining French Infantry and Cavalry poured towards the hill line in one seemingly unstoppable wave.

Spanish Infantry open up on the approaching French
With the British troops only just waking up the first Infantry attack fell on the Spanish troops lining the hill. Ripples of musket fire went up and down the line as the French columns came on.

Recule
As you can see from the photo above and the abundance of Falter and Retreat markers the first blood fell to the Spanish who with a combination of steady fire power and poor French die rolling, saw off the initial assault of Godinots Brigade.



The troops of Gazan and Girand where coming into action whilst the French Cavalry continued to cause havoc on the allied right, The Vistula Legion Lancers tried to break the square of the Spanish Irlanda Regt, it was a close run thing but the square held.


After a brief lull the French renewed their attack on the Spanish, with the elite French Grenadier Battalion heading the charge the Spanish finally started to give way after a long hard fight. Brigades began to break and the resistance crumbled.


Coles Division had formed a defensive line with the Fusilier Battalions facing the oncoming French, this was fine whilst the Spanish held but as they left the field the flank of the Fusiliers was exposed. The Allied generals failed to deal with the position and left the flank exposed, leaving the British Cavalry unused on the hill at the rear of Albuera. This would prove their downfall.


Meanwhile the French and British Battalions clashed around the town, a couple of French units made gains but there wasn't enough support to push the advantage home.


The game ended when the French Grenadiers pushed home an attack on the flank of the Fusiliers, poor dice rolling saw the impacted battalion break and then a double 1 on the Brigade morale saw the flank collapse.

There were plenty of untouched British and Portuguese troops to allow an orderly withdrawal from the field but the day and the honours went to the French.

Below is a list of the casualties in our game, if a unit is not mentioned it suffered no losses, these casualties do not include routing troops.

French Casualties

Godinots Brigade
1/16 Legere 13 out of 28 figures = 260 men or 46%
2/16 Legere 16 out of 28 figures = 320 men or 57%
3/16 Legere 6 out of 28 figures = 120 men or 21%
1/51 Ligne 12 out of 36 figures = 240 men or 33%
2/51 Ligne 17 out of 36 figures = 340 men or 47%
3/51 Ligne 5 out of 36 figures = 100 men or 14% Routed
Grenadier Battalion 10 out of 48 figures = 200 men or 21%

Briche Cavalry
10th Hussars 7 out of 20 figures = 140 men or 35% Routed
21st Chasseur 4 out of 20 figures = 80 men or 20%


Brons Cavalry - No Casualties

Bouvier des Èclaits Cavalry
14th Dragoons 1 out of 16 figures = 20 men or 6%
17th Dragoons 1 out of 16 figures = 20 men or 6%

Unattached Cavalry
Vistula Legion Lancers 6 out of 28 figures = 120 men or 21%
27th Chasseur 1 out of 22 figures = 20 men or 5%

Girards Division
2/34 Ligne 3 out of 24 figures = 60 men or 12%
3/34 Ligne 1 out of 24 figures = 20 men or 4%
1/40 Ligne 4 out of 20 figures = 80 men or 20%
2/40 Ligne 1 out of 20 figures = 20 men or 5%

Gazans Division
2/21 Legere 13 out of 20 figures = 260 men or 65%

Werles Division
2/12 Legere 8 figures out of 36 figures = 160 men or 22%
3/12 Legere 4 figures out of 36 figures = 80 men or 11%
3/55 Ligne 2 figures out of 30 figures = 40 men or 7%

Total Casualties 2,700


Allied Casualties 

Colbornes Brigade
2/31st Foot 7 figures out of 21 = 140 men or 33%
2/48th Foot 1 figure out of 23 = 20 men or 4%
2/66th Foot 6 figures out of 22 = 120 men or 27%

Houghtons Brigade
29th Foot 6 figures out of 25 = 120 men or 24%
1/57th Foot 1 figure out of 32 = 20 men or 3%

Abercrombie Brigade
2/28th Foot 4 figures out of 26 = 80 men or 15%

Myers Brigade Broken Brigade
1/7 Fus 14 figures out of 36 = 280 men or 39% Routed 
2/7 Fus 1 figure out of 28 = 20 men or 4%
1/23 Fus 5 figures out of 37 = 100 men or 13%

Harvey's Portuguese Brigade
1/11 Line 1 figure out of 29 = 20 men or 3%
1/23 Line 1 figure out of 28 = 20 men or 4%


Hamilton's Portuguese Brigade
1/2 Line 3 figures out of 30 = 60 men or 10%
1/14 Line 1 figure out of 30 = 20 men or 3%

Blake's Spanish

Lardizabal Brigade
Canaris Foot 1 figure out of 24 = 20 men or 4%
2nd Leon Foot 4 figures out of 24 = 80 men or 17%

Ballasteros Brigade Broken Brigade 
Catalonia Foot 8 figures out of 20 = 160men or 40% Routed 
Pavia Foot 4 figures out of 20 = 80 men or 20%
Lena Foot 7 figures out of 20 = 140 men or 35% Routed 
Castropol Foot 8 figures out of 20 = 160 men or 40 % Routed
Inifiesto Foot 4 figures out of 20 = 80 men or 20%

Zayas Brigade Broken Brigade 
Spanish Guard 12 figures out of 30 = 240 men or 40%
Irlanda Foot 13 figures out of 30 = 260 men or 43% Routed 
Patria Foot 3 figures out of 30 = 60 men or 10%
Toledo Foot 1 figure out of 30 = 20 men or 3%
Esteramdura Foot 3 figures out of 30 = 60 men or 10%
Spanish Artillery 12 figures out of 12 = 240 men or 100%

Loys Spanish Cavalry Brigade Broken Brigade 
Castillo Hussar 5 figures out of 20 = 100 men or 25% Routed 
Granaberos Horse 6 figures out of 20 = 120 men or 30% Routed 

Penne Villemuir Spanish Cavalry Brigade Broken Brigade 
Reina Horse 7 figures out of 20 = 140 men or 35% Routed 

Total Casualties 2980 men

An excellent game, closely balanced and a good challenge for both sides, highly recommended, I will be looking at getting another big Napoleonic Game in soon but this time trying out the rule mods in a 1813 situation.


الجمعة، 29 مارس 2019

Top 15 Best URL Shortener to Earn Money 2019

  1. LINK.TL: LINK.TL is one of the best and highest URL shortener website.It pays up to $16 for every 1000 views.You just have to sign up for free.You can earn by shortening your long URL into short and you can paste that URL into your website, blogs or social media networking sites, like facebook, twitter, and google plus etc.
    One of the best thing about this site is its referral system.They offer 10% referral commission.You can withdraw your amount when it reaches $5.
    • Payout for 1000 views-$16
    • Minimum payout-$5
    • Referral commission-10%
    • Payout methods-Paypal, Payza, and Skrill
    • Payment time-daily basis

  2. Adf.ly: Adf.ly is the oldest and one of the most trusted URL Shortener Service for making money by shrinking your links. Adf.ly provides you an opportunity to earn up to $5 per 1000 views. However, the earnings depend upon the demographics of users who go on to click the shortened link by Adf.ly.
    It offers a very comprehensive reporting system for tracking the performance of your each shortened URL. The minimum payout is kept low, and it is $5. It pays on 10th of every month. You can receive your earnings via PayPal, Payza, or AlertPay. Adf.ly also runs a referral program wherein you can earn a flat 20% commission for each referral for a lifetime.
  3. Clk.sh: Clk.sh is a newly launched trusted link shortener network, it is a sister site of shrinkearn.com. I like ClkSh because it accepts multiple views from same visitors. If any one searching for Top and best url shortener service then i recommend this url shortener to our users. Clk.sh accepts advertisers and publishers from all over the world. It offers an opportunity to all its publishers to earn money and advertisers will get their targeted audience for cheapest rate. While writing ClkSh was offering up to $8 per 1000 visits and its minimum cpm rate is $1.4. Like Shrinkearn, Shorte.st url shorteners Clk.sh also offers some best features to all its users, including Good customer support, multiple views counting, decent cpm rates, good referral rate, multiple tools, quick payments etc. ClkSh offers 30% referral commission to its publishers. It uses 6 payment methods to all its users.
    • Payout for 1000 Views: Upto $8
    • Minimum Withdrawal: $5
    • Referral Commission: 30%
    • Payment Methods: PayPal, Payza, Skrill etc.
    • Payment Time: Daily

  4. Short.am: Short.am provides a big opportunity for earning money by shortening links. It is a rapidly growing URL Shortening Service. You simply need to sign up and start shrinking links. You can share the shortened links across the web, on your webpage, Twitter, Facebook, and more. Short.am provides detailed statistics and easy-to-use API.
    It even provides add-ons and plugins so that you can monetize your WordPress site. The minimum payout is $5 before you will be paid. It pays users via PayPal or Payoneer. It has the best market payout rates, offering unparalleled revenue. Short.am also run a referral program wherein you can earn 20% extra commission for life.
  5. Bc.vc: Bc.vc is another great URL Shortener Site. It provides you an opportunity to earn $4 to $10 per 1000 visits on your Shortened URL. The minimum withdrawal is $10, and the payment method used PayPal or Payoneer.
    Payments are made automatically on every seven days for earnings higher than $10.00. It also runs a referral system wherein the rate of referral earning is 10%.
    • The payout for 1000 views-$10
    • Minimum payout -$10
    • Referral commission-10%
    • Payment method -Paypal
    • Payment time-daily

  6. Linkbucks: Linkbucks is another best and one of the most popular sites for shortening URLs and earning money. It boasts of high Google Page Rank as well as very high Alexa rankings. Linkbucks is paying $0.5 to $7 per 1000 views, and it depends on country to country.
    The minimum payout is $10, and payment method is PayPal. It also provides the opportunity of referral earnings wherein you can earn 20% commission for a lifetime. Linkbucks runs advertising programs as well.
    • The payout for 1000 views-$3-9
    • Minimum payout-$10
    • Referral commission-20%
    • Payment options-PayPal,Payza,and Payoneer
    • Payment-on the daily basis

  7. Oke.io: Oke.io provides you an opportunity to earn money online by shortening URLs. Oke.io is a very friendly URL Shortener Service as it enables you to earn money by shortening and sharing URLs easily.
    Oke.io can pay you anywhere from $5 to $10 for your US, UK, and Canada visitors, whereas for the rest of the world the CPM will not be less than $2. You can sign up by using your email. The minimum payout is $5, and the payment is made via PayPal.
    • The payout for 1000 views-$7
    • Minimum payout-$5
    • Referral commission-20%
    • Payout options-PayPal, Payza, Bitcoin and Skrill
    • Payment time-daily

  8. Linkrex.net: Linkrex.net is one of the new URL shortener sites.You can trust it.It is paying and is a legit site.It offers high CPM rate.You can earn money by sing up to linkrex and shorten your URL link and paste it anywhere.You can paste it in your website or blog.You can paste it into social media networking sites like facebook, twitter or google plus etc.
    You will be paid whenever anyone will click on that shorten a link.You can earn more than $15 for 1000 views.You can withdraw your amount when it reaches $5.Another way of earning from this site is to refer other people.You can earn 25% as a referral commission.
    • The payout for 1000 views-$14
    • Minimum payout-$5
    • Referral commission-25%
    • Payment Options-Paypal,Bitcoin,Skrill and Paytm,etc
    • Payment time-daily

  9. Cut-win: Cut-win is a new URL shortener website.It is paying at the time and you can trust it.You just have to sign up for an account and then you can shorten your URL and put that URL anywhere.You can paste it into your site, blog or even social media networking sites.It pays high CPM rate.
    You can earn $10 for 1000 views.You can earn 22% commission through the referral system.The most important thing is that you can withdraw your amount when it reaches $1.
    • The payout for 1000 views-$10
    • Minimum payout-$1
    • Referral commission-22%
    • Payment methods-PayPal, Payza, Bitcoin, Skrill, Western Union and Moneygram etc.
    • Payment time-daily

  10. CPMlink: CPMlink is one of the most legit URL shortener sites.You can sign up for free.It works like other shortener sites.You just have to shorten your link and paste that link into the internet.When someone will click on your link.
    You will get some amount of that click.It pays around $5 for every 1000 views.They offer 10% commission as the referral program.You can withdraw your amount when it reaches $5.The payment is then sent to your PayPal, Payza or Skrill account daily after requesting it.
    • The payout for 1000 views-$5
    • Minimum payout-$5
    • Referral commission-10%
    • Payment methods-Paypal, Payza, and Skrill
    • Payment time-daily

  11. Ouo.io: Ouo.io is one of the fastest growing URL Shortener Service. Its pretty domain name is helpful in generating more clicks than other URL Shortener Services, and so you get a good opportunity for earning more money out of your shortened link. Ouo.io comes with several advanced features as well as customization options.
    With Ouo.io you can earn up to $8 per 1000 views. It also counts multiple views from same IP or person. With Ouo.io is becomes easy to earn money using its URL Shortener Service. The minimum payout is $5. Your earnings are automatically credited to your PayPal or Payoneer account on 1st or 15th of the month.
    • Payout for every 1000 views-$5
    • Minimum payout-$5
    • Referral commission-20%
    • Payout time-1st and 15th date of the month
    • Payout options-PayPal and Payza

  12. Shrinkearn.com: Shrinkearn.com is one of the best and most trusted sites from our 30 highest paying URL shortener list.It is also one of the old URL shortener sites.You just have to sign up in the shrinkearn.com website. Then you can shorten your URL and can put that URL to your website, blog or any other social networking sites.
    Whenever any visitor will click your shortener URL link you will get some amount for that click.The payout rates from Shrinkearn.com is very high.You can earn $20 for 1000 views.Visitor has to stay only for 5 seconds on the publisher site and then can click on skip button to go to the requesting site.
    • The payout for 1000 views- up to $20
    • Minimum payout-$1
    • Referral commission-25%
    • Payment methods-PayPal
    • Payment date-10th day of every month

  13. BIT-URL: It is a new URL shortener website.Its CPM rate is good.You can sign up for free and shorten your URL and that shortener URL can be paste on your websites, blogs or social media networking sites.bit-url.com pays $8.10 for 1000 views.
    You can withdraw your amount when it reaches $3.bit-url.com offers 20% commission for your referral link.Payment methods are PayPal, Payza, Payeer, and Flexy etc.
    • The payout for 1000 views-$8.10
    • Minimum payout-$3
    • Referral commission-20%
    • Payment methods- Paypal, Payza, and Payeer
    • Payment time-daily

  14. Wi.cr: Wi.cr is also one of the 30 highest paying URL sites.You can earn through shortening links.When someone will click on your link.You will be paid.They offer $7 for 1000 views.Minimum payout is $5.
    You can earn through its referral program.When someone will open the account through your link you will get 10% commission.Payment option is PayPal.
    • Payout for 1000 views-$7
    • Minimum payout-$5
    • Referral commission-10%
    • Payout method-Paypal
    • Payout time-daily

  15. Short.pe: Short.pe is one of the most trusted sites from our top 30 highest paying URL shorteners.It pays on time.intrusting thing is that same visitor can click on your shorten link multiple times.You can earn by sign up and shorten your long URL.You just have to paste that URL to somewhere.
    You can paste it into your website, blog, or social media networking sites.They offer $5 for every 1000 views.You can also earn 20% referral commission from this site.Their minimum payout amount is only $1.You can withdraw from Paypal, Payza, and Payoneer.
    • The payout for 1000 views-$5
    • Minimum payout-$1
    • Referral commission-20% for lifetime
    • Payment methods-Paypal, Payza, and Payoneer
    • Payment time-on daily basis

Introducing Android Q Beta

Posted by Dave Burke, VP of Engineering

In 2019, mobile innovation is stronger than ever, with new technologies from 5G to edge to edge displays and even foldable screens. Android is right at the center of this innovation cycle, and thanks to the broad ecosystem of partners across billions of devices, Android's helping push the boundaries of hardware and software bringing new experiences and capabilities to users.

As the mobile ecosystem evolves, Android is focused on helping users take advantage of the latest innovations, while making sure users' security and privacy are always a top priority. Building on top of efforts like Google Play Protect and runtime permissions, Android Q brings a number of additional privacy and security features for users, as well as enhancements for foldables, new APIs for connectivity, new media codecs and camera capabilities, NNAPI extensions, Vulkan 1.1 support, faster app startup, and more.

Today we're releasing Beta 1 of Android Q for early adopters and a preview SDK for developers. You can get started with Beta 1 today by enrolling any Pixel device (including the original Pixel and Pixel XL, which we've extended support for by popular demand!) Please let us know what you think! Read on for a taste of what's in Android Q, and we'll see you at Google I/O in May when we'll have even more to share.

Building on top of privacy protections in Android

Android was designed with security and privacy at the center. As Android has matured, we've added a wide range of features to protect users, like file-based encryption, OS controls requiring apps to request permission before accessing sensitive resources, locking down camera/mic background access, lockdown mode, encrypted backups, Google Play Protect (which scans over 50 billion apps a day to identify potentially harmful apps and remove them), and much more. In Android Q, we've made even more enhancements to protect our users. Many of these enhancements are part of our work in Project Strobe.

Giving users more control over location

With Android Q, the OS helps users have more control over when apps can get location. As in prior versions of the OS, apps can only get location once the app has asked you for permission, and you have granted it.

One thing that's particularly sensitive is apps' access to location while the app is not in use (in the background). Android Q enables users to give apps permission to see their location never, only when the app is in use (running), or all the time (when in the background).

For example, an app asking for a user's location for food delivery makes sense and the user may want to grant it the ability to do that. But since the app may not need location outside of when it's currently in use, the user may not want to grant that access. Android Q now offers this greater level of control. Read the developer guide for details on how to adapt your app for this new control. Look for more user-centric improvements to come in upcoming Betas. At the same time, our goal is to be very sensitive to always give developers as much notice and support as possible with these changes.

More privacy protections in Android Q

Beyond changes to location, we're making further updates to ensure transparency, give users control, and secure personal data.

In Android Q, the OS gives users even more control over apps, controlling access to shared files. Users will be able to control apps' access to the Photos and Videos or the Audio collections via new runtime permissions. For Downloads, apps must use the system file picker, which allows the user to decide which Download files the app can access. For developers, there are changes to how your apps can use shared areas on external storage. Make sure to read the Scoped Storage changes for details.

We've also seen that users (and developers!) get upset when an app unexpectedly jumps into the foreground and takes over focus. To reduce these interruptions, Android Q will prevent apps from launching an Activity while in the background. If your app is in the background and needs to get the user's attention quickly -- such as for incoming calls or alarms -- you can use a high-priority notification and provide a full-screen intent. See the documentation for more information.

We're limiting access to non-resettable device identifiers, including device IMEI, serial number, and similar identifiers. Read the best practices to help you choose the right identifiers for your use case, and see the details here. We're also randomizing the device's MAC address when connected to different Wi-Fi networks by default -- a setting that was optional in Android 9 Pie.

We are bringing these changes to you early, so you can have as much time as possible to prepare. We've also worked hard to provide developers detailed information up front, we recommend reviewing the detailed docs on the privacy changes and getting started with testing right away.

New ways to engage users

In Android Q, we're enabling new ways to bring users into your apps and streamlining the experience as they transition from other apps.

Foldables and innovative new screens

Foldable devices have opened up some innovative experiences and use-cases. To help your apps to take advantage of these and other large-screen devices, we've made a number of improvements in Android Q, including changes to onResume and onPause to support multi-resume and notify your app when it has focus. We've also changed how the resizeableActivity manifest attribute works, to help you manage how your app is displayed on foldable and large screens. To you get started building and testing on these new devices, we've been hard at work updating the Android Emulator to support multiple-display type switching -- more details coming soon!

Sharing shortcuts

When a user wants to share content like a photo with someone in another app, the process should be fast. In Android Q we're making this quicker and easier with Sharing Shortcuts, which let users jump directly into another app to share content. Developers can publish share targets that launch a specific activity in their apps with content attached, and these are shown to users in the share UI. Because they're published in advance, the share UI can load instantly when launched.

The Sharing Shortcuts mechanism is similar to how App Shortcuts works, so we've expanded the ShortcutInfo API to make the integration of both features easier. This new API is also supported in the new ShareTarget AndroidX library. This allows apps to use the new functionality, while allowing pre-Q devices to work using Direct Share. You can find an early sample app with source code here.

Settings Panels

You can now also show key system settings directly in the context of your app, through a new Settings Panel API, which takes advantage of the Slices feature that we introduced in Android 9 Pie.

A settings panel is a floating UI that you invoke from your app to show system settings that users might need, such as internet connectivity, NFC, and audio volume. For example, a browser could display a panel with connectivity settings like Airplane Mode, Wi-Fi (including nearby networks), and Mobile Data. There's no need to leave the app; users can manage settings as needed from the panel. To display a settings panel, just fire an intent with one of the new Settings.Panel actions.

Connectivity

In Android Q, we've extended what your apps can do with Android's connectivity stack and added new connectivity APIs.

Connectivity permissions, privacy, and security

Most of our APIs for scanning networks already require COARSE location permission, but in Android Q, for Bluetooth, Cellular and Wi-Fi, we're increasing the protection around those APIs by requiring the FINE location permission instead. If your app only needs to make peer-to-peer connections or suggest networks, check out the improved Wi-Fi APIs below -- they simplify connections and do not require location permission.

In addition to the randomized MAC addresses that Android Q provides when connected to different Wi-Fi networks, we're adding new Wi-Fi standard support, WPA3 and Enhanced Open, to improve security for home and work networks as well as open/public networks.

Improved peer-to-peer and internet connectivity

In Android Q we refactored the Wi-Fi stack to improve privacy and performance, but also to improve common use-cases like managing IoT devices and suggesting internet connections -- without requiring the location permission.

The network connection APIs make it easier to manage IoT devices over local Wi-Fi, for peer-to-peer functions like configuring, downloading, or printing. Apps initiate connection requests indirectly by specifying preferred SSIDs & BSSIDs as WiFiNetworkSpecifiers. The platform handles the Wi-Fi scanning itself and displays matching networks in a Wi-Fi Picker. When the user chooses, the platform sets up the connection automatically.

The network suggestion APIs let apps surface preferred Wi-Fi networks to the user for internet connectivity. Apps initiate connections indirectly by providing a ranked list of networks and credentials as WifiNetworkSuggestions. The platform will seamlessly connect based on past performance when in range of those networks.

Wi-Fi performance mode

You can now request adaptive Wi-Fi in Android Q by enabling high performance and low latency modes. These will be of great benefit where low latency is important to the user experience, such as real-time gaming, active voice calls, and similar use-cases.

To use the new performance modes, call WifiManager.WifiLock.createWifiLock() with WIFI_MODE_FULL_LOW_LATENCY or WIFI_MODE_FULL_HIGH_PERF. In these modes, the platform works with the device firmware to meet the requirement with lowest power consumption.

Camera, media, graphics

Dynamic depth format for photos

Many cameras on mobile devices can simulate narrow depth of field by blurring the foreground or background relative to the subject. They capture depth metadata for various points in the image and apply a static blur to the image, after which they discard the depth metadata.

Starting in Android Q, apps can request a Dynamic Depth image which consists of a JPEG, XMP metadata related to depth related elements, and a depth and confidence map embedded in the same file on devices that advertise support.

Requesting a JPEG + Dynamic Depth image makes it possible for you to offer specialized blurs and bokeh options in your app. You can even use the data to create 3D images or support AR photography use-cases in the future. We're making Dynamic Depth an open format for the ecosystem, and we're working with our device-maker partners to make it available across devices running Android Q and later.

With Dynamic Depth image you can offer specialized blurs and bokeh options in your app.

New audio and video codecs

Android Q introduces support for the open source video codec AV1. This allows media providers to stream high quality video content to Android devices using less bandwidth. In addition, Android Q supports audio encoding using Opus - a codec optimized for speech and music streaming, and HDR10+ for high dynamic range video on devices that support it.

The MediaCodecInfo API introduces an easier way to determine the video rendering capabilities of an Android device. For any given codec, you can obtain a list of supported sizes and frame rates using VideoCodecCapabilities.getSupportedPerformancePoints(). This allows you to pick the best quality video content to render on any given device.

Native MIDI API

For apps that perform their audio processing in C++, Android Q introduces a native MIDI API to communicate with MIDI devices through the NDK. This API allows MIDI data to be retrieved inside an audio callback using a non-blocking read, enabling low latency processing of MIDI messages. Give it a try with the sample app and source code here.

ANGLE on Vulkan

To enable more consistency for game and graphics developers, we are working towards a standard, updateable OpenGL driver for all devices built on Vulkan. In Android Q we're adding experimental support for ANGLE on top of Vulkan on Android devices. ANGLE is a graphics abstraction layer designed for high-performance OpenGL compatibility across implementations. Through ANGLE, the many apps and games using OpenGL ES can take advantage of the performance and stability of Vulkan and benefit from a consistent, vendor-independent implementation of ES on Android devices. In Android Q, we're planning to support OpenGL ES 2.0, with ES 3.0 next on our roadmap.

We'll expand the implementation with more OpenGL functionality, bug fixes, and performance optimizations. See the docs for details on the current ANGLE support in Android, how to use it, and our plans moving forward. You can start testing with our initial support by opting-in through developer options in Settings. Give it a try today!

Vulkan everywhere

We're continuing to expand the impact of Vulkan on Android, our implementation of the low-overhead, cross-platform API for high-performance 3D graphics. Our goal is to make Vulkan on Android a broadly supported and consistent developer API for graphics. We're working together with our device manufacturer partners to make Vulkan 1.1 a requirement on all 64-bit devices running Android Q and higher, and a recommendation for all 32-bit devices. Going forward, this will help provide a uniform high-performance graphics API for apps and games to use.

Neural Networks API 1.2

Since introducing the Neural Networks API (NNAPI) in 2017, we've continued to expand the number of operations supported and improve existing functionality. In Android Q, we've added 60 new ops including ARGMAX, ARGMIN, quantized LSTM, alongside a range of performance optimisations. This lays the foundation for accelerating a much greater range of models -- such as those for object detection and image segmentation. We are working with hardware vendors and popular machine learning frameworks such as TensorFlow to optimize and roll out support for NNAPI 1.2.

Strengthening Android's Foundations

ART performance

Android Q introduces several new improvements to the ART runtime which help apps start faster and consume less memory, without requiring any work from developers.

Since Android Nougat, ART has offered Profile Guided Optimization (PGO), which speeds app startup over time by identifying and precompiling frequently executed parts of your code. To help with initial app startup, Google Play is now delivering cloud-based profiles along with APKs. These are anonymized, aggregate ART profiles that let ART pre-compile parts of your app even before it's run, giving a significant jump-start to the overall optimization process. Cloud-based profiles benefit all apps and they're already available to devices running Android P and higher.

We're also continuing to make improvements in ART itself. For example, in Android Q we've optimized the Zygote process by starting your app's process earlier and moving it to a security container, so it's ready to launch immediately. We're storing more information in the app's heap image, such as classes, and using threading to load the image faster. We're also adding Generational Garbage Collection to ART's Concurrent Copying (CC) Garbage Collector. Generational CC is more efficient as it collects young-generation objects separately, incurring much lower cost as compared to full-heap GC, while still reclaiming a good amount of space. This makes garbage collection overall more efficient in terms of time and CPU, reducing jank and helping apps run better on lower-end devices.

Security for apps

BiometricPrompt is our unified authentication framework to support biometrics at a system level. In Android Q we're extending support for passive authentication methods such as face, and adding implicit and explicit authentication flows. In the explicit flow, the user must explicitly confirm the transaction in the TEE during the authentication. The implicit flow is designed for a lighter-weight alternative for transactions with passive authentication. We've also improved the fallback for device credentials when needed.

Android Q adds support for TLS 1.3, a major revision to the TLS standard that includes performance benefits and enhanced security. Our benchmarks indicate that secure connections can be established as much as 40% faster with TLS 1.3 compared to TLS 1.2. TLS 1.3 is enabled by default for all TLS connections. See the docs for details.

Compatibility through public APIs

Another thing we all care about is ensuring that apps run smoothly as the OS changes and evolves. Apps using non-SDK APIs risk crashes for users and emergency rollouts for developers. In Android Q we're continuing our long-term effort begun in Android P to move apps toward only using public APIs. We know that moving your app away from non-SDK APIs will take time, so we're giving you advance notice.

In Android Q we're restricting access to more non-SDK interfaces and asking you to use the public equivalents instead. To help you make the transition and prevent your apps from breaking, we're enabling the restrictions only when your app is targeting Android Q. We'll continue adding public alternative APIs based on your requests; in cases where there is no public API that meets your use case, please let us know.

It's important to test your apps for uses of non-SDK interfaces. We recommend using the StrictMode method detectNonSdkApiUsage() to warn when your app accesses non-SDK APIs via reflection or JNI. Even if the APIs are exempted (grey-listed) at this time, it's best to plan for the future and eliminate their use to reduce compatibility issues. For more details on the restrictions in Android Q, see the developer guide.

Modern Android

We're expanding our efforts to have all apps take full advantage of the security and performance features in the latest version of Android. Later this year, Google Play will require you to set your app's targetSdkVersion to 28 (Android 9 Pie) in new apps and updates. In line with these changes, Android Q will warn users with a dialog when they first run an app that targets a platform earlier than API level 23 (Android Marshmallow). Here's a checklist of resources to help you migrate your app.

We're also moving the ecosystem toward readiness for 64-bit devices. Later this year, Google Play will require 64-bit support in all apps. If your app uses native SDKs or libraries, keep in mind that you'll need to provide 64-bit compliant versions of those SDKs or libraries. See the developer guide for details on how to get ready.

Get started with Android Q Beta

With important privacy features that are likely to affect your apps, we recommend getting started with testing right away. In particular, you'll want to enable and test with Android Q storage changes, new location permission states, restrictions on background app launch, and restrictions on device identifiers. See the privacy documentation for details.

To get started, just install your current app from Google Play onto a device or Android Virtual Device running Android Q Beta and work through the user flows. The app should run and look great, and handle the Android Q behavior changes for all apps properly. If you find issues, we recommend fixing them in the current app, without changing your targeting level. Take a look at the migration guide for steps and a recommended timeline.

Next, update your app's targetSdkVersion to 'Q' as soon as possible. This lets you test your app with all of the privacy and security features in Android Q, as well as any other behavior changes for apps targeting Q.

Explore the new features and APIs

When you're ready, dive into Android Q and learn about the new features and APIs you can use in your apps. Take a look at the API diff report, the Android Q Beta API reference, and developer guides as a starting point. Also, on the Android Q Beta developer site, you'll find release notes and support resources for reporting issues.

To build with Android Q, download the Android Q Beta SDK and tools into Android Studio 3.3 or higher, and follow these instructions to configure your environment. If you want the latest fixes for Android Q related changes, we recommend you use Android Studio 3.5 or higher.

How do I get Android Q Beta?

It's easy - you can enroll here to get Android Q Beta updates over-the-air, on any Pixel device (and this year we're supporting all three generations of Pixel -- Pixel 3, Pixel 2, and even the original Pixel!). Downloadable system images for those devices are also available. If you don't have a Pixel device, you can use the Android Emulator, and download the latest emulator system images via the SDK Manager in Android Studio.

We plan to update the preview system images and SDK regularly throughout the preview. We'll have more features to share as the Beta program moves forward.

As always, your feedback is critical, so please let us know what you think — the sooner we hear from you, the more of your feedback we can integrate. When you find issues, please report them here. We have separate hotlists for filing platform issues, app compatibility issues, and third-party SDK issues.