Release v0.4 #1459
Open
Release v0.4 #1459
+35,689
−9,965
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…#1250) Use these 2 map events in Celltags. 604: Checks if the techno that entered in the cell has the same ID specified in the event. 605: Checks if the techno that entered in the cell appears in the selected list in AITargetTypes. - HouseIndex can be customized to focus in a specified house.
…ft as is and add a check for being burrowed
* Possible fix to AircraftTrackerClass range issue * Add credits / changelog
massive overhead elsewhere. at least don't tint twice
- Fix commit 5da5e46 breaking custom tint for AircraftTypes - Skip applying vanilla game intensity changes (invulnerability, flash, airstrike) to VehicleType voxels twice (this is just an optimization, not actual visual change) - Streamline some checks in TechnoExt::ApplyCustomTintValues() and bail out early if custom tint is not applied - Inline functions for checking if AttachEffect/ShieldTypeClass has custom tint
just complementary, hence no changelog needed
… owner change Co-Authored-By: Coronia <[email protected]>
- Condense tinting related hooks and remove unnecessary ones - Fixed a couple of inconsistencies in which tint effects were supposed to be applied to what types of objects - Allow adding to IC / FS tint intensity - Allow enabling parsing of 8-bit RGB values from [ColorAdd] instead of RGB565
maybe solving volkov's problem
* move logicclass::update and teleport away from veinhole * remove all my gamestrings header
Techno with ReloadInTransport=yes suffered from a crash when the transporter's owner is changed (i.e. being mind controlled). This is because it'll move the techno from the original owner's OwnedTransportReloader list to the new owner's, which is actually wrong when the transporter doesn't have Passengers.SyncOwner=yes. Attempted to fix this issue and unified the conditions of ReloadInTransport Co-authored-by: chaserli <[email protected]>
this should fix #1443 --------- Co-authored-by: Trsdy <[email protected]>
…t. (#1454) `Flamer? -> `Flamer` A very minor error that affects users' reading and comprehension. It made me wait for two months without seeing anyone fix it. So, I decided to take care of it myself. That's all.
Warhead is fully detonated needs ReflectDamage.Warhead.Detonate
Co-authored-by: Aephiex<[email protected]>
|
Nightly build for this pull request:
This comment is automatic and is meant to allow guests to get latest nightly builds for this pull request without registering. It is updated on every successful build. |
If you don't know it yet: Phobos has an active Chinese tester group which helps with new function testing and crash/desync hunting. Now that 0.4 is on the pipeline, I'd like to credit these players for assisting Phobos development
[Ares](Ares-Developers/Ares@1b8b66f) marked its initialpayload already created for units spawned by trigger actions because of the mutex.
not tested yet
Fix the problem caused by the incorrect return address of the hook in b37 repair. Skipping repeated check. And avoiding RE caused by uninitialized different data in EBX of different players.
Synchronize document formatting and link fixes from the develop branch
Metadorius
force-pushed
the
release/v0.4
branch
from
5c47b68 to
2f47375
Compare
…ls. (#1516) Phobos previously added a rule to select weapons based on `[Warhead] ► Wall= (bool)` but `[TechnoType] ► NoSecondaryWeaponFallback= (bool)` cannot disable this rule this causing the Soviet Siege Chopper to use the `160mm` weapon to attack walls even when not deployed. --------- Co-authored-by: Starkku <[email protected]>
Synchronize the community navigation and personnel changes from the develop branch to the release version of the documentation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.