Yo, it's Wednesday! Here's a round-up of updates from the past week. 23rd to the 25th = three day weekend.
Every Status equipped entity has around 20 stats, all defined directly in c++, and they can be affected by about *45* status effect primitives, also specified in c++. Status primitives are everything from ForceField to FlawedProtection to ClumsyProtection to ExplosiveDefense to ExplosiveDefensePower to.. you get the idea. Extending the status system right now involves doing things like extending this enum and adding to this set of fields.
Now, don’t get me wrong, simple and hard-coded sometimes works great. Usually, it’s what you want to try *first*, and you stick with that until it’s clear that it needs to be replaced by something more powerful. Well, for the Status system, that time is NOW.
Omni and I have been working on a replacement for the Status system that should hit (fingers crossed) master in a few days. Stats are generic String -> Float mappings, there’s a system for adding temporary modifiers to the String -> Float set, there is a resource system that is closely tied to the stats system for things like health / energy / warmth, and, the most exciting part is, it will be driven by lua scripts!
Not only will this allow us to have, well.. sort of more “interesting” status effects like brain reboot and things like that driven by an isolated script and with way more interesting graphical effects, it will allow modders to add additional status effects and, as a side effect, will give modders a place to add persistent client-side data and scripts that affect the player without having to tie into the tech system.
Also, as either part of this update or soon thereafter, I’m trying to work it so that status graphical effects like cold and hunger that affect the screen can actually modify the shader used by the world renderer for some more interesting graphical effects than what we have now.
Recently, we’ve been discussing adding some more capabilities to the Status and Status Effect system in Starbound. There are a lot of interesting things we want to do, but as of right now the Status system is a bit of a pain point in the Starbound codebase.
Instead I primarily spent my time getting the Novakid armors that George showed off last week actually craftable in-game. We’ve got all their tiered weapons designed and ready to go too, they just need to be implemented and balanced.
The Novakids feel so at home in our universe, they could well usurp the Glitch as my favorite race!
I’ve also begun work on rebalancing all the armors that fall into the separator, accelerator and manipulator classes. I expect to spend most of tomorrow continuing on this task, so I’d like to get it to a good place. That said, I have no doubt we’ll need to do some fine-tuning down the line as we continue our playtesting.
Until next time!
I ended up deviating a bit from my work on the lunar base mission today, as I’m waiting on further developments on the new enemy before I go too in-depth with careful placement and setting up the loot distribution. We have some other cool stuff for it in the works, but I’d really like to keep those elements a surprise if I can help it.
So a while back I mentioned that I made some changes to sky to decouple them from the coordinate information. Today I hooked it up to the WorldParameter system so that it could actually begin to be used on Floating Dungeons and stuff. There’s more work to be done, because currently there’s no randomization in this area. But we can put any sky on the outpost worlds now. Here’s an example:
What does this mean, exactly? Previously, some biomes would only appear on planets with higher threat levels, but there wasn’t much relating a world’s appearance and environment to how challenging it is other than the explicit threat level. We’re now grouping the primary biomes by tier in a way that makes the progression of difficulty more logical and encourages players to visit a wide variety of planet types as they play through the game. When a player acquires gear with the appropriate environmental protection (such as heating systems to insulate them from cold environments), they will gain access to several new primary biome types (such as Tundra, Arctic and Asteroid worlds). We’re making sure to have enough variety within each tier to keep exploration entertaining while still retaining a somewhat consistent theme at each stage.
Once a player has completed the game’s progression and can access all of the various primary planet types, they will be able to visit planets with special high-level versions of the biomes. These will include some of the stranger variations like metallic trees/plants, as well as previously unavailable mini-biomes and dungeons. There’s no need to rush or grind to the endgame, but there will still be lots to discover after reaching it!
I’ve also been working on some smaller biome and planet configuration improvements. I’ve made the biome/sub-biome combinations more reasonable, so you won’t find ice trees growing next to pools of lava, and improved the matching of planet types to the distance from their star so you can reliably look for hot worlds in near orbits, temperate worlds in the habitable zone and frozen worlds in the outer fringes.
One big part of the game’s progression will be the ability to access new planet types as your ship and equipment improve. To facilitate this, we’re making biomes correspond with threat levels as you advance through tiers.
'Til next week! ːpizzasliceː
Continuing from part one! In the future these will be shorter and fit into one post, but we're taking on 20 days worth of posts here (and Armagon talks a lot :D).
I did that today. It’s now tied to the steam upload so it should update every time Steam does (ie, nightly).
You can find the documentation here: http://doc.playstarbound.com/
You can navigate around by classes or by namespace, but the front page is mostly blank (because it’s the default doxygen setup).
The bits that you lua modders are most interested in are located here:
http://doc.playstarbound.com/namespaceStar_1_1LuaBindings.html under the namespaces section ( for instance:
Hope this helps!
Also did a few things with the Sky today. I’m currently separating the Sky from the Celestial Coordinate system so that we can give fully featured Skies to Outputs and Instances and the like. Nothing too exciting though.
Remember the late time I mentioned documentation I said I’d eventually make it automated?
I’ve been working on a ton of things lately, instancing and unique world support, world <-> world warping, new world generation types and general world generation fixes, material light sources.
But right now I’m fixing a loooong standing series of bugs in starbound regarding projectile disconnects between the client and server. I’m basically done, and with any luck you will see it in tonight’s update.
If I finish and merge today, I’ll do another post later today that goes into how the fix actually works.
Sorry, I was supposed to do the daily update yesterday and I missed it :(
I promised I would go into more detail but.. it’s late so here’s the very VERY quick version:
Projectiles are now proper synced entities with entity update deltas and everything, and damage is sometimes applied where an entity is not necessarily the master entity. Our old concept of a disconnected entity is gone, and there has been a lot of simplification with other damage and status related parts of the code. Self damage no longer routes through the damage manager, and instead entities can produce arbitrary damage notifications themselves. Damage requests and now also a new thing called *hit requests* can travel over the network before being applied, and there is no longer a need for direct status effect requests over the network. Total change in lines of code: -120
PvP needs lots more work still, but PvE locally and over network should be MILES better.
Projectile disconnect fix is complete and pushed to master. It’s less of a fix and more of a.. near total rework.
Over the past few days I’ve continued my work on the lunar base mission with a nice steady rate of progress with some feedback from Tiy and George along the way. As I’ve stated previously, I don’t wish to spoil any plot details, but I’m okay with teasing a small piece of the environment. You may also notice a subtle new feature that crept its way into the game. Blocks are now capable of casting light.
It can be challenging at times; sculpting out a cave environment in such a way that it looks natural while also keeping the player’s ability to traverse it firmly in mind. That said, I think it’s coming along nicely.
On a side note, yesterday’s upload of the nightly build failed, so if you’re interested in trying out Kyren’s new projectile code, the update only went live a couple of hours ago. Personally, I’ve already noticed a huge improvement!
Area-of-effect projectiles like grenades are hitting and damaging multiple enemies far more reliably. The issue of projectiles outright disappearing when shot point blank into an enemy’s face is gone. If you have a bunch of monsters clustered together and you land a melee attack it now damages all of them as it should, rather than just a fraction. The PvE combat is feeling really good right now. Nice work, Kyren!
Anyway, that’s it from me. Stay classy and good night!
Time to go back to my Devcave. K Bye!
Here’s a little something I’ve been working on… The Novakid will be needing their own armor sets.
Players will be able to upgrade the area, digging power, and other numerical aspects of the Matter Manipulator as well as enabling new harvesting options such as liquid collection. Hopefully, this should make it a satisfying tool in your character’s arsenal and even offer a bit of customization to suit your play style.
As we’ve been working on the progression of the early game, one awkward point that kept coming up is the Matter Manipulator. You’re given this all-purpose future tool, but then immediately replace it with stone age pickaxes because of their superior digging ability. So, for the past few days, I’ve been prototyping a system of upgrades for the Matter Manipulator that should keep it useful throughout the course of the game and give players something more futuristic than hand tools. This is all WIP, obviously, but so far it seems to make more sense both aesthetically and mechanically. Here’s a quick look at the current range of upgrades we’re testing:
Kyren kindly implemented a quick update to our lighting engine that provides far greater control of how a light flickers. Previously the controls were a little vague and it was often difficult to get the precise results desired. It was difficult to get lights doing anything other than dimming and brightening in an largely unpredictable fashion.
Now we have the capacity to make lights pulse, strobe, or flicker erratically as we wish. As a side effect of this update, you may notice in the nightly that any lights that previously flickered currently are not doing so, but I’ll be quickly zipping through them to make them work as intended again in my downtime.
I put a quick video test together with a variation of the spotlights that flickers erratically. I do not advise watching this video if you are sensitive to strobing light effects as I have purposefully used a lot of them in one space simply to demonstrate.
It’s pretty much been business as usual for me the last few days. The lunar base mission is getting to a really nice place, and I’ll be able to start populating it with enemies and loot very soon.
No space left for Omni's post from yesterday on the JSON patching system, so I'll just leave a link here.
'Til next time!