Talk:MexScript to Wiki - Revision history

imported>Dinoguy1000: moved Talk:BMS to Wiki to Talk:MexScript to Wiki: BMS refers to the binary (compiled) form of MexScript

2011-10-22T03:55:16Z

moved Talk:BMS to Wiki to Talk:MexScript to Wiki: BMS refers to the binary (compiled) form of MexScript

← Older revision	Revision as of 03:55, 22 October 2011
(No difference)

imported>Dinoguy1000: moved Talk:BMS to Wiki to Talk:MexScript to Wiki: BMS refers to the binary (compiled) form of MexScript

2011-10-22T03:55:16Z

moved Talk:BMS to Wiki to Talk:MexScript to Wiki: BMS refers to the binary (compiled) form of MexScript

← Older revision	Revision as of 03:55, 22 October 2011
(No difference)

imported>Dinoguy1000: A suggestion

2006-10-02T04:54:52Z

A suggestion

← Older revision	Revision as of 04:54, 2 October 2006
(No difference)

imported>Dinoguy1000: A suggestion

2006-10-02T04:54:52Z

A suggestion

← Older revision		Revision as of 04:54, 2 October 2006
Line 23:		Line 23:

	--[[User:Dinoguy1000\|Dinoguy1000]] 18:44, 27 August 2006 (EDT)		--[[User:Dinoguy1000\|Dinoguy1000]] 18:44, 27 August 2006 (EDT)

			== A suggestion ==

			(I also posted this as a comment to the announcement on the front page) I was thinking, perhaps you should create a new tag for the WIlKIBMS feature that lets the author specify the version of MexScript used for the script. This would allow for errorchecking in future WIKI-based versions of MexCom, preventing them from trying to use an otherwise incompatible script that woulld otherwise result in errors. Any thoughts?

			--[[User:Dinoguy1000\|Dinoguy1000]] <sup>[[User Talk:Dinoguy1000\|Talk]]</sup> 00:54, 2 October 2006 (EDT)

imported>Dinoguy1000 at 22:44, 27 August 2006

2006-08-27T22:44:05Z

← Older revision	Revision as of 22:44, 27 August 2006
(No difference)

imported>Dinoguy1000 at 22:44, 27 August 2006

2006-08-27T22:44:05Z

← Older revision		Revision as of 22:44, 27 August 2006
Line 19:		Line 19:

	--[[User:Mr.Mouse\|Mr.Mouse]] 17:52, 27 August 2006 (EDT)		--[[User:Mr.Mouse\|Mr.Mouse]] 17:52, 27 August 2006 (EDT)

			Thanks for the answers! As to the voting system, I should have been more specific... I meant to ask, how is it marked on the WIKI? And will it use categories, as I suggested on the forum? Sorry for all the questions! =P

			--[[User:Dinoguy1000\|Dinoguy1000]] 18:44, 27 August 2006 (EDT)

imported>Mr.Mouse: /* A few answers */

2006-08-27T21:52:34Z

A few answers

← Older revision	Revision as of 21:52, 27 August 2006
(No difference)

imported>Mr.Mouse: /* A few answers */

2006-08-27T21:52:34Z

A few answers

← Older revision		Revision as of 21:52, 27 August 2006
Line 17:		Line 17:
	You would get "'Baldur's Gate'" as a value for the games attribute. That's three single-quotes there. The parser would read only Baldur. So, at the moment, you can't use single-quotes in the name of the game. <br>		You would get "'Baldur's Gate'" as a value for the games attribute. That's three single-quotes there. The parser would read only Baldur. So, at the moment, you can't use single-quotes in the name of the game. <br>
	One final note: suppose we have a PAK extension in the database. Suppose the games are Quake 1, Quake 2, Quake 3, Quake 4, Quake 5, Quake 6. Each of these games can have a different script processing their PAK archives. They can all have the same script processing their PAK archives. Now, what happens if you notice that Quake 1 has another TYPE of PAK file? So, we have two PAK file-formats for Quake 1. We need to start a new page, and a new entry. If I'm correct, then my code wil check if the scripts are alike, if not, add it to the list of games for the PAK extension. <br>		One final note: suppose we have a PAK extension in the database. Suppose the games are Quake 1, Quake 2, Quake 3, Quake 4, Quake 5, Quake 6. Each of these games can have a different script processing their PAK archives. They can all have the same script processing their PAK archives. Now, what happens if you notice that Quake 1 has another TYPE of PAK file? So, we have two PAK file-formats for Quake 1. We need to start a new page, and a new entry. If I'm correct, then my code wil check if the scripts are alike, if not, add it to the list of games for the PAK extension. <br>

			--[[User:Mr.Mouse\|Mr.Mouse]] 17:52, 27 August 2006 (EDT)

imported>Mr.Mouse at 21:52, 27 August 2006

2006-08-27T21:52:19Z

← Older revision	Revision as of 21:52, 27 August 2006
(No difference)

imported>Mr.Mouse at 21:52, 27 August 2006

2006-08-27T21:52:19Z

← Older revision		Revision as of 21:52, 27 August 2006
Line 7:		Line 7:

	--[[User:Dinoguy1000\|Dinoguy1000]] 16:35, 27 August 2006 (EDT)		--[[User:Dinoguy1000\|Dinoguy1000]] 16:35, 27 August 2006 (EDT)

			== A few answers ==

			Firstly, you can only vote once per game/ext combination. Either a yes, or a no. <br>
			Secondly, the voting IS behind the MexCom key, only Friends of MultiEx can vote, more importantly: only Friends of MultiEx can use the WIKI options in MexCom. <br>
			Next: the head honcho is the extension of the archive. Entries are saved according to Extension --> games. If a format is used by different games, you can list those that use the same extension in one go. The one with the other extension will need a new entry. Note that this WIKI is listing according to Extension. You can select the extension and then see a list of games. <br>In the BMS database, any new game that is added to an Extension can have it\s own script OR reference an already existing script. It doesn't matter. If a script already exists, that one will be refered to.<br> So , the hierarchy is clear : Extension-->Games(with platforms)-->scripts<br>.
			Third, that would all be great, but failed to have priority as I needed to have a working version of MexCom 4.3 finished by the end of august. <br>
			Lastly, take for example Baldur's Gate. Notice the single-quote there in the name?
			You would get "'Baldur's Gate'" as a value for the games attribute. That's three single-quotes there. The parser would read only Baldur. So, at the moment, you can't use single-quotes in the name of the game. <br>
			One final note: suppose we have a PAK extension in the database. Suppose the games are Quake 1, Quake 2, Quake 3, Quake 4, Quake 5, Quake 6. Each of these games can have a different script processing their PAK archives. They can all have the same script processing their PAK archives. Now, what happens if you notice that Quake 1 has another TYPE of PAK file? So, we have two PAK file-formats for Quake 1. We need to start a new page, and a new entry. If I'm correct, then my code wil check if the scripts are alike, if not, add it to the list of games for the PAK extension. <br>