Loading...
  OR  Zero-K Name:    Password:   

Post edit history

ZK Developer Support of AIs

To display differences between versions, select one or more edits in the list using checkboxes and click "diff selected"
Post edit history
Date Editor Before After
1/24/2017 9:52:40 PMCHrankAdminDeinFreund before revert after revert
1/24/2017 9:49:19 PMCHrankAdminDeinFreund before revert after revert
1/24/2017 9:48:56 PMCHrankAdminDeinFreund before revert after revert
1/24/2017 9:48:33 PMCHrankAdminDeinFreund before revert after revert
Before After
1 There is currently no working version of spring for zk. All there is to do is choosing from one of the development builds to keep the negative impacts to a minimum. Because of this, zk doesn't use the latest version of spring which means bugs can't be properly debugged either, as some of them have already been fixed in newer versions and the code has changed. 1 There is currently no working version of spring for zk. All there is to do is choosing from one of the development builds to keep the negative impacts to a minimum. Because of this, zk doesn't use the latest version of spring which means bugs can't be properly debugged either, as some of them have already been fixed in newer versions and the code has changed.
2 \n 2 \n
3 Once we actually arrive at an engine version that could be called stable, we should announce any changes as you say. I'm actually hoping for a new Spring 91 around 104 or 105. But in order to arrive there, we'll have to help the spring devs by letting them know about our issues. The most efficient way to do that is to take a step backwards and use the latest dev builds. This will probably cause even more crashes/lags/desyncs than the current versions, but those bugs won't find themselves. 3 Once we actually arrive at an engine version that could be called stable, we should announce any changes as you say. I'm actually hoping for a new Spring 91 around 104 or 105. But in order to arrive there, we'll have to help the spring devs by letting them know about our issues. The most efficient way to do that is to take a step backwards and use the latest dev builds. This will probably cause even more crashes/lags/desyncs than the current versions, but those bugs won't find themselves.
4 \n 4 \n
5 Our current "player base" would probably hate being experimented on, but DeinSteamDreams require a stable and well tested engine, not some dev build. AIs breaking is a side effect of those experiments. 5 Our current "player base" would probably hate being experimented on, but DeinSteamDreams require a stable and well tested engine, not some dev build. AIs breaking is a side effect of those experiments.
6 \n
7 \n
8 This is all just what I've picked up from how the engine has been getting updated lately and not representing @GoogleFrog or any actual dev's thoughts.