|Category:||Puzzle ➤ Transport ➤ Misc.||Commercial:|
|License:||GPL v3||Deb Repo:|
|Played:||Single & Multi||PDA:|
|Quality (record):||Quality (game):|
|Contrib.:||Goupil & Louis||ID:||14721|
|[fr]:||Un puzzle abstrait dans lequel le joueur tente de déjouer un mécanisme complexe||[en]:||A game of competitive puzzle-design. At its core, this is an abstract Turn-Based puzzle game in which you pick a lock by co-ordinating a pair of tools to manipulate its mechanism.|
Trailer / Gameplay [en] / [en] / [fr] :
Website & videos
[Homepage] [Dev site] [Features/About] [Screenshots] [Videos t t t g g g g g g g g] [WIKI] [FAQ] [RSS] [Changelog 1 2]
Commercial : (empty)
[Open Hub] [PCGamingWiki] [MobyGames]
Devs (Martin Bays [fr] [en]) : [Site 1 2] [twitter] [YouTube] [Interview 1 2]
Game : [Blog] [Forums] [twitter] [YouTube]
On other sites
News / Source of this Entry (SotE) / News (SotN)
Un puzzle abstrait mono et multijoueur en compétition et au tour par tour, par Martin Bays (mbays).
Intricacy est un puzzle abstrait mono et multijoueur (en compétition et au tour par tour), dans lequel le joueur tente de déjouer un mécanisme complexe (conçu éventuellement par un autre s'il joue en multi) qui lui est présenté.
À la base, c'est un jeu de puzzle abstrait au tour par tour dans lequel vous choisissez un verrou en coordonnant une paire d'outils pour manipuler son mécanisme. Les verrous que vous choisissez sont conçus par d'autres joueurs; une fois que vous avez compris le secret sur la manière de crocheter la serrure, vous devez sécuriser ce secret derrière un verrouillage de votre propre conception.
Le joueur dispose de 2 outils (un petit et un gros) en bas à gauche de l'interface (grise), qu'il peut déplacer de case en case (cases hexagonales).
A l'aide d'un outil il déplace un mécanisme comprimé par un ressort, permettant éventuellement de libérer la place pour en glisser un autre un peu plus loin, le but étant de parvenir à libérer une gâchette en haut à droite de l'interface. Plusieurs types de mécanismes viennent complexifier l'ensemble.
Un éditeur intégré à l'interface (non testé) permet d'élaborer de nouveaux puzzles (notamment pour le mode multi).
A game of competitive puzzle-design.
At its core, this is an abstract Turn-Based puzzle game in which you pick a lock by co-ordinating a pair of tools to manipulate its mechanism. The locks you pick are designed by other players; once you have figured out the secret of how to pick a lock, you must secure that secret behind a lock of your own devising.
Free software, released under the GPLv3.
Written in Haskell, with SDL and Curses user interfaces.
Rough description of the game mechanics
• Locks consist of blocks, pivots and balls. Blocks can be connected to other blocks by springs. Pivots have arms. When picking a lock, you control two tools - a hook, which acts as a mobile one-armed pivot, and a wrench, which acts as a mobile block with momentum.
• To open a lock, the "bolthole" (the area in the top-right) must be empty.
• Each turn, the tools push and rotate according to the player's commands, and then each spring which is compressed or extended beyond its natural length pushes/pulls on the block at its end.
• If two forces try to move a piece in two different directions, or try to move two pieces into the same hex, one or both is blocked.
• If a pivot/hook is trying to turn and there's a piece in the way of one of its arms, it will at first try to push the piece away - but if that force is blocked, it will try instead to pull the piece round with the arm as it turns.
• If two springs are trying to push two blocks into the same hex, they will generally both be blocked. However, if one of the forces is also pushing against a fixed piece such as a tool, it won't block the other force.
Full details of the metagame mechanics
(Where by the 'game' I mean the lock-picking bit, and by the 'metagame' I mean the bit with the 3-letter codenames and the three lock slots and notes and so on.)
Scoring is always relative - each player has a score relative to each other player. That score is the number of the second player's lock slots to which the first player has access, minus the number of the first player's lock slots to which the second player has access.
A player accesses a lock slot when one of the following holds :
• the player has solved the lock in the slot, and declared the solution;
• the player has read three notes on the lock in the slot;
• there's no lock in the slot, and the player has accessed all the slots which do have locks in them.
A player reads every note in every lock the player accesses. When a lock is replaced ('retired'), each note secured by the lock becomes 'public', and is read by every player.
Note this means that once three notes on a lock become public, every player accesses the lock. The lock is then 'public' (and its owner should replace it!).
To declare a solution, you must secure a note on it behind a non-public lock in one of your three lock slots. Once the note is placed, it can't be moved.
Full details of the game mechanics
Springs are directed; one of the blocks it is connected to is the 'root', the other the 'end'. A block is stationary if it is not the end of any spring. The directed graph whose nodes are the blocks and whose edges are the springs is required to be acyclic. A spring may also be rooted in a pivot.
I will now attempt to describe in full excruciating detail the game physics, i.e. the algorithm used to determine what happens on a turn. You shouldn't need to read this to play the game! Experimenting and turning on blockage annotations should be enough.
The following description corresponds to the code in Physics.hs. The algorithm is the result of an extended process of experiment and iterated simplification; see notes/game in the source distribution if you're perverse enough to want to read a scattered stream-of-consciousness account of the process.
Each turn is separated into two phases. In the first phase, the forces arising from the player's move are 'resolved', possibly resulting in some movement. In the second phase, forces arising from stretched or compressed springs are resolved, possibly resulting in some movement.
Here we abuse physics terminology, and use the term 'force' to refer to either a directional force in the usual sense, which we call a 'push', or a rotational force, which we call a 'torque'. A force is always on a piece, in some direction. Only the obvious six hex directions and the two obvious rotational directions occur; the magnitude is always 1.
Player moves result in forces on the tools in the obvious way. A wrench which is moving gets a push in that direction each turn (sorry, Newton!). A spring which is not at its relaxed length results in a push on the end piece.
To _resolve_ these initial forces:
• each initial force is 'propagated to a force group'
• if a group is 'inconsistent' with another group: if one of the group is 'dominated' by the other, it is 'blocked'; else both are blocked
• each force in each unblocked force group is 'applied'
To _apply_ a push: move the piece in the given direction.
To _apply_ a torque: rotate the piece in the given direction.
To _propagate_ a force:
• If applying the force would result in an overlap with another piece, push that piece - but if it's an arm, twist the pivot instead when that makes sense.
• If the force is a torque and an arm is pushing on another piece, we have a special rule: if the obvious push ends up propagating to a resisted force (see below), then it is replaced with a 'clawing' push. e.g. in the following situation:
\ O #
if the pivot is twisted clockwise, the ball will first be pushed east, but when that force propagates to a push on the stationary block to its east which is resisted, processing will back up and a push on the ball southeast will be tried instead.
• A spring connecting two blocks transmits a push on one block to the other unless the direction is such that the push is tending to compress/extend the spring and the spring isn't already fully compressed/extended.
A force is _resisted_ if it is a push on a pivot or on a block which isn't the end of a spring, or it's a torque on a block, or it's a force on a hook which isn't already getting that force this phase as the result of a player move, or it's a force on a wrench which isn't a push in the direction it's already moving.
To _propagate an initial force to a force group_:
• Propagate the force as above, then recursively propagate the resulting forces, checking for resistance as we go. The force group consists of all the resulting propagated forces.
• On resistance: back up to try clawing as described above if appropriate, else consider the whole force group resisted - so the resulting force group is empty.
Two forces are _inconsistent_ when
• they act on the same piece in different directions, or
• applying both at once results in overlapping pieces.
Two force groups are _inconsistent_ iff there is some force from the first which is inconsistent with some force from the second.
A force group _dominates_ another iff their initial forces are spring forces, and the root of the first spring is an ancestor of the root of the second spring, where an ancestor of a block B is recursively defined to be a block which is the root of a spring which ends at B, or an ancestor of such a block.
-- firstname.lastname@example.org 2013
Test (du binaire en version 0.4.1) par goupildb :
(testé 10 min)
Le jeu est fonctionnel, avec une belle interface.
Pas évident à maîtriser.
J'étais plutôt sceptique avant d'essayer le jeu (la page du site semblant ancienne je me demandais s'il allait fonctionner, et donc l'entrer dans le Bottin), mais il m'est rapidement apparu intéressant et même addictif.
Très très bien. Bravo et merci à son auteur !