Mir wurde das Spiel glücklicherweise empfohlen und möchte es weiterempfehlen :)

this game is - well not exactly bad, but it also isn't a very good game of the genre - there are some riddles and puzzles that can give you quite the headache. I like hard puzzles, I like games where all isn't quite obvious - but I also like a barrier-free gaming experience.

It feels like it was thrown together in a weekend using parts from "Think To Die" since even the successful act of feeding your chickens has the same blood-splatter-on-camera-lens that you would get from scoring in Think To Die where your goal is to kill all of your people as opposed to this where you are feeding animals, so what's with the blood splatter? It just shows a lack of attention to detail.

The blood when you get the animal to food is really off putting. It doesn't make sense, is the player suppose to be eating the animal once you get it to food? If the dev just removed that it would make this game MUCH MUCH better.

It is also the first game I've seen whose icon for "mute" is not a crossed-out speaker/note, but a symbol for "pause" in musical notation...

Inspired by Minesweeper.

The problem is the 'power-ups' (aka cheats?): the ice cubes, bombs, and especially the teleports. They seem needed to solve some levels (at least for 3 stars completion), but because they are widely available (5 of each / level) they are completely overpowered. Why would you try to solve a level without them, when you can use them? It removes the incentive to actually solve the puzzles the hard way. It breaks the game. Shame.

The Not So Good: The Dev/s seems to be in hiatus -- still waiting for the "coming soon" additional levels: Laser Land.

This is an unfinished/abandoned 2D "diving" game (basically a flyer/"platformer") where you swim through an underwater maze and collect various objects. The game wasn't finished, it's clunky, and lacks polish. The developer dumped it on Steam as a quick cash grab and ran. This should be removed from Steam until completed (if ever). I can't recommend incomplete games,

I would be really proud to show it off it was "my baby", but as a player, it's incredibly boring.

The gameplay (swim to treasure chests to loot them and kill sharks on your way) is basic.

The movement speed is painfully slow. There's nothing to do on your way.

I love puzzles.I love detective games.I love story rich adventures.I love point and click games.Somehow this title FAILED in all four departments.The gameplay is Painfully broken.

these events can break the flow of the game and force the player to repeat sections until they master the event, adding false difficulty to the game.

Made with love an care.

An ingenious and adorable piece of casual gaming. Definitely recommended.

Motivation is provided by an ever-escalating difficulty, though not to the point where you feel frustrated.

A non-pretentious yet funny and innovative physics puzzle game

A Game-design MasterpieceTake one simple game mechanic, and make the absolute most of it – that's exactly what the developers of Jim is Moving Out did, and it worked really well! The core of this game is stunningly simple: a few little boxes (furniture) inside a big box (Jim's house), one or two flying fellas (the players) and a physics engine. Think about the most creative ways you could make this into a game. Anything you think about, this game did it. What if you had to squeeze through narrow holes without breaking too much furniture? It's in the game. What if the room had wheels? Yep, it's there too. What if one of the walls was missing and you had to avoid losing the furniture? The whole co-op is about this. Zero gravity? Yes, even that is in the game.

I must say I am quite surprised by so many negative reviews. To me this little game is pure genius. There's something about it you just can't put your finger on... something strange, hard to define. The premise is utterly simple - roll left or right - but the game keeps adding new possibilities every level. And it doesn't make a fuzz about it. "Here's something completely new, it's there, who cares". The mechanics and physics are spot on and the game explores them brilliantly. Visually it's beautiful and the characters you interact with are strange and fascinating. A feeling of novelty and discovery permeates the game from start to finish.Here's my suggestion: watch some videos of the gameplay and see if it bothers you. If not, go for it, for you've barely seen the tip of the iceberg.

is a casual indie game inspired by the old Tom & Jerry (NES) game

There were a few times I felt like making notes, but never ended up needing to because the scale of the puzzles is kept manageable throughout.

A very creative concept that i`ve never seen before in a video game.

A PvP level was added just for the sake of ♥♥♥♥♥ and giggles, the only purpose of this this is game is achievement farming.

however the biomass that you collect does nothing but gives "yay for you" points

Fortunately for fans of high quality puzzle games, RUSH is anything but simple.

Colormeleons

I'll tell you my intention right away, because the language difference between us may offend you. For those things I don't understand, I apologize in advance (if you don't need my apology and feel that my apology is offensive to you, I firmly withdraw my apology).

{Graphics}☐ Great - ☐ Good - ☑ Simple - ☐ Bad{Gameplay}☐ Great - ☑ Good - ☐ Meh - ☐ Unplayable{Audio}☐ Great - ☑ Good - ☐ Nothing Special -☐ Bad{Audience}☑ Kids - ☑ Teens - ☑ Adults{Difficulty} ☐ Too easy -☑ Just Right - ☐ Easy to Play/Hard to Master - ☐ Too Hard{Story}☐ Great - ☐ Good -☐ Simple - ☐ Barely a Story - ☑ No Story{Game Time}☐ 100+ - ☐ 61-99 - ☐ 39-60 - ☐ 11-30 -☑ 0-10 {Overall}Very enjoyable Chess Puzzle Game that should appeal to both Chess and Puzzle Gamers.

Many hand made levels

Academy Games has always prided itself in the quality of its rules. Most of our rules are taught in stages, allowing you to start playing as soon as possible without needing to read everything. We are very careful about the order we teach rules and rely heavily on graphics and pictures to facilitate understanding. We also include a large number of detailed picture examples, often with 3D renders, that help you understand the context of the rules.

During development, we are constantly trying new and diverse game mechanics. The game's rules can change hour to hour as we test which ideas work best. Rules start out as just ideas and we record which ideas work and which ones don't. This forms the first development ruleset which is essentially a change log that notes why ideas do or don't. As the rules are consolidated, there are rarely any pictures to indicate what a rule is referring to,  since prototype art is also changing constantly. Terminology can also change section to section as we explore what wording works best. This makes the development rules impossible to understand for anyone other than the development team.

We also include a large number of detailed picture examples, often with 3D renders, that help you understand the context of the rules. For these reason, we generally don't start laying out the final rulebook until production art is complete. Writing and laying out a 20 page rule book like this generally takes about 3 months from start to finish, usually requiring a complete rewrite or two, and involves dozens of editors.

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