I used CoC text game for alot of years, and always wished to help with some feats of the game. Hi all and nice to be part of this forum. I think i registered in the forum alot of time ago but i forgot it all, so i registered again. This still doesn't help you with missing properties though.Ĭonsider some naive structure like (which is almost exactly what the character viewer was doing in parts): **** Unless you add classpath overrides to tell the AMF system to use a different class in place of another. *** If you don't either a) explicitly "clone" (read: create a deep copy) the data segment, or (I think) b) reference the data segment elsewhere and then explicitly close the shared object, then you're effectively working directly on the object that will be saved again as soon as the swf closes. ** Which is easy to do, because AMF makes it *feel* like the purposeful structure you've created with your custom classes is right there, and it's all nicely typed and has properties etc etc. Everything is converted into a dynamic object with only basic data types (int, number, string, array, object), and the shared object is only open long enough to immediately clone its data contents into another structure to avoid potential fuckery. If that class has gone missing****, or no longer has properties that are in the serialized object, the whole thing breaks.Īnd now you know why TiTS saves things in the way it does. When you then load the object, Flash looks for that class to create an instance of it. If you have a custom class and serialize it, the *class path* itself gets serialized into the object. * This is done using structural encoding called AMF.
If you modify the data in the referenced object, you're also modifying data inside the shared object**.Ĭertain things (including closing the swf/tab/etc) will flush the current state of the shared object to disk***. If you just grab the data segment after loading the shared object, you're referencing the object structure directly. It's how shared objects work, for "ease of use".Ī shared object is a container that has a *data segment that gets written to disk.
0 kommentar(er)
