We use an online editing program called ProofHQ, where you and our development team will review the rules, discuss ideas, and add comments and suggestions, so that these rules are of the same high quality as our other game rules. We have used this process for years, because integrating outside eyes and ears is an invaluable asset.

The story behind this game started many years ago. My two sons were playing Pokemon, collecting cards and constantly talking about these fantasy creatures. I noticed, amazed, that after a while they knew by heart names, complicated properties and relations of somewhere around hundred, maybe more, characters! How did it happen, seemingly effortless? Did they study hard? Not in the sense we normaly think about studying. They were playing. They were having fun. And their hungry brains, like kids have, just absorbed the names, properties and relations. Seemingly effortless.

[0.5] Controls & Training & Help[0.1] Menu & Settings[0.4] Sound & Music[0.1] Graphics[0.1] Game Design[0.3] Game Story[0.1] Game Content[0] Completion time (level/game)?[0] is it Enjoyable & Fun?[0] Could it hold a spot in Favorites? (& if the Game can be repeatedly played again)[0] BONUS point: Multi-Player related[0] BONUS point: Review for VRStars received: 1.6/10

Nothing but a lazy asset flip from the Unity Asset Store:https://assetstore.unity.com/packages/templates/systems/sky-flight-full-game-template-113460And yeah, the developer bought a low poly winter landscape as well. Buy two asset kits, replace above asset kit for gameplay and then replace the map with a new winter low poly asset map to try and "hide" the laziness and using asset kits. SMH.https://www.youtube.com/watch?v=RJPJqok8iecExport, change the name to "Bird" and ready for Steam in less than 10 minutes of work! The developer couldn't even be bothered to make a way to EXIT the game much less add Steam high scores, controller support, or achievements! NOT RECOMMENDED! *Refunded this myself* ..Let your wallet talk and Please don't support lazy developers like this one.

Onto the review!

Yeah, I probably think of using foam before anyone else does.

You can add-on more copies of the game

In MetalSkies we take the approachability of Risk and combine it with greater strategic depth. That's why we've spent dozens of hours perfecting MetalSkies' gameplay mechanics and strategic balance.

Have you ever played Risk? If you're looking at this game, there's a good chance you have! I wager you know the frustration of losing your huge army to one a third its size because of a handful of random dice rolls. The pace of Risk is great, but I find it hard to take the 5th straight roll of snake eyes.

Have you ever tried Axis and Allies? I did too. And by tried, I mean just that!  Two hours after opening the box, we finished the manual and nearly died laughing. There was no way we'd have enough time left to play the game, AND we had already forgotten the first half of the directions anyway!

Fatum Betula is, arguably, a nearly perfect video game, depending upon your philosophy when it comes to criticism. If you, like me, believe that to a large extent the success of a game depends upon how well it achieved what it set out to do, I think you can get very far with such an argument.

And Ashampoo Office 8 doesn't save your files in some online cloud service but where they belong: on your PC!

# unauthenticated do # as :user do # root to: 'devise/registrations#new' # end # end

# authenticated :user, lambda {|u| u.role == "admin"} do # root to: "admin/dashboard#show", as: :user_root # end

# +devise_for+ is meant to play nicely with other routes methods. For example, # by calling +devise_for+ inside a namespace, it automatically nests your devise # controllers: # # namespace :publisher do # devise_for :account # end

This approach is preferable to overriding authenticate_user! in your controller because it won't clobber a lot of "behind the scenes" stuff Devise does (such as storing the attempted URL so the user can be redirected after successful sign in).

however, if this is relevant to just one spec, you don't necessarily need to include devise helpers to all your controllers specs, you can just explicitly include those helpers in that one controller describe block: require 'spec_helper' describe MyCoolController include Devise::TestHelpers it { } end

Scholar@UC: University of Cincinnati's self-submission institutional repository

