This week is another week of typical bug fixing, so I thought we would make a one-time change of style and do a day-by-day account of what exactly that means for us.
We had a typical day of bug fixing for the most part. After our weekly Monday meeting, where we discuss the development plan and the Friday Facts plan, everyone settled into the normal bugfixing work, which boils down to something like this:
Can this be changed through a console command without breaking achievements?
Negatory
Added attack modifier setting into the pollution section in the map generator. This modifies how much pollution is consumed by biters attacking. (default is 50% for deathworld presets)
I assume this applies to existing games?
Existing death worlds will still remain at the default 100%
The mod should check, arbitrary limitations like this just restrict otherwise creative and interesting uses of mods.
You can arrange the teams before the event starts now, but this will still be useful for if someone joins half way through.
There is a internal function set_player(player, team, mute)
So the function will look something like this
/c set_player(game.players["Klonan"], global.pvp.config.teams[1], false)
The number of the team is determined by the order in the setup GUI.
If the last parameter mute is set to true, then it won't print a message when the player is set to the team.
So with 12k+ automatic crash reports, how does the team handle sorting and evaluating them, and associating them to bugs?
Is it just like a sort exception type, or exception type + location (function or instruction address, etc.)? Any other criteria used to make that manageable?
We have a script that sorts them by platform and by specific crash reason, so we get a list of most common problems for that platform.
Why does the job posting want iOS experience?
Its an optional plus, its good for if we ever want to look into an iPad/iPhone port of the game.
I keep reading the FFF's and see the beta number being already up at 0.17.8...
I'm patiently waiting for 0.17 to be released as stable... hnnng... any ETA on that?
Edit: I went ahead and caved in.. Am now part of the cool 0.17 gang!
Stable? Probably not within another 6 weeks or so.
This past weekend we beat our previous record of most simultaneous players with a peak player count on Steam of 22,457 players, and no doubt another couple thousand playing the non-Steam version.
We have a proportionate number of bug reports coming in for macOS systems, and we don't have a dedicated developer responsible for the problems. The Job listing is still up on our website, and we have the desk...
Read more!Linkmod Total Automization
This mod is the only one I'm currently are of that has RTS aspects, there are probably more, have yet to try it.
The Robot failed, here is the link:
Webm/Mp4 playback not supported on your device.
So we finally released the 0.17 experimental this week. (patch notes) Hooray :)
Fun fact: The release script failed to post the release announcement on Steam and Reddit and we were wondering why. The reason is that the patch notes were so big, that it exceeded the maximum post size (40k characters). If this isn't the indication that we should split our releases into smaller chunks, than nothing is :).
Code wise, it is clearly the biggest release, and the amount of bugs we have to go through correlates with it. In other words, there are tons of bugs of all variety. We want to fix everything eventually, but it will take time, so we had to ...
Read moreWe have been playtesting a few days this week. There were some things we had to fix on the fly, but we still were able to play quite a lot, so I would say that it went surprisingly well. We have been able to get 3 multiplayer bases into a late game stage.
In 0.16 one of the the map starting settings related to pollution is called Dissipation rate. Its tooltip says "Control how f...
Read more
devtrackers.gg