Open Charilaos opened 6 years ago
General
In-game status card (above)
Tutorial card
Steps card
Pause menus
The Countdown feature
Levels by difficulty
Completed levels
Top menu
Levels by category
Back to the top menu
Top menu ALTERNATIVE
Globally shared levels
All level selection info cards
Level Editor
Really looking forward to hear some feedback!!
This is absolutely FANTASTIC! I totally love every single aspect of your designs.
It is specially nice that this will adapt perfectly to nearly all imaginable device sizes (beyond a certain minimum size of course) and input methods.
You covered pretty much everything here.
About redefining difficulty and categories and having 8 of each: I agree that this makes the whole thing look better organized. I have made a quick check about how many of the currently (the latest java-based work in progress) built-in levels fall into each:
5 Simple 47 Easy 38 Straight (formerly Moderate) 67 Normal 57 Tricky 47 Tough 26 Difficult 33 Hard 10 M.A.D.
28 Fun
23 Travel
57 Action
52 Fight
73 Puzzle
45 Science
48 Work
3
Reduction to 8 difficulty levels is straight-forward: Integrate Simple into Easy. But I am not sure now about my previous choice to rename Moderate to Straight. Maybe I should revert to the old name. I surely want to keep M.A.D. Not only resembles this the name of one of the favorite magazines of my youth, but somehow the explicit abbreviation dots makes me think of S.W.A.T. And levels in these difficulty surely need very special tactics indeed ;-)
The categories are much harder to decide upon. I don't want to follow your proposal to join Puzzle and Science because there are so many levels there. The science category should indeed by used for levels that need a different approach to solving than just combining well-known game elements. But I guess it would make much sense to reorganize the categories Action,Fight into Fighting, Speed, Survival. All three things lay stress on being fast in some way but with slightly different flavor:
Speed - just being fast to achieve the goal without enemies overly present Survival - avoid being killed by enemies without much fighting back Fighting - live and let die
About globally sharing levels: This is one of the benefits of making an online-only game. I am not quite sure about how to organize these, tough. I am not very fond of the idea of actually curating levels because it will require some constant effort on our side even if the game is all finished and I want to turn to other projects more. Maybe just having automatic rankings on the base of novelty or most played or most loved or such is good enough. I am not sure about how to handle potential abuse (swearing or other stuff in the level names and descriptions), but I will leave this out for now.
Hi from a random outsider / longtime fan who's been following this repo for a while 👋 this looks incredible! I love the clean/modern look of the panels and I particularly like the instant level preview. Showing demos in the background was fun, but I often only figure out whether I want to play a level after seeing it, so this would make browsing a great deal smoother.
r.e. handling potential abuse, I reckon you could get by using a bit of regex, plus a user flagging system, plus maybe something like this to flag possible abuse for inspection by an admin https://www.paralleldots.com/abusive-content . You'd only have to pay for it if you get past 1000 new levels a day, which would be a great problem to have.
Hey, first if all thanks for the kind words @ both!
Good point on the difficulty levels. How come there are only 5 simple levels? Keeping the original spirit on the difficulties sounds like a plan! Moderate sounds just fine and clear. And cool to hear a little backstory on M.A.D. :) It took me quite some time to figure out it meant Maximum Acceptable Difficulty. I like the mysterty about it. And even if people don’t get the abbreviation, its position after Hard, its color and its icon should speak volumes.
About the categories: again great to get some backstory on Science. It wasn’t entirely obvious at first, but it sounds like a clear distinction. And about re-categorizing Action levels into Fighting, Survival and Speed: love it! Should be very doable. I’m glad spending an afternoon playing all the Action levels. By the way, what are those 3 uncategorized levels?
Also very reasonable point about the featured levels. Active players would start to expect a regularly updated list. 3 alternatives I’ve thought of that also could make sense (and aren’t seen in the design) are: most loved, (your) recently played, or all levels. I don’t think swearing is very likely to occur given the expected audience. This is pure speculation, but I assume for every person that starts abusing the level names, at least one fan will reach out to us here.
There is however a bigger issue that is inherent to a pure online game. While people can create levels, fill in an author name and flip the switch to make it globally available, the lack of account creation makes the following impossible:
In an ideal world, players would have accounts, you could follow other authors that make great levels, and even find their newly created levels in a feed. While that’s a lot of work, there are 2 simpler solutions:
Finally, if the game artwork and UI is exported as regular PNGs (as I posted it here) it looks good on regular displays, but very out of place on high density displays such as retina displays and scaled displays on Windows computers (especially since fonts are always crisply rendered). So there’s a decision to be made on whether we use PNG’s (booh), SVGs (guaranteed to look good but also tend to cause glitches on several browsers and are the least performant), or doublesized PNGs that are rendered the same size as normal (recommended, should look good everywhere without performance or render issues).
Actually I very well plan to let users create accounts. The usual mail-address & password scheme. But this is optional for nearly everything in the game: You can have anonymous accounts for instant start and as long as you don't lose the startup-key you can use the game indefinitely. You only really have to sign up with mail-address if you want to publish some of your levels.
About the graphic assets: You are right that the 60x60 images would look quite out-of-place on retina displays. Since the program runs with OpenGL rendering which should be fast enough on basically every relevant system, we could indeed switch to 120x120 pixel images. Probably I will do some post-production downscaling to provide smaller images also for devices with less system resources (mobile phones). But the overall approach stays the same: the .PNGs simply contain strips of images, organized from left to right for animations, with the leftmost image being the "base" appearance.
Good to hear, I’ll bake the account flow into the design early next week.
General
Top level menu
About
The "incentive" dialog
Profile (logged out and logged in versions)
Controls
Contextual options
Level info
Level actions
Tiny additional update:
That's it! The biggest task left now are the element animations. There are quite a lot of them. I'll post updates of those in the Graphics and Gameplay issue.
Hi!
I finally got the time to go through your designs in detail and give some sensible answer on the various parts:
Level categories: I am fine with "Adventure". So we would have (as shown in your design already): Fun, Adventure, Puzzle, Science, Work, Speed, Survival, Fighting I would prefer to present them in this order (going from lighthearted to more and more serious)
Level difficulties: "Tutorial" does not really make sense, because the tutorials of the old game varied in difficulty. And the very few "Simple" levels now just do not justify an own level. But "Difficult" really does. So, we will keep Easy, Moderate, Normal, Tricky, Tough, Difficult, Hard, M.A.D. About coloring these, I you can not find a suitable shade of orange for Difficult, I have no problem in shifting the colors. With "Tricky" being bright green then. Somehow this feels no so bad, because "Tricky" is just what could be solved by a casual player after several tries. Everything beyond that starts to need a serious effort.
YamYam debris: OK, lets re-introduce this. If it is only one common setting for all YamYams in a level that is not such a big deal. Actually I also want to re-introduce the speed parameter for the robot. As it is now, the robot is not as fun to use as it was previously.
About account registration. Yes, it is currently widely used practice to just use the email-address to specify the account. I will follow this. I would not even require an account name here. Upon publishing levels, the user may opt to publish them under a pseudonym instead to keep the email-address private.
I very much like your various icons. But I am not sure about how to implement the rendering of these. It seems to me that they are all rather simple vector-shapes that can be rendered with various colors. For these purposes I have 2 possibilities: Directly render them as vectors (which would be a bit demanding on the CPU because of the many vertices), or use the mechanism I already use for the text rendering. I already guess the second is better, but then I need all these icons (including everything on buttons and such) very super-high resolution to pre-process them into a distance-field image (like I did for the font). The mechanism would even allow to make the strokes thicker or thinner at runtime or apply adjustable edge antialiasing.
For the next steps to do, I want to consolidate the work I have already done with javascript and concentrate to improve the following things first:
Level artwork: This is currently a complete mess because the program now just uses the existing graphics in the way it should be organized in the future. If you already have usable graphics, it would be perfect if you could start to push stuff into the game/tiles folder which I have just created to receive graphics tiles in 120x120 image strips (everything .png). You should have the required privileges to do so. You probably need to install a git client if you have not done so yet. To make this as simple as possible, I want to organize the images as follows:
Sound and music: For development I want to just reuse the existing stuff to actually get the program working, but soon I need proper sounds too (I guess this will be Jürgens part then).
Game icons: The game/gfx folder does not contain much stuff right now. Please put game icons there in a sufficiently very high resolution as monochrome .png (like 200x200 for the category icons) . I will need to perform some post-processing to convert this to a "distance field" representation (like I did for the font.png).
For unifying the rendering, I will also replace the big sapphire image directly with vector drawing commands. So the only thing that will be used then are the tiles for the game elements, and distance-field images for all fonts and icons.
Shifted difficulties and adjusted categories: sounds good! (it isn’t worth trying to fit yet another hue in the warm end of the spectrum, it gets too red-heavy). Here’s what it looks like:
Robot speed back: if swamp speed is there, robot speed makes sense. I wasn’t too bothered by the robot being so tough, but obviously with only top-speed it wouldn’t be possible to make easier levels with robots. I would suggest for both the swamp speed and robot speed to have the values “off” and 1 through 10 ( as in the level editor), where 10 is the maximum speed. Also, small tweak: Remember that you adjusted the robot — when it only had one speed — to walk toward where the played moved FROM, instead of where the player is heading? Maybe turn that back so the robot at top-speed is even deadlier, now that we re-introduce the option for slower robots?
By the way! by re-introducing robot speed and 1 yamyam debris, quite a few of the old levels you removed are possible again. (Such as Needful Things).
About removing the pseudonym/author name from the account creation: it makes sense to decrease the amount of steps necessary to create an account. However, this one step of adding a name (call it Nickname to instantly make clear it doesn’t have to be your real name) saves us from quite some additional UI, and saves users from extra interaction and cognitive load. To be precise, by not asking a nickname during account creation: 1. a name would need to be asked the first time you “toggle” a level to be shared, and 2. even for privately created levels, people would like the “by [author]” field in each level to be filled by some (nick)name, not their email address. So probably, by not asking a name in the account creation you’d need to add that name field in the level editor anyway, which makes people more likely to change it every now and then. Ideally people should be actively discouraged to change that name often. Recap: nickname as one extra step in account creation saves us all time + effort. Nickname allows for automatic level authors, users will never have to deal with it in the main UI (unless they go to their profile and manually change it there).
I can provide all icons used in buttons in any crazy resolution imaginable. Aren’t you going to use them more or less the same way as the game artwork? I can easily export them as, say, 200% sized PNGs that will look good on about every display. Alternatively (and probably the best option), we could just use SVGs which would look the best on any display, and you’ll be able to change the colors on the fly (there are a lot of icon-color combinations). Performance-wise this shouldn’t be an issue. I’ve seen countless js apps exclusively using SVGs. Our UI shows about 20 icons on-screen simultaneously, or 30 on desktop monitors.
Alright, I can definitely prep some artwork! Next week I can populate the folder as most elements and some animations are already finished. 2 questions:
So, OK, we will request the nickname at registration. I do not expect too many nickname name conflicts, so the registration should be rather painless. Changing nickname later on: This will also lead to all published levels to be shown with the new nickname from then on. So, exported levels will not have explicit author information.
About icons: I want to avoid using vector graphics in the game, because it will be very cumbersome and slow to make a vector renderer in javascript. For the texts I am using a bitmap-based approach with a very clever way to still get high quality using the opengl fragment shader capabilities (which can offload a huge amount of work into the GPU to keep it from the javascript program). Since the texts letters are so very much like your icons, I will use the same rendering technique for them also - basically just treat the icons as any other letter. For this I make a preprocessing step that generates the necessary images at deployment time. This preprocessing can as well use vector graphics files, because performance is not an issue there. So I guess it would be easiest for you to just provide me with some SVG for the icons and I will merge then together with the font to get these data. Please put these SVGs into the "gfxdesign" folder which was already meant to receive graphics files that are not directly part of the game, but rather some form of raw or design files.
With "morphing" I meant things that I could not handle with simple scaling or rotation, like opening bags or breaking sapphires or the like.
For organizing the files: To keep it simple we can follow your idea to provide single still images for the game elements (a .PNG with 120x120 pixel). When a game element has multiple appearances depending on context (earth, walls), you could provide them in a single .PNG as we already did. I will figure out what is what. The animations are a bit more ticky. The game will run at a designed speed of about 60 frames per second or exactly 15 frames per turn (when the program is not able to keep this pace, it will start to drop frames). So at every turn (each taking 0.25 seconds) there is always the starting situation (consisting only of all the still images of all game elements), then there are 14 animation steps and then there is already the starting situation (again consisting only of still images) of the next step. So basically all animations need exactly 14 frames to serve as in-betweens for the still images (which you could imagine as "key frames"). When the player uses fast-forward or fast-backward no animations will be played at all, but only still images are shown in rapid succession (giving a 15:1 speedup). Following this scheme, it is still possible to provide a kind of "slower" combined animation for acid bubbling and such: Each animation still has only 14 in-between steps and only lasts for 0.25 seconds (including the stills). But you can provide an animation that shows the first half of a periodic swing (from "zero" position to "zero" going through positive ) and also another animation for the second half of the period (from "zero" to "zero" going through negative). Maybe you get the idea - I am thinking about how a vibrating string returns to its center two times in every cycle. Please make 2 animation .PNGs with 14 frames each for such cases.
To keep things simple for the various appearances of the acid pool, we will keep using the overlay to paint the container (has context depending appearance) and the acid (has animation).
If you already have created animations that consist of 15 frames, we can only use them if one of these frames is the still image already (I can ignore this frame at loading time). Otherwise I can not fit 15 in-between frames into the 14 in-between frames of the game engine smoothly. I hope there is not too much work lost by my unclear specification.
Hadn't heard of the distance field technique but it sounds great! If it all ends up in PNGs, I'll export all UI icons in 400% sized PNGs. Artwork at 200%. Here's to performance!
Thanks for the background info on dropping frames and fast-forward. Makes a lot of sense why the initial image in strips of 15 frames has to be the still image. Don't worry about that, I'll change the animations accordingly. All left-to-right, 15 frames per turn, and if possible I'll try to create a great anim for the acid without requiring 2 turns (for the love of simplicity). However, the multi-turn animations should still be supported for the explosions.
Quick update: refined a lot of the artwork again, so in less than a day I'll upload: the artwork set, UI icons, specification for most UI components, and 1-2 animations to test with.
Updated the /game/gfx folder with 3 icon packs in folders with self explanatory names (category, difficulty, menu). Also provided a UI specification sheet with global styling that should cover the majority of the UI as seen in this thread.
If you start implementing the UI, to avoid extra work it's safest to start with anything that's not on this list (as these are the smaller UI todo's I still need to pick up):
Level editor woes...
Hi Charilaos!
I have worked on the level editor and it turns out that I am a bit clueless on what do do with it. In the current version you can start the editor for a built-in level by pressing "e" in the main menu..
The editor is very unfinished and only allows simple piece placement - no level settings yet. Please give it a try to see what I am talking about in the next paragraphs.
I already have troubles to make the program work satisfactory in all possible conditions. I want it to be usable with mobile devices and to keep complexity down, this means it should work with a single-touch interface. This then will work on desktop devices with a mouse without additional efforts, but then only a single mouse button is supported (or both buttons doing the same thing).
While I have managed to work with this restriction in the game itself, this becomes a pain in the level editor. Mainly concerning one detail: Scrolling around in the map. While I can scroll the tool bar by dragging the mouse, I can not scroll the map in this way because this action must result in painting the selected piece. In normal desktop/web programs this could be easily solved by using the second mouse button or the mouse wheel or some control key or whatever. But here I don't want to use all this.
Maybe you have some ideas on this topic? To make the thing even worse, I would also like the program to work with only the barest minimum of key controls. Like in the game: A directional pad, one select button (grab), one auxiliary button (bomb) and an escape/pause/exit button.
If you want to use the level editor nevertheless to work on the built-in levels, you need to do the following: Edit levels by pressing "e" in the main menu. After you are finished, you can press "w" in the main menu to write a printable version of the level to the javascript console (press F12 in most browsers to open this console). Copy/paste the definition into the proper level pack file. If you need to change level settings also for this, you need to modify the level pack file with a text editor as usual. I hope I can build the settings dialogs in the next days or so. When you want to take care of the broken demos, you can check the whole set of built-in levels by pressing "t" in the main menu. This gives a problem list in the javascript console.
That's it for today, Reinhard
It works! And I see. The challenges become quite clear once you fire up the level editor. Part of the problem is of course that on desktop, there is a distinction between scrolling and "click and drag", while on mobile there isn't. I'll jot down a few ways we can achieve the functionality along with a rating for usability. Then you can judge the right balance between usability and implementation complexity.
You've probably come across some mobile websites with Google Maps embedded. It requires 2 fingers for panning around, because one finger is already reserved for scrolling the page. This interaction model differs from desktop because the input methods differ so vastly. This principle leads us to the "fully optimized" model. On desktop: scroll either direction (or press the scroll wheel on certain mice) to pan around. Click and drag to paint. For desktop that's the clear winner. On mobile we'll have to test the ideal way: 1. the method described above with hold-to-paint. 2. drag to paint / arrow keys to pan. 3. drag to pan, have a "sniper target" in the middle of the screen and a "shoot" button in a thumb corner, which you hold to paint in the target spot (while using your other thumb to pan around for painting more). Example above. Usability rating: best possible.
Both mobile and desktop: Permanent arrow keys on screen for panning, click/drag to paint. Low complexity, easy learning curve, but rather cumbersome on desktop and obscuring valuable screen space on mobile. Usability 7/10.
Editing permissions It's been there in the original SY and now it's here too, but I'd recommend against it: users being able to edit built-in levels. I believe the players should only be allowed to create and edit their own levels. Just like it wouldn’t make sense to edit levels shared by other players, editing the built-in levels doesn't feel right. (That's why in the screen designs back in this issue I only included an edit button on the player's own levels.)
Check this out! Go ahead and download Lode Runner 1 from the play/app store (free). It's a remake of the old original that's specifically designed for mobile and it's really well done. Notice 2 things mainly:
Looking forward to this week. Kept the evenings free for artwork improvements and maybe a few level designs. I'll respond to the gameplay issue tomorrow.
Hi!
I did more work on the level editor and I implemented your solution #1 for panning: switching modes. It is not as cumbersome as you would think, because many levels are small enough to fit into the screen. And when working on the big ones, you normally stay on the same spot for longer periods of time.
I have also added the button (bottom left) to open up the menu just like in the game screen. Please let me know what you think about the workflow in the editor. The game main menu is still a pain to use and the keyboard actions to "edit" and "write" the levels to the console are just intended for us developers. In the released games these function will be disabled, as well as viewing demos will only be allowed after a certain time delay.
I will surely check out lode runner to see which kind of controls they implemented. Nevertheless I still like my touch/mouse-based approach to draw the walking path. It feels quite natural on a touch device.
Hi! I have finally tried out Lode Runner. And yes, they did an amazing job in bringing keycontrols to a touch screen. This snapping to the latest finger position is a very clever solution. Still there were quite some situations where the control pad lost proper track of my finger and missinterpreted my intentions. Maybe I could implement something like that as a third option (besides true keys and the path arrow).
Takes some getting used to but I think this'll work! I'll slightly redesign the UI I did for the LE for the menus to be layed out a bit more logically. Any chance you could make the "New Level" working next up so I can really test the LE without having the feeling of ruining the existing levels? ;)
Hello!
As you may have noticed I have completely reworked the main menu to now follow your design for selecting category/difficulty and then the individual level. I have not implemented your preview card on the right side because I want a solution that also works on very small screens. Please try out the newest version and tell me what you think. There is no mouse/touch control implemented for this menu screen, but using the keys already works pretty well.
One more info about key input: I no longer use the "Ctrl" key for anything because that it is also used for various browser functions - especially changing zoom levels.
Now I have streamlined the whole keyboard input to work with just 8 keys like a standard game controller: 4 directions and 4 action buttons: Enter/Space (Affirmative and Grab), Shift (drop bomb), Esc (back), Tab (switch input modes).
I guess I will some day buy an actual game controller to get this working there properly.
Big update I see here, great, I do have some thoughts.
Browsing levels is a breeze now. The level preview really is instantaneous. Seeing a list of levels that are precisely your chosen difficulty or category is very clear. There is one user experience issue however with the sorting. While alphabetical sorting is generally very logical, we might want to cheat in the “Easy” difficulty so we can provide those levels in a hardcoded order that makes sense from a first timer learning perspective.
On the level previews: I purposefully designed those to be actual size and screen-centered (so position nor size changes when entering the level). I get the temptation for a zoomed out view, but planning how to play in such an overview is (cheating and) less fun than discovering by actually playing. I'm eager to see how this will work with the 3-turn countdown mechanism, as described in the first posts of this issue. Another great addition would be the 'live' animations of elements (such as swamp, gem shines and acid) during level selection and the pause menu.
I don’t think people will likely be using game controllers for this so it doesn’t make too much sense trying to align the key bindings - but the new input keys are awesome! I especially like the space bar (after some serious time re-adjusting muscle memory). This works great on Macs, where the Control key is in a slightly different position, and most users would even expect the Command key instead. Wonderfully solved with the space bar.
My honest opinion about this game on small (phone sized) screens is that it doesn’t work. On desktop, controls are tactile and don’t obstruct the screen (together with your fingers), and screen real estate (in terms of how many tiles shown) starts being sufficient on mid-sized tablets. And then there is the browser UI eating up another 10-20% of the already tiny phone screens. And many UI problems arise on phones, not just the bottom-right level details pane in the level selection. The level preview will have the same problem, as does the VCR UI (for replays, demos, undo and single step). The same goes for those “hit shift to drop a bomb” tutorial UI, that normally has the same bottom-right placement as the VCR UI.
Given this, I believe the best option would be to have a minimum screen size, below which you could display a message along the lines of “Try this on a bigger display - it’s worth it!”. For current UI, I strongly suggest 720x720px. To illustrate all mentioned gameplay and UI constraints, here's a scenario on 720x720px:
Later, if live and people love it and crave for playing it on their phones, we should optimize for that experience. That's usually a combination of hiding some elements, moving others (such as key tutorials and VCR), and making smaller versions of some components only on small screens. Even then we need a minimum size, as hell sometimes freezes over: smartwatches are gaining web views these days.
Lastly, one little thing seems unintended. When completing a level, there's no action possible other than exiting to main menu:
Other than that, 3 people over here love the changes already!
Hi!
On the topic of small screens: Of course it is better to have a bigger screen, but I would never prevent anyone to use a small phone. If it can run the game and the user wants to have it that way, I am fine with that. But probably I will do some adjustment of the default-scaling in that case, so that the game will show at least 7x5 game elements: This is the "Mission Possible" format and also approximately the width of the pause screen. In this size, the game is fully functional and even the level editor can be used, although with extensive scrolling of course.
I am still not sure how to do the level-previews. Currently I have no "start" action in the level selection screen, so if the user presses "Enter" on a level he enters the game with the pause menu open where he then can start the game. If I had the level previewed in full scale, there would nearly be no visual difference between the level selection and the game screen. I myself got a bit confused when navigating between these different screens.
And I fixed the pause menu after finishing a game. It now shows also the option to continue with the next level.
Sounds good. The level preview, if at full scale, would look much more reasonable if you implement the 3-2-1 countdown feature, from level selection to game, and from pause menu to game. Additionally, having a transition animation from the game to the pause menu (and the level selection) would further clarify user actions.
The problem with hiding UI (such as the level info panel or steps VCR on the right), is that you might lose functionality. For the provided levels - in that info panel - there is only info + a play button, but for your own levels there should be an additional button for Level Editor, plus a switch button for shared/private. For community levels, there should be a button to favorite/bookmark a level. Fundamentally, if this panel is hidden, but we still need this basic functionality, some other place in the screen would have to make space for those buttons anyway. I think it's still easiest to create the best experience possible for most screens, and in a final stage of development have a look at how to perform a few effective optimizations for smaller screens.
Hi! I've been looking closely at the UI to summarize which things we need to improve.
Regarding polish of the UI: the most notable thing is that many elements appear smaller / more crammed together than intended. Especially the icons — which are rendered below the intended 24px size — don’t look precise as their lines fall in between pixels, making them appear blurred. I updated the UI specification document, with notable changes marked in bold. If you follow these instructions, the UI will breathe some air and look more precise.
Sapphire Yours UI Specification.pdf
A few smaller points that will improve the user experience:
And finally, it's time to show some love for the true first-timers by implementing the tutorial tips. The boxes are 32048px, text is Montserrat 14 medium, white, 20px line heigh, 16px margins left and right. The illustrations (8040px and 172*40px for the arrows, vertically centered and 4px from the left side) are exported and found below:
Best would be to hardcode the walking tutorial to "Basic Mining", the grab tutorial to "Collect by Grabbing", and the timebomb tutorial to "Dynamite". It becomes clear that we need to make an exception for the Easy levels: they should be ordered manually instead of alphabetically to control learning progression. This level pack should start with Basic Mining and the walking tutorial, definitely not with "A box full of dynamite" ;)
Hi Charilaos!
I have decided to no longer hold back our work from the public. Even if not all issues are solved completely, the game is now good enough to be used.
In the last days and weeks prior to this release, I have changed the following things (party due to your request):
What I could not do:
The problem with incomplete animations and missing tiles could have been a problem I already fixed last time. Bascially I allocated the texture buffer too small so not all tiles did fit.
I hope you are not angry with me for rushing the release, but somehow this unfinished state of affairs started to get in the way of all my other projects. And paying for the domain www.sapphireyours.com for 1.5 years already without any use and purpose did not help either.
all the best, Reinhard
Hi Reinhard! So the unthinkable happened after all! A very fine decision I'd say.
Wouldn't expect that sizes and paddings couldn't be defined in pixels. Especially since you managed to render the game tiles pixel perfect, independent of system scaling.
I'll post my list of level updates/improvements in the Levels issue in a moment. If you have some time, they're worth looking into.
Are you still in to tweak some things every now and then? There are only two things really missing at the moment: the explosions still render incorrectly (we once had their animations running more smoothly), and in Safari on desktop sound is missing altogether. If done, I'd like to post a notice that it's publicly available on the old forums, maybe some youtube videos and twitter. :)
The explosions look better now, but I don't really know how to proceed with the sound issue. I have no Apple device myself and can not debug the game on Safari. Maybe you can have a look at the javascript console to see if there are some suspicious error messages appearing.
Reinhard
Intended for all things UI related, to keep these designs and their discussion separated from the in-game artwork.