-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
D2k build and charge times and game speed #18051
Comments
When I started "fixing" the build speeds I found trace references in the rules and eventually tracked down the PRs responsible for the current values - #9453 and the related #9106. With that in mind I am creating these "Documentation" issues to try and document as thoroughly as possible the decisions that are being made and how and why changes are happening to D2k, so if anyone needs to check in some years it's all here. So remembering all the relevant information from the original post, here are the raw values from TibEd for future reference: Buildings
Upgrades
Units
*On Normal speed. |
Keeping with the double speed idea and the knowledge from the original post that support powers share the timing pipeline with producible actors and using the Dune 2000 in-game clock for timing, we also get:
*On Normal speed. |
It has recently come up on Discord that our build- and charge-times may not be true to the original game's times.
After some testing with Dune 2000's in-game mission timer (details in that same discussion) we agreed to set a baseline for the game speeds where our Normal speed would match 2x the "normal" speed (as defined by the in-game clock) of the original game - link to Discord.
People who want to play on the original's Normal speed can play on our Slowest speed, which happens to be half the Normal speed, so should match the original perfectly.
With that relation set, we can now tweak our unit/building/upgrade build times, ability/cloak/support power charge times, weapon reload times, projectile and unit movement speeds to exactly match the original.
Important things to note:
900/x = build_time_in_seconds
, wherex
can be directly taken from TibEd:(Explanation also here - WW games run at 15 ticks per second so that's 900 ticks in a minute).
So in ORA the build times would be simply need to be transfered from TibEd using
25*900/x
.Edit: Final formula used is (900*25)/(2*<actor_build_factor_in_TibEd>) = <openRA_ticks>, or
11250/<BuildSpeed> = <openRA_ticks>
.Unknown.Long48
property in TibEd. It uses the same formula as actor production.Adding a tracking list of things that need to be fixed here:
The text was updated successfully, but these errors were encountered: