Alpha 2 is out! This time we’ve added tons of modding support, butchery and cooking (including cannibalism with attendant psychological effects), an ambience sound suite from Alistair, and a pile of other goodies including various oft-requested features.
Here’s the video with the info:
The changelog has a full accounting of changes (read between builds 334 and 363).
Anyone having trouble with their download – please see this forum thread.
Cheers,
Ty
It’s finally here – Alpha 1!
Everyone who has the game got this on January 27th via email. If you didn’t get it, more info here.
(Mac users: Please install the Mods folder alongside your app folder, not inside it. This will be rearranged for next build, but for now Mods needs to be there. Also, if your mouse right-click isn’t working, go fullscreen.)
This version brings a host of improvements on the venerable build 254b from last November. Take a look:
The game is on sale at rimworldgame.com.
Here’s a rundown of the new features and changes:
Resources no longer vanish into a magical storage number in the sky. Everything in the game is now present on the map at all times.
One nice natural side-effect of this change is that your colonists will no longer starve if they have a huge food reserve but no nutrient paste dispenser. They can eat the raw food right from the stockpile – though it’s not efficient, and they hate eating raw potatoes. Also note that animals will sometimes eat food out of your stockpile.
Putting everything on the map required re-jiggering a lot of existing systems (which is why we did it now, so we won’t have to re-jigger even more systems to do it later):
There was a janky tutor before, but he basically ran on a rail and told you the same things every game, whether you needed to know them or not. The new adaptive tutor is much smarter in providing only the information players need.
The AT watches everything you do and keeps an internal database of how much he thinks you understand various game concepts. A concept is something like, “you can zoom the camera”, or “you can capture enemies by doing X”. He also watches what’s happening in the game, and works out a measure of how much you need to know each different concept at the moment. And, in his database of concepts, each concept has a natural priority. For examples, camera movement is considered more essential than opening the wiki.
Finally, the AT keeps track of the player’s “relax desire”. This is how much the player probably doesn’t want to see another tutor message right now. People only want to absorb information so fast, so we don’t want to overwhelm. Relax desire peaks just after a message appears, and falls off over time.
Evaluating all these together, the AT shows you training messages if the combination of their priority and immediate need-to-know exceeds the player’s desire to relax. The final outcome is:
There’s more to do to perfect this guy (like making messages point to elements on the map or on the UI), but so far I think it’s a great improvement on the old non-adaptive tutor.
Also, the AT’s database of player knowledge is now saved separately from maps, so it will stay between games. To reset it, delete Knowledge.xml in your RimWorld saves folder.
Modding support is started but not finished.
Many of the definitions in the game – some buildings, all sounds, hair, training concepts – are now exposed in a Mods folder, in the Core mod, in editable XML files. However, some data is still not exposed, like most Thing properties (especially the ones essential to making weapons or plants), race definitions for making animals or alternate humanoids, trader profiles, storyteller tunings, and so on. In addition, there’s not yet a system to install, activate, and deactivate mods. All you can do is destructively edit the core files.
Development tools have been added to the game. You can activate them with the “development mode” checkbox in the menus. For more info on these, check out the basic RimWorld modding document.
This system will be finished in a future release. Hopefully soon, because I grew up as a modder and can’t wait to see what people will do modding RimWorld.
You’ll notice some beautiful new art for our menus. Thank Ricardo Tomé, Portuguese digital painting expert, for spicing up the menu backgrounds and giving some life to the AI Storytellers.
The character art in game has been redone by Rhopunzel, combined with some fun color-randomizing code by yours truly. So pawns can come in a variety of body shapes, skin colors, and head shapes.
And that’s just when they’re naked. In addition, there is a new apparel system. Characters can wear multiple layers of clothing, and the clothing itself is randomized. So you could have a guy in a green T-shirt. Or a dude in a white T-shirt, with an armor vest and a tan duster. The number of combinations is nearly infinite. Finally, hairdos are now randomized as well.
Currently, they’re just randomized for everyone and cannot be changed. In future, apparel will be fleshed out systemically, and you’ll see different clothing and hairdos for people from different cultures. One pirate band will wear all leather and spiky mohawks. A nearby tribe will send raiding parties in animal skins with tribal hairdos. And you could enforce an all-pink-clothes-with-pink-afro colony uniform if you wanted.
Overall we’re looking to get to a point where colonists and pirates can be characterized and recognized just by looking at them. The tools to do that are now in, but they’re used haphazardly. Upcoming versions will have characters spawn with proper clothing and change their clothing as appropriate. Clothes will also help protect characters, affect their movement speed, and so on.
Tons of things have been fixed and tuned, including recruiting chances, storyteller difficulties, and so on.
If you got the Name in Game or Backstory in Game pack and had your content approved before Friday or so (when I content-locked the Alpha for final stability testing), your content will be in the game. It’s quite refreshing to have a nice deep pool of content to draw from. There aren’t a massive number of backstories – you can become familiar with individuals if you play a lot – but there are enough that the game isn’t under pressure to repeat anything.
Also, the options menu now has an “encouraged spawn list” of names. Put a last name on here, and the game will prefer spawning characters from this list. So you’ll want to put your own name on the list, and perhaps those of your friends, and watch yourself spawn in!
Great thanks to all the testers and the two creative rewards moderators who helped make this happen. Have fun and watch out for the raging muffalo!
Tynan
And, the last of the lineup, Phoebe Friendly!
In other news, I’ve been working hard on the January release, which is healthy and on track. To see what I’ve been up to, check out the changelog.
Here’s the second portrait of the lineup, Randy Random!
Portuguese digital painter Ricardo Tomé has been working on key art for RimWorld. Here’s his portrait of Cassandra Classic (click to expand).
These portraits will appear in the menus. We’re also looking at having them pop up in-game when the storyteller takes certain actions, to remind players just who they’re dealing with. I’ll post Randy Random later.
Hey, all you people who got the name-in-game or backstory-in-game rewards! We’re finally ready to accept your wild and wacky creations! Web wizard Hypolite has created an online system that will allow you to add your character names and backstories into a database. Each time we release a new version of the game, I’ll pull the data from the database and put it in the game itself.
RimWorld Creative Rewards System
As a reminder, you should keep the Creative Rewards Guidelines in mind while coming up with your creations. I can’t wait to see all the wild ideas you put in.
Also, I’m still looking for creative rewards moderators. If you’re a solid, clear writer and interested in helping, please contact me. Thank you!
I’m happy to announce that we’ve got eminent pixel and game artist Rhopunzel working on the in-game art for RimWorld!
Rho has worked on several awesome indie games. The most recent was Starbound, with pieces like this scary skeltal dragon or this crunchy mech. Before that, Rho did pretty much everything for Gnomoria.
Some people have asked how much the final art will change. Up until now, I’ve done all the art in a simple, iconic style. Rho will be working in a similar style (though at a much higher level of ability). We’re sticking with the vector look because it satisfies RimWorld’s design constraints very well. The goal with this art isn’t just to look good – it must satisfy a specific set of design goals as well.
First, it has to convey a lot of complex gameplay information in a really intuitive way, even when compressed to a tiny space on-screen. For example, looking at a character will tell you:
Packing that all into a space as small as 32×32 pixels and making it look good is tough!
Second, it has to balance abstraction with specificity. If it’s too abstract, people can’t intuitively understand what’s going on. If it’s too specific, it fills in too many gaps so players have no room to subconsciously interpret what’s happening. We need to leave room for players to interpret, because player intepretation is the real engine of game-driven story generation.
Third, it has to be lightweight in content, so it runs and loads quickly, can be iterated quickly, can be modded easily, and can be expanded to a wide variety of objects and characters. We’d rather have 100 kinds of characters with 3 frames of animation each than 3 characters with a hundred frames each. Because what matters is the final experience of the game, which in the case of RimWorld is best served by variety, not detail.
I’m happy to say Rho has been rising to the challenge. We’ve already been passing pieces back and forth and watching the style develop. Here are a couple shots of random colonists in various mixed outfits. Yes, one of them may be naked.
Hey all, just a quick update on what I’ve been doing. In short: audio and modding.
I’ve been working on the system that our audiopath Alistair Lindsay is going to use to define the sounds for the game. Up until now I’ve created simple sounds myself from free source files found at freesound.org. The code would then just play the appropriate sound file directly when triggered. This filled the gap enough for my own pre-alpha purposes, but now that we’re getting serious about audio it’s clear something much more is needed.
Al wrote me an awesome document describing the kinds of features he needs in an audio authoring system and I’ve been working on getting it done for him. He’ll be able to define sound containers that the game will randomly choose between (like creating several sounds for a punch hitting someone). It’ll avoid repeating sounds frequently, if desired. Loopers can now define a maximum number of voices, so if there are 40 fires near the camera, Al can choose to have the player only hear the closest three of them, fading between sources as the camera moves around. Soon I’ll be doing a loop-shuffle system where he can define sounds in a container and the game will crossfade between them to create one long sustained sound. So, there might be several short samples of fire burning that the game will shuffle up into a never-repeating fire mixture.
After that will be the really fun and hardcore stuff – tying sounds to game parameters. So we might tie a fire size parameter to some processing in the fire sound. It might fade from a small fire sound to a big fire sound, or change EQ settings or volume as it gets larger. I’ve created an editor to define these things while the game is running, even adding and changing sound files without stopping play.
This progress isn’t just about the audio, either. This editor generalizes to anything you can define in the game. It is the in-game mod editor. Some day it’ll be usable to creating new weapons, configuring them, creating audiovisual content for them, and playing with it all while editing it without ever closing the game. I’m hoping that a really powerful modding interface will encourage modders to create lots of new content. Here’s what it looks like now after a week of development:
Another fun detail is that this interface with line-by-line editing and collapsible objects is really modeled after the property editor in UnrealEd, which I used for many years at Irrational and before. It’s funny how some things stick with you and you end up using them where you might not expect.
I don’t know when the next public content update will be. There is some pretty heavy technical lifting to do over here – I’m doing this audio/modding system and planning to switch the game to use Dwarf Fortress-style on-map stockpiles. It could be a little while.
Build 254 is out!
This is a small update on 250, but it has some important fixes. Most importantly, the storytellers are balanced out and fixed. They won’t send advanced raiders with sniper rifles and charged-shot weapons so early any more. I’ve also resolved a bug that caused story events to stop coming in long games.
There’s also a new storyteller called Chill Callie Classic. She runs the same algorithm as her more uptight sister Cassandra, but at a more relaxed pace for players who don’t want the intensity of Cassandra but don’t want to go all the way down to Phoebe.
Here’s the full changelog.
Everyone who has the game should be getting an email update about the new release. Alternatively, you can just re-use the private SendOwl download link you already have.
All right! It’s out!
Backers whose payments succeeded in the first day should be getting emails with links to download the first public pre-alpha, build 250.
There is one bug you should know about - sometimes the game starts and the screen is black. To work around this, just move the window a bit.
If your payment was not successful the first time around, you have two options:
If you want to read the changelog, find it here. Discussions, suggestions, and bug reports are always welcome at the Ludeon forums. I’m also on Twitter.