Video Game Deep Cuts: Observing A Playdate With Some Cool Ghosts

Social/Online Games - Gamasutra - 24 May 2019 - 8:32pm

This week's roundup includes a look at AI thriller Observation, the unique new Panic handheld Playdate, and subjects including eSport shadiness, Oculus Quest, and Pathologic 2. ...

Categories: Game Theory & Design

Drupal blog: Drupal-powered sustains traffic surge from Mueller report post

Planet Drupal - 24 May 2019 - 3:47pm

This blog has been edited and reposted with permission from Dries.

On the day that the Drupal-powered website released Special Counsel Robert Mueller's long-awaited report on Russian interference in the U.S. election, the site experienced a 7,000% increase in traffic.

The report was successfully delivered without interruption via Acquia, using Drupal. 

According to Federal Computer Week, by 5pm on April 18, there had already been 587 million site visits, with 247 million happening in the first hour the report was released. The site typically receives 8 million visits per day. 

There were no IT performance or availability issues during the release of the 142-MB report, which is ideal during these types of high-pressure events when the world is watching. Thus, no news is good news. 

Keeping sites like this up and available to the public is an important part of democracy and the freedom of information. 

I'm proud of Drupal and Acquia’s ability to deliver when it matters most!

Categories: Drupal


New Drupal Modules - 24 May 2019 - 12:36pm

This module is an integration between the CKeditor spoiler plugin and the bower-assets installation of the libraries folder that holds js and css files needed to load the ckeditor plugin.

Categories: Drupal


New Drupal Modules - 24 May 2019 - 12:34pm
Categories: Drupal


New Drupal Modules - 24 May 2019 - 12:24pm
Categories: Drupal


New Drupal Modules - 24 May 2019 - 11:34am

This module will load a library into your theme that will let you know when the browser is supporting mouseover event.

Since the last 20 years had been assumed that all browser will have mouseover events, but with the not so late introduction to mobile devices and also computers with touchscreen this assumption causes undesired behaviors.

These are some of the issues you might experience:

  • Mobile Devices: When styles are added for :hover on links, this causes on mobile that the first touch (click), won't fire the desired action, it will instead activate the hover state of the link, and a second click will be needed to get the desired click behavior, this is solved by removing the CSS style :hover from the link, therefore the first click will result in the real click behavior.
  • Remove :hover only from Mobile Devices: There are some libraries that try to detect if the browser is using a Mobile devices, either by measuring width of the browser or by inspecting on Javascript the navigator.userAgent value, the problem with this, is that this would't work with existing known mobile devices, but as soon as a new browser or mobile device were to be promoted, this approach wouldn't work, also, this doesn't take into consideration, that you might use a Mouse connected through bluetooth, in which case, you would trigger "mouseover" events.
  • Rely on Width: Similar to the above approach, this doesn't take into account that you can actually resize your desktop browser width, neither you would have a way to predict all mobile devices width's.

The approach we use is to actually detect mouseover event, as soon as the user moves the mouse, class has-mouseover will be added to html tag.

Now, instead of adding styles to links as this:

a:hover{ text-decoration: underline; }

You would do it as:

html.has-mouseover a:hover{ text-decoration: underline; }

With this approach you cover the following situations:

  • If user has a mobile device, mouseover won't be triggered, therefore the a:hover rule won't be present, and the first click on the link will trigger the desired behavior.
  • If user has a mouse connected to desktop computer, tablet, mobile, or any kind of device, has-mouseover will be added as soon as mouse is moved inside the website, therefore all :hover or rules that you prefix with html.has-mouseover will be present.
How to use
  1. Install this module through composer:
    composer require drupal/mouseover-detect
  2. Enable mouseover-detect module.

Once module is enabled, you will see has-mouseover class in the html tag, from here you can create :hover styles that depend on this class, so that it works only when mouseover has been detected.

Categories: Drupal

Don't Miss: The making of Call of Duty 4: Modern Warfare

Social/Online Games - Gamasutra - 24 May 2019 - 10:49am

