To get more money, simply raise the fee of the park when people are coming through the entrance gate to increase your profits. Submitted by: aarondhartley Get More Money You can make a huge profit if you price appropriately, since umbrellas are a cheap investment on your end. Place an information kiosk near the entrance to your park so that guests will purchase an umbrella as they enter when the rain is pouring. That said, this whole idea of doubling up on flags stems from my own excitement for implementing it with the current framework or impatience of not wanting to wait until duncan's extended data idea is implemented.When it is raining, your customers will happily pay outrageous rates for umbrellas, provided they have enough money to afford the accessory. I don't have any problems doubling up a flag when possible to save using the last bit - I have my sights set on using it as the supports flag. For a broader scope, the HAS GREEN LIGHT flag is only set on stations (as far as I know) which would open up the ability to flag the speed setting for every track piece, something that would benefit dark rides, train rides, and scenic railway coasters. For a narrow scope, the HAS GREEN LIGHT flag and CABLE LIFT flag will never be set on booster nor brake elements. Speaking of backwards compatability and flags, there's one unused bit in the flags2 field, but there's also some flags a unified speed setting would not interfere with. The 255 value would act as a flag, but flagging what, I do not yet know. I am also pondering the utility of making the unified speed's upper bound 254 instead of 255.
It will tell me with relative certainty if legacy backwards compatability will be a concern. The script I expect will take a week to test all 975 parks. I've begun scraping all NEDesigns parks uploaded after 1 January 2017, the day boosters were merged into 0.0.6 develop. If they don't occur, then there's little reason to support the legacy behavior. I think it is possible to scrape all of NEDesigns and Deurklink parks since the introductrion of the booster track type and use a slightly modified version of OpenRCT2 develop to determine if any of these merges occur. This is not ideal, because it adds complexity to support legacy and unified speed/power, but it would assuage fears of breaking coasters since OpenRCT2's introduction of the booster track piece. In particular, the booster power setting is not consistent across ride types, so any simple application of a ride type's booster power to its boosters will cause problems if a coaster merges onto a booster of a different type than its own. it may be useful to use the MSB of the field(s) as a flag for determining if new behavior is enabled per-track piece. Thinking forwards to a few other features. A non-giga non-junior coaster has to merge onto a giga or junior coaster's booster.A junior coaster has to merge onto a different ride type's booster.A giga coaster has to merge onto a different ride type's booster.It has come to my attention this has the potential to break coaster booster speed, although the conditions for this are very rare:
0 kommentar(er)