let(:warden) do instance_double('Warden::Proxy').tap do |warden| allow(warden).to receive(:authenticate!).with(scope: :user) .and_return(authenticated?) allow(warden).to receive(:user).with(:user).and_return(user) end end let(:user) { instance_double(User) } let(:authenticated?) { true } def simulate_running_with_devise stub_const( 'Rack::MockRequest::DEFAULT_ENV', Rack::MockRequest::DEFAULT_ENV.merge('warden' => warden), ) end

Yes, you are right. That was a very bad workaround. Stubbing methods on NilClass can be compared to switching to dark side of force. Powerful but comes with a huge price. I highly don't recommend using my workaround from 1 year ago.

There is no request.env in functional tests because the functional tests are supposed to remain at the controller level.

Could you please update the wiki yourself? Thanks!

Wasn't sure if this belonged as an issue in Devise or Rails though.

For now, you will need to give the second root a different named route: authenticated :user do root to: "users#index", as: :authenticated_root end unauthenticated do root to: "main#index" end

This is a Rails change of behaviour and Rails is not going back.

class LoggedInConstraint def self.matches?(request) request.env['warden'].authenticate? end end

I'm closing this issue. If you have any problem, please comment to this issue :-)

class AuthConstraint def initialize(&block) @block = block || ->(_) { true } end def matches?(req) user = current_user(req) user.present? && @block.call(user) end def current_user(req) User.find_by_id(session[:user_id]) end end This is a flexible approach to defining route access based on any desired variable (roles, auth, etc...)

This is a great application for using route constraints.

scope module: 'authenticated', constraints: AuthConstraint.new { |user| user.present? } do # Management dashboard root 'dashboards#index' end root 'home#index'

answered

authenticated :user do root 'calendars#index', as: :authenticated_root end unauthenticated :user do root 'pages#home', as: :unauthenticated_root end

You can also specify constraints as a lambda:

The hostname's first n segments, starting from the right (the TLD).

find_field finds by id, name or placeholder text - so find_field('Prefix') should find the element with matching placeholder text rather than needing xpath.

It might be possible to fix it in Capybara, but I'm afraid that we'd just add more unexpected, ambiguous behaviour (which key should have been pressed, backspace, space?).

Here's another workaround:

find_field('Prefix').send_keys([:control, "a"], :backspace)

fill_in('Foo', with: 'bar', fill_options: { clear: :backspace })

Most of my work has been writing computer software, but this has touched on a wide range of other areas: scientific equipment, data analysis, visualization, geological exploration, simulation of complex systems, economic modeling, maps, “big data”, trend analysis, artificial intelligence, and web software.

I am not at Stanford anymore. I just have my web pages here because I have an alumni account at Stanford. Thank you, Computer Science Department!

Why interactive explanations? I find that I learn best when combining the language side of my brain (reading, formulas) with the visual side of my brain (illustrations, interaction). I want to learn not only by reading something or watching something, but by playing with it. I’m mostly focused on small, self-contained articles, but I’m also interested in interactive textbooks.

I create interactive explanations of math and computer science topics at Red Blob Games[1]. I explore topics related to computer game development, as I’ve found that’s a rich source of motivating examples. My favorite topics are related to maps (grids, paths, procedural generation) and simulations (transportation, economics, complex systems, AI).

I've been collecting hex grid resources[1] for over 25 years.

Only two of the three coordinates are needed to find each hex, the third coordinate can be used as a check. Trios of hex coordinates always add up to 0.

International backers have two options:  a) quick delivery but expensive shipping b) slow delivery but cheap shipping

Please note: The shipping cost does not include any local import tax you may have to pay in your own country. 

I'm maintaining one that can be run and asserted on: https://github.com/cirosantilli/rails-cheat/blob/master/app/test/integration/capybara_test.rb

I have a 2 radio buttons with the same id and label, only different values, (true, false)....anything I can do to choose false?

   Ambiguous match, found 2 elements matching visible field "name" that is not disabled

