-
Notifications
You must be signed in to change notification settings - Fork 62
/
Upgrade Guide.txt
62 lines (43 loc) · 2.73 KB
/
Upgrade Guide.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
This document contains information on important steps that you might need to
take when upgrading Game Framework. If you have issues that are not covered
by the below then please get in contact via our forums at
http://www.flipwebapps.com or send an email to me directly on me a mail
directly at [email protected]
Check the latest version of this guide online at:
https://github.com/FlipWebApps/GameFramework/blob/master/Release%20Notes.txt
GENERAL UPGRADE NOTES
- Before upgrading always take a backup copy of you project so, incase of
problems, you have a working baseline and can refer old settings.
- Delete the old /FlipWebApps folder before upgrading to cater for possible
conflicts.
- Read the release notes for an overview of changes.
VERSION UPGRADE NOTES
v5.0.4
Networking functionality is removed due to being deprecated and removed by Unity. If you need this functionality please copy out from and older versions
v5.0.1
There are a few improvements relating to Game Actions that may need attention
- To allow additional options, Game Actions targets are now made selectable.
Please review the target of any existing Game Actions is correct in your project
- GameAction and GameCondition API improvements. Note the following changes that
you might need to rename for:
InitialiseCommon() -> InitialiseInternal(Monobehaviour owner)
EvaluateConditionCommon(MonoBehaviour monoBehaviour) -> Evaluate()
EvaluateCondition(MonoBehaviour monoBehaviour) -> Evaluate()
PerformActionCommon(MonoBehaviour monoBehaviour, bool isStart) -> ExecuteInternal(bool isStart)
PerformAction(MonoBehaviour monoBehaviour, bool isStart) -> Execute(bool isStart)
Owner property exposed for access to containing Monobehaviour
- GameActions are now upgraded to support new target options . Please check
any target property is still correct in your project and if need be reselect.
v5.0
This version introduces the concept of conditions and actions which improves on
and makes redundant several existing components. Some of these components
remain in place with deprecation warnings, others have been removed / rewritten
due to not being compatible.
- Several of the old EnableBasedUpon[GameItem] components have been removed as they
were incompatible with the new API. You should replace these with ConditionalAction
components, add the action that you want to enable / disable a GameObject based upon
e.g. Player Score and then as Actions add Hierarcy->SwapGameObjects
- All Old Colliders deprecated in favour of new, more powerful, Collision Handler
component. Replace old Collider components with Collision Handler and add actions
corresponding to the desired behaviour e.g. Player -> Change Coins.
Upgrading to V4.5 & Below - See Release Notes.txt for details