Ducky on steroids v1 implementation instructions:
1: Become root in a linux environment:
sudo su
2: partition the card, destroying all data, /dev/sdb in this example, the blank lines are required:
fdisk /dev/sdb <<EOF
o
n



+100M
t
C
n




w
EOF
3: Format  and mount your root and boot partitions:
mkfs.ext4 /dev/sdb2
mkfs.vfat /dev/sdb1
mount /dev/sdb2 /mnt
mkdir /mnt/boot
mount /dev/sdb1 /mnt/boot
cd /mnt
4: Create the simlink so that bsdtar can extract the rootfs from the curl  stream
ln -s /dev/stdin /dev/st0
5: download and extract the arch linux arm rootfs image:
curl -L http://os.archlinuxarm.org/os/ArchLinuxARM-rpi-latest.tar.gz|bsdtar -xz
6: install qemu-user-static for binary translation and copy the static interpreter to the newly created rootfs for arch with the jenux repo, you can just do:
pacman -Sy qemu-user-static
cp /usr/bin/qemu-arm-static usr/bin
7: extract the included ducky.tar file, you can do it later, but why not do everything you can do outside the chroot first?
tar -xf /path/to/ducky.tar
8: chroot into your new arm system:
chroot /mnt /usr/bin/qemu-arm-static /bin/sh
rm /etc/resolv.conf
echo nameserver 1.1.1.1 > /etc/resolv.conf
mount -t proc /proc /proc
mount -t devtmpfs /dev /dev
mount -t sysfs /sys /sys
9: initialize the pacman keyring, the system will do this on reboot, but to save yourself the headache, why not do it with your system's local entropy?:
pacman-key --init
pacman-key --populate archlinuxarm
10: install two packages required by duckyd and its companions, why not update the system while you're at it?:
pacman -Syu zsh dosfstools
11:  enable duckyd to start on boot, also, add some needed config.txt and module settings for gadget support:
systemctl enable duckyd
echo dtoverlay=dwc2 >> /boot/config.txt
echo libcomposite >> /etc/modules-load.d/raspberrypi.conf
12: take out those psudo mounts:
umount /sys /proc /dev
13: exit the chroot:
exit
cd
14: unmount the card
umount /mnt/boot /mnt
15: pop the card into the pi, do I really need to provide instruction for this portion of the setup? 
16: apply power to the otg port, rather than the power port, it's the closest to the micro hdmi port, after around 45 seconds, a new mass storage device will be presented to your host with the fslabel "copypayload"
17: read! the readme.txt file on the drive
18: After placing your simulated keys  on the drive, unmount it and plug it into your target. Once the key sequence has been sent, the device reverts back to programming mode, awaiting a new payload.
Enjoy your USB Rubber Ducky on Steroids!