why do you guys think have_css matcher is named the way it is? I mean, it sure deals with css identifiers, but have_css gives(at least to me) the impression that the page has certain stylesheet loading.

Thanks much for hearing me out.

data[:users, :[], :name] = 'Matz' # :[] is next index, 0 in this case

reduce(root){@1[@2]||={}}

A proposal to specify the path for bury with classes as values of a hash arg: {}.bury(users: Array, 0 => Hash, name: Hash, something: 'Value') # {user: [{name: {something: 'Value'}]} So all absent nodes could be created via klass.new

{}.bury(users: Array, 0, 'Value')

{}.bury(users: Array, 0 => 'Value')

A one-liner alternative for hash-only cases can be implemented using Enumerable#reduce: root = {} [:a, :b, :c].reduce(root){@1[@2]||={}}[:d] = 'E' # root => {:a=>{:b=>{:c=>{:d=>"E"}}}}

I think the issues/problems specified in the comments are not present with a Hash-only implementation. :) I would be supportive of re-considering this feature just for use with a Hash, where I believe 80% of the real-life use cases would (and do) exist. I have encountered this need before in the wild, but not with Arrays.

If this is okay, then it might even be nice if #dig took a block as well as a fallback value: [].dig(1) { 'default' } #=> "default"

Would it be desirable to specify the new object in a block? That would make it somewhat symmetrical to how Hash.new takes a block as a default value.

data = {}.extend XKeys::Auto # Vs ::Hash, uses arrays for int keys data[:users, 0, :name] # nil data[:users, 0, :name, :raise => true] # KeyError data[:users, :[], :name] = 'Matz' # :[] is next index, 0 in this case # {:users=>[{:name=>"Matz"}]} pick = [:users, 0, :name] data[*pick] # Matz data[:users, 0, :accesses, :else => 0] += 1 # {:users=>[{:name=>"Matz", :accesses=>1}]}

In fact, I'm only here because it seems like something one would 'expect' ruby already to do.

The reason Final Form does this is so that pristine will be true if you start with an uninitialized form field (i.e. value === undefined), type into it (pristine is now false), and then empty the form field. In this case, pristine should return to true, but the value that the HTML DOM gives for that input is ''. If Final Form did not treat '' and undefined as the same, any field that was ever typed in would forever be dirty, no matter what the user did.

If you change a form value to '', Final Form will set the value in its state to undefined. This can be counterintutive, because '' !== undefined in javascript.

// WRONG ❌ - values.myField might be undefined! if (!values.myField.match(/myexpression/)) {

If you are doing a regular expression check, your function should handle undefined as a potential value.

Your validation functions should also treat undefined and '' as the same. This is not too difficult since both undefined and '' are falsy in javascript. So a "required" validation rule would just be error = value ? undefined : 'Required'.

If you've ever talked about regular expressions with another programmer, you've invariably heard this 1997 chestnut: Some people, when confronted with a problem, think "I know, I'll use regular expressions." Now they have two problems.

Addition of the keyword would allow such syntax as If ThisThing Ain't Nothing Then According the source "We're just trying to keep up with advances in the English language which, as you know, is changing almost as fast as technology itself."

Whenever I get a new cookbook, I go through it and bookmark recipes that are either worth considering, or that go on a list to definitely try. Usually the maybes outnumber the definites. In this case, I've bookmarked a large number of recipes that I DEFINITELY will make.

Do you prefer voice acting so you can bitch about the quality of that instead?

It seems the game is trying to be similar to Monkey Island, which isn't necessarily a bad thing. Imitation is sometimes considered flattery afterall.

_Underline_

If you want to know more about the story behind this best-selling game, check out the New Yorker Article.

A Dark Room makes use of the ProMotion and BubbleWrap gems. During its development Amir used all the refactoring techniques of the Ruby language and also ran the built-in spec framework in the background

