[img]http://i.imgur.com/8VdQZjl.jpg[/img] Afternoon Survivors, Another status report tuesday comes around, this time with Brian, Mirek, and Viktor giving us a bit of info on subjects such as the new player controller, new server browser, connection and inventory issues, and an update on blocker/prio issues for 0.60 going live on Stable branch. [b]Contents This Week[/b] [list] [*]Dev Update/Hicks [*]Dev Update/Mirek [*]Dev Update/Viktor [*]Community Spotlight [/list] [h1]Dev Update/Hicks[/h1] Greetings Survivors, Its that time again - so lets take a look at last weeks blockers on 0.60 experimental, talk about their status - and outline the current priority issues on the road to 0.60 stable branch. [list] [*]Characters prevented from logging in once connected: Fixed [*]Client stuck on black screen after launching PC in some configurations: Fixed [*]Weapon Attachments twitching randomly out of sync with weapon and player hands: Fixed [*]Clearing weapon chamber deletes the chambered round: Fixed [*]Known issues with "infinite ammo": Fixed [*]Known causes of server crashes: Approximately 75% resolved - remaining issues are under investigation [*]Server Memory Usage issues: In progress [*]Restock values affecting global economy: Fix in testing [/list] The last entry specifically is one part of the ongoing development of DayZ's Central Economy that those who like to dig into those values might enjoy knowing a bit more about. The CLE for DayZ is an interestingly complex tool that manages over 3 million potential spawn points, covers all potential tag and category classifications for items, and structures, is dynamic enough to be adapted to new maps for mod authors in the future, in some cases monitors items not only in the gamespace but also within player camps and player inventories. Each item in DayZ has its own values configured dynamically within this tool covering: [list] [*]Minimum Amount: Bottom end point in which the system will begin respawning once quantities drop below [*]Nominal Amount: Targeted operating value in which items respawning at the minimum point will respawn to [*]Lifetime: Duration the item can be persisting in the world before being cleaned up to free up space for new items [*]Restock: Value used for rare/controlled items to ensure that if they fall below the minimum they do not respawn in bulk and allow loot cycling of rare items [*]Tiering: Regions of the world in which these items are allowed to respawn [*]And quite a bit more [/list] The CLE is an integral component in DayZ gameplay, and has evolved throughout the Early Access period thanks to us being able to observe raw data from the Experimental and Stable branch servers. DayZ Mod had a very basic, rudimentary trigger based spawning controlled via script and having to populate no more than around 10,000 potential points - only spawning within proximity to players. DayZ spawns globally, and has evolved to allow more and more precise and complex control over when/where/how much/etc and we continue to iterate upon it, constantly trying to find that right point in which we offer a struggle to survive, without allowing abuse or making the experience *too* punishing. For .60 we're hoping to have the restock values functioning properly for the first time on controlled high end military gear, and pending testing on experimental branch we'll see if this value will function properly enough to allow us to use it for the entire economy - potentially creating points of shortage / supply & demand rotating throughout the servers life. As always, testing and iteration will tell - but Peter and I both are very excited about the possibility here. [b]0.60 Build Milestone Goals:[/b] [list] [*]New Renderer: Implemented [*]Randomized Attachments & ItemsRandom: Implemented [*]New Reload Mechanics: Implemented / Iteration on jamming mechanics in test [*]60 Player-per-instance: Implemented and pending final call on server performance [/list] [i]- Brian Hicks / Creative Director[/i] [b]For the full Status Report, please use the following link: http://forums.dayz.com/topic/233988-status-report-07-jun-2016[/b]