All RPGs and Storygames by Tod Foley are now available at DrivethruRPG. Bring these games to your table!
Starfarers Codex: Legacy Dragonrider is a book that simply provides rules for a character class that is focused on riding dragons. Have you ever been in a game where a player asked, 'Hey, can my character have a pet dragon to ride on?' Of course you have! It happens all the time in role-playing games set in fantasy settings--and this book actually provide some great rules that allow players to ride a dragon into combat that aren't game-breaking.
The dragon rider class presented in this book is a playable class just like any other in Starfinder. It high a high attack bonus and good reflex, will, and fortitude saves. The class gets a few spell-like abilities that choose from pre-existing class spell lists depending on the type of the dragon that the character rides. They also get some sensory abilities, such as low- light vision, darkvision, etc that progress with the character, as well as energy resistance tied to dragon type. The class is weak in a few spots: only being proficient with light armor and some limited weapons, and lacking any special abilities that are really useful in combat, aside from energy resistance. To make up for this, they do get to ride a dragon and have it fight by their side--with some limits.
Of course, when introducing dragons as a player option in a game in any capacity, there is the concern that they may be too powerful. The rules for this class are designed with that concern in mind, and they do a fairly good job of letting a player have a dragon in a way that won't break your game. Players selecting this class are allowed to pick their dragon's type, starting with a young dragon that grows in size and power as the character advances. There are stats for all of the standard chromatic dragons (black, blue, green, red, white), and metallic dragons (brass, bronze, copper, gold, silver), as well as outer dragons (lunar, solar, time, void, vortex). These dragons show up in the Starfinder Alien Archive books, though you don't need those books to use this character class. The dragons have been alerted from the standard monster stats to make them more balanced. Each dragon has different abilities that may include different move speeds, movement types (some can swim or burrow), different starting size (some dragons start off too small to ride), different attack damage, and breath weapon abilities. These rules are close enough to dragons as described in the Alien Archives, but nerfed enough to make them playable, though still some dragons are more powerful than others. To deal with the power discrepency between dragon types, this book adds a mechanic called 'mystic focus' that determines the character's ability to get the dragon to do what they want. The more powerful the dragon, the harder it is to control, and it requires more of the dragon rider's time each round to control it. If a character doesn't spend time each round controlling their dragon, it takes only move actions. Thus, if your character has one of the more powerful dragons, you will be able to do little else than direct it each round. At higher levels, mystic focus takes up less time each round, and it really brings balance to what might seem like an over-powered class, especially at lower levels.
Overall, this book presents some fantastic rules for allowing a player to have a dragon in your game. As a long-time game master, I've had many players wanting their character to have a dragon, and balanced rules for allowing this are very much welcomed and appreciated. The rules strike a good balance between allowing players to have something powerful, but at the same time restrict their use of it so as to not make it game-breaking. Starfarers Codex: Legacy Dragonrider does an amazing job of this, and I hope to see these rules adapted to similar fantasy games.
Read teh full review at [Geeksagogo.com!](https://www.geeksagogo.com/single-post/2019/04/26/Yes-You-Can-Have-a-Dragon--Review-of-Starfarers-Codex-Legacy-Dragon-Rider-for-Starfinder)
This month, we're running a membership campaign to grow our base of support and connect with more of the Drupal ecosystem. We're challenging you to take one step this month to brighten Drupal's future: invite your colleagues and clients to join the Association for Drupal's future.
By building a broader membership base, we're securing a financial future for supporting the Drupal community. A large, global base of members who contribute to sustain the Association are a force! Every member who participates is making an impact and a statement that Drupal is here to stay.Thank you for taking the time to share this campaign.
The campaign page is full of information on our work toward current goals that help fulfill our mission. If you are using Drupal or contributing to the project, there's some part of what we do that helps you and the community at large.
For a long time now, I’ve preferred Vagrant for local development. My starting point of choice for using Vagrant on a project has been the excellent trusty32-lamp VM, maintained by Andrew Berry. However, with Ubuntu 14.04 reaching end of life, Andrew thought to merge the best of trusty32-lamp VM with Laravel’s Homestead.
The term merge flag module allows users to merge taxonomy terms and have user flags merge with them
Add a permission to bypass all transition state restrictions and set content to any state on a given workflow.
DvG Authentication provides a complete set of modules to allow visitors to login using external authentication methods.
This module is designed for sites using the Drupal voor Gemeenten distribution. It replaces the dvg_digid and dvg_digid_autologout module in DvG.
Best used in combination with the webform module.
Support for the following authentication methods is included in this project:
The Entity Admin Handlers module provides an out-of-the box admin UI for custom entity types whose configuration means that the admin UI code in Drupal core doesn't fit.
This reduces the need for boilerplate code to provide a UI to manage fields on the entity type and its bundles.
The following cases are provided for.Single bundle entity type
This is for entity types that do not use bundles and in effect, have a single
bundle which typically has the same name as the entity type.
This is identical to the way the core user entity type works.
Sugar Aggregate connects to a SugarCRM instance, pulls down data about
all entries belonging to a specific SugarCRM module, and up to one
related (linked) SugarCRM module, aggregates that data into the
specified format, and saves it to a single node on the Drupal instance.
I am about to present about Drupal 9 at DrupalCamp Belarus in May and then at Drupal Developer Days Transylvania in June . I already presented an Acquia webinar with Dries Buytaert on the topic, and was on the Lullabot Podcast discussing Drupal 9 with Angie Byron and Nathaniel Catchpole. I am a firm believer that this know-how should spread as far and wide as possible. I should not be needed to travel around the globe to present the topic and people should not spend the same time again to redo slides for their local presentations. There is no intellectual property here to hide, as many people should be aware and excited and participating as possible. The topic should be presented at Drupal Meetups, Camps, and inside your own companies. So the natural next step for me was to create an open source slideshow.
I took all that we learned from the webinar and Dries' keynote at DrupalCon Seattle as well as new technology that emerged since then. I also used a free slide template and Google Slides so you can make a copy for yourself and add your own contact information as well as edit the slides down to shorter or longer timeslots. The 51 slides in my test run for about 35 minutes, leaving 10 minutes for discussion in a 45 minute slot. You would likely need to cut content for shorter sessions. There are only basic buildup animations, so if you need to present offline that is also an option. Edit in your contact/introduction info and export and present as PDF.
The 1.0 version of the slides have been presented by Christian Fritsch at DrupalCamp Munich last week and I updated some content to the current 1.1 version as it is available now. I'll keep updating slides based on all your feedback. I shared the slides with public comments allowed, so keep the feedback coming there, comments here or some other way you can get ahold of me.
Resources to watch/listen to learn more include:
- Dries' State of Drupal presentation from DrupalCon Seattle
- Lullabot Podcast on Drupal 9
- Acquia Webinar on Drupal 9
Thanks to Acquia for funding me to create this slideshow and thank you for presenting it!
Part of me is suspecting that I may be one of the lucky 10,000 today but I figure it's worth putting this out there because if I wasn't aware of this then there may be others too. It turns out that the version of Drush that you just installed may not be the version of Drush that executes your command.
So, as it happens there's a number of ways to install Drush. Older OSs may have it in the package management system, you may have just installed it globally using the instructions on the site, or, if your project is managed by composer it may have been installed as a site-local version. In my case I had messed it up just a little and had multiple versions hanging around and, despite having definitely downloaded and installed drush 8.2.3 to /usr/local/bin/drush and I confirmed that this was being called via which drush when I ran drush --version it informed me I was running version 9.6.2.
The thing that I didn't know... Drush will check the directory the site is in to see if there is a local-site version installed and pass off the request to that. So despite having Drush 8.2.3 installed and called from the command line the request was finding the local copy and returning results from that. If it wasn't for the fact that this was a Drupal 7 site and I'd inadvertently installed Drush 9.x locally via composer (Drush 9.x doesn't support Drupal 7.x) I'd never have known that this was how it worked.
Big thanks to Kirill for correcting my brain meat on this.Planet Drupal
Ubisoft andÂ Genba Digital have partnered on silent key activation, a more secure method of selling games through third-party stores that aims to prevent keys from popping up on unauthorized resellers. ...
If you have AWS CloudFront CDN setup in front of your web server then you can use this module to invalidate pages on CDN