Not enjoying Xcode, Amir used RubyMotion instead. Amir had real-world experience with Xcode and Objective-C, but didn't like it at all. Amir also has a Ruby background and went with RubyMotion to build A Dark Room. The command-line interface, the testing framework, the gems libraries and the CocoaPods integration and the freedom to use any text editor contributed to his decision.

has been downloaded nearly four million times worldwide across both app stores

ProMotion is a RubyMotion gem that makes iOS development more like Ruby and less like Objective-C.

While you're welcome to use ProMotion, please note that we rely on the community to maintain it. We are happy to merge pull requests and release new versions but are no longer driving primary development.

Influenced byC, Smalltalk

The overridden core classes for Hash and Array here only handle those two types. A hash hands off a bury to an Array if it encounter a nested array. Similarly, an Array hands off a bury if it encounters a non-integer or a nested hash.

Some pesky non-human users (namely computers) have taken to “hotlinking” assets via the raw view feature — using the raw URL as the src for a <script> or <img> tag.

The key point is that this is a feature to improve the experience of our human users.

The problem is that these are not static assets. The raw file view, like any other view in a Rails app, must be rendered before being returned to the user. This quickly adds up to a big toll on performance. In the past we’ve been forced to block popular content served this way because it put excessive strain on our servers.

As nosniff support is added to Chrome and Firefox, hotlinking will stop working in those browsers, and we wanted our beloved users, human and otherwise, to know why.

We’re happy to report that the good people at Google and Mozilla are moving towards adoption as well.

We added the X-Content-Type-Options: nosniff header to our raw URL responses way back in 2011 as a first step in combating hotlinking. This has the effect of forcing the browser to treat content in accordance with the Content-Type header. That means that when we set Content-Type: text/plain for raw views of files, the browser will refuse to treat that file as JavaScript or CSS.

Just as we've become super-human thanks to telephones, calendars and socks, we can continue our evolution into cyborgs in a concrete jungle with socially curated bars and mathematically incorruptible governance.

we should eagerly anticipate granting ourselves the extra abilities afforded to us by Turing machines

Stop thinking of the ideal user as some sort of honorable, frontier pilgrim; a first-class citizen who carries precedence over the lowly bot. Bots need to be granted the same permission as human users and it’s counter-productive to even think of them as separate users. Your blind human users with screen-readers need to behave as “robots” sometimes and your robots sending you English status alerts need to behave as humans sometimes.

When the computer created such amazing potential, humans decided that their human genius machines could be handy if they implemented all the pre-existing genius practices.

# Parallel Ruby universes ("Rubyverses") - A proposed interface for # parallel, "semi-private" method or method-and-data spaces via # "closely associated" objects.

Review changes

dont belive the tags, it doesn't have any steam trading cards. waste of money and time.

If you’re a puzzle fan and own any type of Windows, MacOS or even Linux computer,

Yes I fully understood that this was going to be a cryptic puzzle game and that it required research outside of the game. I expected this to have ARG elements and require abstract thinking. However, I also expected it to be longer than 2 minutes of content. You are given 10 pages to read in-game, they might as well have just been screenshots posted somewhere on the internet. And you have no way to input your solutions in game.

This is gonna be an uphill slog and I'm really excited for it. If you know that's what you're getting into (a long slow grind on puzzles that may not fit well together), this could be great - especially if you're invested in both the work and the community (posting on here helps loads with games like this!) Your mileage may vary!

Thanks for review. Please post also to protondb.com to help users and devs there...

Proton is a new tool released by Valve Software that has been integrated with Steam Play to make playing Windows games on Linux as simple as hitting the Play button within Steam. Underneath the hood, Proton comprises other popular tools like Wine and DXVK among others that a gamer would otherwise have to install and maintain themselves. This greatly eases the burden for users to switch to Linux without having to learn the underlying systems or losing access to a large part of their library of games. Proton is still in its infancy so support is inconsistent, but regularly improving.

