Nielk1 wrote:ZA, you should indeed make a version of the Hadeans fit for VSR, but it should lay on top of FE or some such. At least, that is how I figure.
The idea is to make VSR compatible with stock for ease-of-use reasons, as it is shown that making mods launch with a special shortcut adds an extra layer of inconvenience that tends to dissuade people from playing that mod (ie: they have to restart BZ2 to turn the mod on and off). If Hadeans are implemented in VSR, then they will be able to co-exist with other assets in addon w/o causing bad assets in stock 1.3 games (they will also use a workaround to a bug which causes asset checker fails when a non-stock pilot ODF (ie: evpilo.odf, cvpilo.odf) is created.
As well, they will be balanced with VSR -- which means that the hadean assets will have further development or refinement done to them. At this point, Race Project or FE can use those assets if they so choose. I will even let these mods use ISDF/Scion VSR assets as well since the idea of VSR is to improve upon the implementation of stock 1.3 (in fact a lot of the things implemented for VSR were planned for a 1.2 mod called ZST+)
If Hadeans are implemented in VSR, then they will be able to co-exist with other assets in addon w/o causing bad assets in stock 1.3 games (they will also use a workaround to a bug which causes asset checker fails when a non-stock pilot ODF
The bug is that if if anyone creates an (#spilo.odf) file, where # is any letter or number, the asset checker will detect this and cause asset check fails, even if this asset has not been created before or is not actually being used in game (so simply creating a cspilo.odf file will cause asset check fails in stock 1.3). This causes mods that introduce new races not to be able to co-exist with stock 1.3.
The workaround to this behavior is to use a non alphanumeric character as the race prefix, ie: $spilo.odf, #spilo.odf, etc. The downside to that is that I have not found a way for the Race's Name to be displayed, the faction simply says 'Other' -- there might be some other bug-a-boos that crop up from using such an unsupported behavior, but it's the best work around that I can think of to resolve these asset check fails if trying to make everything compatible with stock 1.3.
EDIT: Fixed mix-up between 's' and 'v'.
Last edited by Zero Angel on Thu Mar 01, 2012 3:32 am, edited 4 times in total.
MrTwosheds wrote:Isn't there a file you can add that specifies new files to asset check? would this help?
Its a forced check list, not an anti-check list, for obvious reasons.
Is the actual content of the pilot ODF checked? If not we can just throw a full set of pilots into stock, but I have a feeling it is actually fully checked.
The workaround to this behavior is to use a non alphanumeric character as the race prefix, ie: $spilo.odf, #spilo.odf, etc. The downside to that is that I have not found a way for the Race's Name to be displayed, the faction simply says 'Other' -- there might be some other bug-a-boos that crop up from using such an unsupported behavior, but it's the best work around that I can think of to resolve these asset check fails if trying to make everything compatible with stock 1.3.
Dis be bodgery... What you should be aiming at is getting the VSR assets included in a stock release, at the end of your development, then you won't have any Bad assets issues. What you need is a temporary workaround for your development phase.
The workaround to this behavior is to use a non alphanumeric character as the race prefix, ie: $spilo.odf, #spilo.odf, etc. The downside to that is that I have not found a way for the Race's Name to be displayed, the faction simply says 'Other' -- there might be some other bug-a-boos that crop up from using such an unsupported behavior, but it's the best work around that I can think of to resolve these asset check fails if trying to make everything compatible with stock 1.3.
Dis be bodgery... What you should be aiming at is getting the VSR assets included in a stock release, at the end of your development, then you won't have any Bad assets issues. What you need is a temporary workaround for your development phase.
Same thing DarkFox did for his Hadeans. Which reminds me, did anybody ever recover them?
* modified towers/spires around AI base.
- reduced number of towers/spires surrounding AI base for standard AIP's
- increased cost of towers/spires from 15 to 50/75
- added code to boost scrap for tower/spire team when scrap boost is given to AI team
- reduced scrap supply for tower/spire team
* siege tanks
- reduced limit of siege tanks to 2
- reduced damage done by cannons on AI siege tank
* tweaked AI hover units
- stopped wavering
- reduced distractability of human team units
* removed siege tank from DM vehicles
- this allows last Destroyer to be selected
* fixed button 1 of advanced options not highlighting
* adjusted some initial difficulty settings
please leave some constructive feedback
If given the truth, the people can be depended upon to meet any national crisis. The great point is to bring them the real facts - and beer.
Abraham Lincoln
Battlestrat, FE, G66, In The Shadows, Starfleet, Uler, & ZTV