"We tried several different directions, many of which were failures, but the ultimate result was the best game any of us have ever worked on." ...

Categories: Game Theory & Design

13 data centers in key game dev areas now support xCloud, testing open for some devs

Social/Online Games - Gamasutra - 24 May 2019 - 10:16am

Microsoft has published a post that offers developers new information on its Project xCloud streaming service, detailing the steps its currently taking to make the service as accessible as possible for game developers. ...

Categories: Game Theory & Design

Uncache AJAX forms

New Drupal Modules - 24 May 2019 - 9:49am

This module exists solely for quickly bypassing the problem occurring with AJAX forms when the page is cached. This is thoroughly described at #1694574: drupal_process_form() deletes cached form + form_state despite still needed for later POSTs with enabled page caching.

According to @firewaller (see comment #94 in issue above), there are the following proposed solutions:

Categories: Drupal

Dauntless saw 500,000 new players within 24 hours of its cross-platform launch

Social/Online Games - Gamasutra - 24 May 2019 - 9:05am

That influx of new faces brings the free-to-play RPG†™s lifetime player count over 4 million. ...

Categories: Game Theory & Design

Video Game Deep Cuts: Observing A Playdate With Some Cool Ghosts - by Simon Carless Blogs - 24 May 2019 - 8:29am
This week's roundup includes a look at AI thriller Observation, the unique new Panic handheld Playdate, and subjects including eSport shadiness, Oculus Quest, and Pathologic 2.
Categories: Game Theory & Design


New Drupal Modules - 24 May 2019 - 7:27am

QuickTwig is a tool for theme developers to quickly override Twig template files. Instead of searching through Twig debug markup and manually copying and renaming files to your theme folder, you can easily access QuickTwig on the toolbar, which will open an off-canvas dialog on the page. Select a theme hook, source template and new template filename (based on the file name suggestions listed in the HTML comments), and QuickTwig will copy the Twig template to your current theme.

Categories: Drupal

Design trajectories in Let's Play: Ancient Greek Punishment: Chess Edition - by Pippin Barr Blogs - 24 May 2019 - 7:27am
Pippin Barr examines the design and development process of his game Let's Play: Ancient Greek Punishment: Chess Edition, making use of his extensive documentation for the project.
Categories: Game Theory & Design

Taking A Look(ing Glass) at Thief: Deadly Shadows... 15 Years Later - by Michel Sabbagh Blogs - 24 May 2019 - 7:14am
15 years ago, Thief saw a third outing in a year hosting the likes of Half-Life 2. Doom 3 and Far Cry. In this retrospective piece, Bethesda Softworks alumnus and writer Michel Sabbagh explains why Deadly Shadows should be celebrated.
Categories: Game Theory & Design

Kliuless #36: The Tech Cold War - by Kenneth Liu Blogs - 24 May 2019 - 7:12am
Each week I compile a gaming industry insights newsletter that I share broadly within Riot. This edition is the public version that I publish broadly every week as well. Opinions are mine.
Categories: Game Theory & Design

Gábor Hojtsy: Analysis of top uses of deprecated code in Drupal contributed projects in May 2019

Planet Drupal - 24 May 2019 - 6:00am

Dwayne McDaniel did some thorough reporting of deprecated code use in all Drupal 8 contributed modules in March. Ultimately this kind of reporting would be best to have on but while that is figured out, Dwayne's data set provides a very nice way to mine data about Drupal 9 readiness of contributed modules and to inform our tooling to improve the process. His original numbers showed that almost 44% of contributed modules had no deprecated code use at the time. What I was interested in was how to help the rest of the 56%.

Dwayne created an updated process and a new repository this week with fresh data. I was still curious so I delved right into the data and started mining it. A key question I was interested in is how much of the most widespread deprecations are actionable right now. An actionable deprecation is something core deprecated in a previous version that is not supported anymore, so you can update your code to remove the use of that API. Currently Drupal 8.6 and 8.7 are supported, so deprecations there should only be acted on for your custom code. However deprecations in and before 8.5 are entirely fine to act on.

First I counted the top list of deprecated APIs used from Dwayne's data across all of contributed projects. Then I wrote a script to collate documentation to the deprecation notices. Ideally phpstan itself would report these messages directly and Matt Glaman is working on that. However since that is still blocked on the phpstan side, one needs a different data source to find the deprecation documentation for each occurrence, so I took to to get that for now. Once that is found, we can categorize the deprecations into actionable, not actionable and actionable for custom code only. For the later case you know which core version you are using, and that should be an up to date minor version. So you don't need to deal with what core branches the community supports otherwise.

The results look really promising so far in terms of how much contributed modules can make progress on even today. If all already actionable deprecations get resolved, there will be very little left at least of the deprecations we already know.

A month ago Dezső Biczó created a set of proof of concept Rector fixes to automate some of these deprecation fixes, so I opened an issue with this new data set to try and cover the top ones that are not just actionable but approachable to automate.

As with all interesting data sets, this summary is just the tip of the iceberg. There is huge potential to mine this data set for other uses, such as finding modules that potential contributors at an event could contribute fixes to. I don't know yet how much I can continue to work with this data myself, and of course others doing analysis of their own would be more than welcome.

Are you a project maintainer? Now would be a good time to fill in your Drupal 9 porting information in your project, so you can let contributors know how to best engage with your in the process towards Drupal 9. projects can now specify Drupal 9 porting information, so *you* can direct *your* contributors to provide the most valuable help on the way to Drupal 9, fund the process or just step back (for now). Edit your project to help your contributors help you!

— The Drop is Always Moving (@DropIsMoving) May 21, 2019

Disclaimer: The data is based on the state of contributed projects on May 20, 2019 based on Drupal core's 8.8.x development branch on May 20, 2019. The lookup on was not perfect and I found some bugs there that are being resolved as well so the data gets more accurate. Also, as contributed modules will get updated, there will be less uses of deprecated APIs. As core will introduce more deprecations, the data could get worse. There may also be phpstan Drupal integration bugs or missing features, such as not finding uses of deprecated global constants yet. This is a snapshot as the tools and state of code on all sides evolve, the resulting data will be different.

Categories: Drupal

Elfsight Airbnb Reviews

New Drupal Modules - 24 May 2019 - 5:30am

Elfsight Airbnb Reviews widget helps you to embed recommendations about your apartment or hotel from Airbnb on the website. You will be able to filter unwanted reviews, with the help of predefined filters; show the star and number ratings, add detailed info about the guests, as well as use a call-to-action button, which will invite visitors to share their thoughts about your lodging on Airbnb. Elfsight Airbnb Reviews widget will help you boast your great social proof on the website and have new guests.

Categories: Drupal

Elfsight Booking Reviews

New Drupal Modules - 24 May 2019 - 5:27am

Elfsight Booking Reviews tool allows you to display reviews about your place that guests leave at You are able to exclude undesired reviews, using filters; demonstrate your star rating and number rating from Booking, show details about the real clients, and place an active call-to-action button that will inspire users to publish a new review about your lodging. Elfsight Booking Reviews will help demonstrate your high social proof on your site and start having more new visits.

Categories: Drupal

Entity Type Behaviors

New Drupal Modules - 24 May 2019 - 3:52am

This project allows a user to attach behavior settings to any fieldable entity type.
The idea came from "Paragraph behaviors". And has been extended to all entity types.

It allows developers to create custom "behavior" plugins, which can be enabled for a content type.

The custom behavior plugin will then be available to enable on a specific entity type and bundle.

Categories: Drupal

Digital Echidna: Thoughts on all things digital: Smart Date Module Puts a Premium on Time, User Experience

Planet Drupal - 24 May 2019 - 3:05am
Time is always of the essence. From a consumer perspective, you want to know when events take place, when something’s open or closed, how long a meeting or activity will last. And, from a development perspective, you want to be able to create a date…
Categories: Drupal


Subscribe to As If Productions aggregator