I've been made aware of a "Compatibility tool to run DOS games on Steam through native Linux DOSBox" called "steam-dos". It can be found on https://www.github.com/dreamer/steam-dos . I pulled this tool from git and using it as the the steam play compatibility tool Megarace 2 runs without issue. Saving both settings and games works again! There is no keyboard support for controlling the vehicle in game but both mouse and joystick/gamepad work. To get around a missing launcher.exe error I copied "MegaRace 2.exe" to the same folder as the original and renamed the copy to "Launcher.exe". Linux users: in your MegaRace 2 folder (steamapps/common/MegaRace 2/) create a symbolic link to start.sh named Launcher.exe. This allows the game to launch through Steam. This also allows you to put time on the game through Steam, hitting that coveted 5 minute mark that makes creating a review possible. With that out of the way, the game itself is a nice touch of nostalgia but the port is absolutely terrible. I don't remember it being quite this difficult to install off the 2 CDs. The game won't launch at all without tweaking. Can't save the config settings. Can't save the game at all in fact. While I really like MegaRace 2, you unlock tracks by completing the previous ones. Since the game can't be saved, I end up running The Foundry track over and over until I'm sick of it.So I'm torn. I love the game but I hate the completely broken port. For $3 and a local install of DOSBOX it can be made to work so I will recommend it anyway.

Parking Attendant is a glorified app game that somehow landed into the Steam Store

The positive reviews are clearly friends of the developer, as this is an extremely low-quality Unreal game, the kind you'd expect from a student project or a 24-hour Game Jam, not something being sold on Steam.

Application: 3-D Shape RegistrationAn important problem in model-based recognition is to find the transformation of a set of datapoints that yields the best match of these points against a shape model. The process is oftenreferred to asdata registration. The data points are typically measured on a real object by rangesensors, touch sensors, etc., and given in Cartesian coordinates. The quality of a match is oftendescribed as the total squared distance from the data pointsto the model. When multiple shapemodels are possible, the one that results in the least total distance is then recognized as the shapeof the object.Quaternions are very effective in solving the above least-squares-based registration problem.

However, the matrixrepresentationseems redundant because only four of its nine elements are independent

ts geo-metric meaning is also more obvious as the rotation axis and angle can be trivially recovered.

Visible spectrum wrapped to join blue and green in an additive mixture of cyan

My preference here is biased by the fact that I spend everyday at work building web components, so Svelte's approach feels very familiar to slots in web components.

The codebase for Pomodone makes more sense to me in Svelte, not React. I find it easier to navigate and work with.

React and Svelte are very similar in many ways, but what I've found is that in all the little ways that they are different, I prefer Svelte.

Svelte is there when I need it with useful APIs, but fades into the background as I put my app together.

If I were to sum up why in one sentence, it's because I don't miss useEffect. I understand why it exists, I understand the approach React takes, and there are benefits of its approach. But writing complex React components feels more like admin; a constant worry that I'll miss a dependency in my useEffect call and end up crashing my browser session. With Svelte I don't have that lingering feeling, and that's what I've come to enjoy.

but I like that Svelte comes with a good CSS story out the box.

This isn't really a downside to React; one of React's strengths is that it lets you control so much and slot React into your environment

I like this approach more because I can scan the code that renders the Box component and easily spot that it takes two children. If the Box took any props, they'd be within the opening <Box> tag, and they would be distinct from any children props.

One gripe I've had with this approach is that you lose the visual cues that you're passing children into the Box component; they now aren't nested within the Box when you render them like we're used to in HTML; it's now up to you to read the props and spot which ones are being used to provide children.

Coming from React to Svelte this did catch me out numerous times but for me I now prefer Svelte's approach, particularly because it removes some of the boilerplate around useEffect.

Svelte is different in that by default most of your code is only going to run once; a console.log('foo') line in a component will only run when that component is first rendered.

Here's where I start to have a preference for Svelte; the two are very similar but once I got used to Svelte I found that React felt like jumping through hoops. You can't create a worker instance, it has to go in a useRef, and then you can't easily pull code out into a function without then requiring useCallback so it can be a safe dependency on useEffect. With Svelte I write code that's closer to "plain" JavaScript, whereas in React more of my code is wrapped in a React primitive.

