Barbie wrote:That's not true. The value of "ReducedDamageType" is "All" but the value of "ReducedDamagePct" is zero.
Yes because he was clueless and his idea was another one wrong applied in practice.
Gustavo6046 wrote:To avoid mismatches and the like...
when it applies the v2 patch.
The fact is as I have explained already, a MH game/server runs properly with CONFORMED files (using sanity checks and small adds) and such a conformed file will never do any mismatch
as much as there is not a single problem with FINAL functions (we might have X GENERATIONS of finals) in such case. I won't deny that conforming has compatibility limitations in several cases but mainly wrapping things is doable.
And time for evidences ( for not talking like not having a clue 90% about what I'm saying ) we do have a player using UT v436 properly playing a Network game joined in a UT v451b server. Engine files are different from 436 to 451b and such session playable, but... we have this said "compatibility" - it's 50% in reality, because can be problem in reversal, with 451b player joined to a 436 server (if it's able to join...) because 451b player is expecting those add-ons which a 436 server won't have - modifications a la UTPG.
Okay, THIS map now - and not only this map. Due to a constant dumbness toward movers I might be willing to drop an auto-fix right in Engine file for preventing to load another ServerActor (with another iterations charge) or replacing a base function using XC_Engine. Way to many maps are messed up here... and if a problem will occur a private patch for map will solve the bad occurrence... probably code will deal with "class.default..." and so on... and using logs of course for showing exactly who does what.
As for some ScriptedPawn love, I think I will need to open another to do list regarding to mapper "preferences" and resetting all dumb editing like:
- screwed cylinders;
- invalid orders generating null states;
- various reduceddamage types;
- combat variables out of normality;
- unexistent real skill - I know what I'm saying here;
Including a fix for default pupae - running without to eat dusty ground - pre-pivoting it higher automatically. Etc, etc.
The only major problem is fixing some pathing task directly in stock as long as we do have holes:
- default Scout is not for run-time - another Scout breaks compatibility in a way - or default Scout needs... some 3 lines of code added;
- if we have solved Scout problem I cannot be sure about creating reachSpecs because those natives probably won't work out of Editor as long as nothing is declaring them for a run-time specific task - shame, EPIC...
- etc ?