- - I
- II -
Abstract Except for few intellect games such as chess, mahjong, and poker games, role-play games in on-line games are the mainstream. As for the so-called RPG, briefly speaking, it is the game type that players play the role of one or more characters exploring, fighting, interacting or growing in the virtual world( no matter on-line games or single-machine games). In the present role-play games, the map which players use in the game is usually edited by the map editor which designed by programmers according to the game plan and stored in the computer in text format. Then, it is called to interpret by program when needed. We will meet four problems in the following when we handle it by such way: 1.The content of the game map file may be understood by the programmer who designs the map editor only. But if the complexity of maps increases or the time for finishing it is too long, the kind of content which the original programmer is not easy to understand will appear. 2.If the original producer may not interpret the content of the game map file easily, then other programmers will not be able to understand or even handle it. 3.We need to modify the program to add the new function when we add the new definition to the map file in on-line games. It will terminate the connection from all users or cause program errors because of ripple effect when the new program is on-line. 4.It is necessary to re-write or modify a brand-new map and map editors in the future for different products. All these various problems come into being due to the reason that the game map file doesn t separate completely and interpret enough. XML can resolve all these problems. Keyword: XML, RPG( Role Playing Game), Map - III -
...I...III...IV...VI...VII...1 1.1...1 1.2...1 1.3...2 1.4...3...5 2.1 UML...5 2.2 XML...7 2.3 XML Schema...9 2.4...10...14 3.1...14 3.1.1...16 3.2...18 3.3...19...23 4.1...23 4.2...27 4.3...28 - IV -
4.4...32...33...36...38...43...45 - V -
...16...18...20...20...24...26...27...28...28...29...30 - VI -
...6...21...21...21 - VII -
- - 1 1.1 1.2
- - 2
- - 3 1.3 1.4
- 4 -
2.1 UML(Unified Modeling Language) 1997 Booch, Rambaugh Jacobson UML OMT, OOSE Booch 4 5 1997 OMG/ISO - 5 -
6 Use Case 7 Class Diagram Activity Diagram 8 (Interaction Diagram) (Sequence Diagram) (Collaboration Diagram) 910 11-6 -
(Package Diagram) 12 <?xml version= 1.0 encoding= big5?> < > < > </ > < >04-22929405</ > < > 2 168 </ > </ > - 7 -
- - 8
- - 9
- - 10
- 11 -
- 12 -
- 13 -
- - 14
- 15 -
- 16 -
- - 17
- - 18
- 19 -
- 20 -
- 21 -
- 22 -
- - 23
- - 24
- - 25
- 26 -
- 27 -
<?xml version="1.0" encoding="big5"?> <RPGMap xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" xsi:nonamespaceschemalocation="d:\my Docs\report3\RPGMAP.xsd"> <MapData> <RPGMapID>1</RPGMapID> <PictureSource>images/map1.gif</PictureSource> <MapWidth>160</MapWidth> <MapHeight>96</MapHeight> <CellWidth>32</CellWidth> <CellHeight>32</CellHeight> </MapData> <CellData> <PictureID>2</PictureID> <MoveLevel>0</MoveLevel> <CellSequence>1</CellSequence> </CellData> <CellData> <PictureID>2</PictureID> <MoveLevel>0</MoveLevel> <CellSequence>2</CellSequence> </CellData>...( ) <CellData> <PictureID>1</PictureID> <MoveLevel>50</MoveLevel> <CellSequence>16</CellSequence> </CellData> </RPGMap> - 28 -
- - 29 [MAP] MapPics=13 anis=0 lay0os=4 lay0as=0 lay1os=18 lay1as=0 lay2os=0 lay2as=0 lay3os=0 lay3as=0 width=40 height=30 cps=0 tps=0 [MAPPIC000] path=05\ I º22.bmp type=0 dotx=0 doty=0 [MAPPIC001] path=05\rocks14.bmp type=0 dotx=0 doty=0.( ) [LAY0O000] obj=0 x=0 y=0 z=1 type=0 dx=0. Dy=0. Screen=0 FX=0 [LAY0O001] obj=5 x=-38 y=-10 z=21 type=0 dx=0. Dy=0. Screen=0 FX=0 ( ) [MAPATTRIB] file=attrib\map004_000.bmp
- - 30
- - 31
- 32 -
- 33 -
- - 34
- - 35
- - 36
- 37 -
- 38 -
- 39 -
- 40 -
- 41 -
- 42 -
- 43 -
- 44 -
- - 45
- - 46
- 47 -
- 48 -