One part of React that I've always championed is how it's just JavaScript. I like that in React you don't use a distinct template syntax and instead embed JavaScript, compared to Svelte's templating language

I will always find React's approach easier - at least in my head - and I think more friendly to people familiar with JavaScript who are learning a library.

I was pleasantly surprised by Svelte's templating; in the past I've found templating languages overwhelming and inflexible, but Svelte offers just the right amount of templating whilst enabling you to use JavaScript too.

Svelte looks pretty similar, but has two small changes that personally make the Svelte code easier to read, in my opinion:

because React components are re-executed every time the component re-renders, you can easily end up with thousands of workers being created! It's essential to use useRef to avoid this problem by maintaining a reference to the worker that you've created.

However, if these timeouts are moved into a web worker, they should run to time and not get de-prioritised by the browser.

What I like is that currentUser isn't a value, it's a store, and therefore you have full control over how you deal with it.

I like that Svelte doesn't make me use the subscribe API every time I need to read the value.

Talking of context, that's much closer to the approach I take with Svelte and use a writable store.

<template> and <slot>

This element and its contents are not rendered in the DOM, but it can still be referenced using JavaScript.

A Low Bar to Entry, and then What?There is an interesting tension between making something accessible and making it boring. Lowering the barrier of entry is a good thing, but if all you do is low-bar stuff, you end up losing the people again that you managed to attract. There needs to be a path forward beyond the entry level.

A business with a low barrier to entry would be those people in poor countries who “wash” your windscreen at traffic lights. A bucket, a cloth, some water and you are in business. A business with a high barrier to entry might be airlines: planes are expensive, staff with the right skills hard to find, the necessary permits to fly hard to obtain.

The key to any good adventure game, really any good game at all, is to guide the player toward understanding the game world's internal logic, even if that logic only makes sense in the game world. This internal logic is what differentiates a game that encourages clever, creative problem-solving from a game like Antventor, which is a maddening exercise in arbitrary, spaghetti-against-the-wall nonsense.In the old text-based adventure games, the internal logic was grammatical, often based on a simple verb-object combination. This simple structure encouraged absurd combinations, sometimes with no results, sometimes with hilarious results, and sometimes with surprisingly fruitful results. The game would subtly nudge you toward the correct solution with hints and consequences, and you would gradually learn the kinds of actions that made sense in the world and the types of consequences you could reasonably expect. Only after establishing those baselines would ambiguity start to creep in ("I could do this, but should I...?", "Is that item meant for here or there?"). As the genre aged, puzzles gradually grew more intentionally obtuse and absurd as a means to make the game "harder". Ultimately, this obscurantism was a sign of a dying genre, catering to a narrower and narrower echo chamber of hardcore fans, as the gaming world in general grew less patient with the kind of experimentation this genre was first built on.Unfortunately, Antventor takes inspiration from those later games. It is gorgeously animated, but the game design is awful. There is no scaffolding, and little to no internal logic to speak of. The interaction targets are often tiny, hidden, sometimes out of focus, and sometimes completely arbitrary. Combine this with an ever-expanding collection of items and screens, and the game quickly devolves into pointless trial-and-error with thousands of combinations.

"BEER" is a simple one-level platformer with an interesting concept: after some time a shadow of yourself appears and repeats every movement you've made. If the shadow catches you - it's a game over. With the passage of time, more shadows appear. Shadows will relentlessly chase you until they catch you. As much as I know, there is no victory: you will have to jump platforms and collect presents until you are caught. At one point, there are so many shadows, it's unavoidable to be touched by one of them. To delay this moment, you may move slowly, so it's easier to keep track of shadows. You may establish a specific route, so the shadows follow a predetermined pattern. Nevertheless, at one point there will be just too many shadows to avoid.