Current events - Revision history

imported>Dinoguy1000 at 22:30, 21 October 2006

2006-10-21T22:30:56Z

← Older revision	Revision as of 22:30, 21 October 2006
(No difference)

imported>Dinoguy1000 at 22:30, 21 October 2006

2006-10-21T22:30:56Z

← Older revision		Revision as of 22:30, 21 October 2006
Line 1:		Line 1:
	~~= BMS Extension Tutorial posted =~~		#REDIRECT [[XentaxWiki:Village Pub]]

	~~http://wiki.xentax.com/index.php/BMS_to_Wiki~~

	;)

	~~--[[User:Mr.Mouse\|Mr.Mouse]] 17:16, 25 August 2006 (EDT)~~

	~~= BMS extension update =~~

	~~As you can see below, this extension works currently.~~
	However, all the code here is OBSOLETE, as during work on MexCom I realized I had done it all the wrong way. The WIKI focusses on archive extensions, and lists games that follow the same rule PER extension. So the archive file extension is pretty high up the ladder, if not on top as far as I'm concerned in the database programming. This I had not implemented at all. I figured people would write their script and then add it, single game, single script wise. I did check if a script wasn't used somewhere already, but in case of PAK files from Doom etc that would be a real pain in the ass to include in the database. We'd have to post every single script in there for each seperate game. In the new code, the games and platform values are linked. That means they both can be a list of values, that are indexed to eachother. So, we can have one PAK script and then add multiple games at once, via "games='Doom', 'Doom 2', 'Heretic', 'Hexen', platform='PC', 'PC', 'PC', 'PC'". That should improve everything a lot AND it is more compatible with the way this type of data is handled in MexCom, where the Archive Extension is at the top of the ladder as well. But.... after I realized I had done it all wrong, I could kill someone. Especially myself. I had to rewrite 90% of it all. And still it may present bugs. But I have to finish it at the end of august.

	~~--[[User:Mr.Mouse\|Mr.Mouse]] 18:23, 15 August 2006 (EDT)~~

	~~= Bad_Behavior hack =~~

	Today I have upgraded the Bad_Behavior hack I had previously installed to the latest version. The older version blocked also good people. I hope the new version won't. (And hope it is still good enough to block spammers).

	~~--[[User:Mr.Mouse\|Mr.Mouse]]~~

	~~Cool, cross our fingers and hope it works!~~

	~~[[User:Dinoguy1000\|Dinoguy1000]] 18:11, 13 August 2006 (EDT)~~

	~~= WIKI code upgrade! =~~

	~~Yep, I have upgraded the code to the latest version of the WIKI and as you can see, the BMS tag now is ready to be exploited. Thanks to our host for running a few scripts.~~

	~~--[[User:Mr.Mouse\|Mr.Mouse]]~~

	Okay, making progress on my local system. The BMS tag is now more or less done, and any additions will be stored in a MySQL database, pretty neat huh! Also, Captain and I are rather proud of "going official" with Xentax now being a foundation (non-profit organisation). :D

	~~--[[User:Mr.Mouse\|Mr.Mouse]] 17:45, 29 June 2006 (EDT)~~


	~~= Working on BMS hack =~~

	~~Just want to say you people are doing a great job at the WIKI. Some very cool ideas are currently being implemented.~~
	~~Next up for me will be a hack that 'll make it possible to tag BMS sections like this:~~

	~~<bms ext="grp" games="'Duke Nukem 3d', 'Shadow Warrior'" author="Mr.Mouse" platforms="'PC', 'PC'" version="1.0">~~
	~~ImpType SFileSize ;~~
	~~IDString 0 KenSilverman ;~~
	~~Get FC Long 0 ;~~
	~~Set MFC Long FC ;~~
	~~Math MFC *= 16 ;~~
	~~Math MFC += 16 ;~~
	~~SavePos FS 0 ;~~
	~~For TE = 1 To FC ;~~
	~~GoTo FS 0 ;~~
	~~GetDString FN 12 0 ;~~
	~~SavePos FSO 0 ;~~
	~~Get FSI Long 0 ;~~
	~~SavePos FS 0 ;~~
	~~Log FN MFC FSI 0 FSO ;~~
	~~Math MFC += FSI ;~~
	~~Next TE ;~~
	~~</bms>~~



	~~See what I mean? Then the WIKI parser should save this section in between in a separate base for future reference by other clients.~~

	~~--[[User:Mr.Mouse\|Mr.Mouse]]~~


	Thanks for the compliments! As to the tag, I'll have to experiment a bit to be sure, but the necessary attribute values could be included into the template the end-user works with. I'll probably wait till you implement the hack to try it, though...
	~~:[[User:Dinoguy1000\|Dinoguy1000]] 17:10, 25 Apr 2006 (EDT)~~

	~~= Countering Spam =~~

	~~We should start to protect pages or block anonymous users from being able to edit. Some of them are lowlife spammers that should be shot without trial~~
	~~--[[User:Mr.Mouse\|Mr.Mouse]]~~

	Actually, I've fixed it. Now, only logged in users can edit pages. Note, anonymous users, that this is not a way to discourage you to help out by forcing you to register, it's a way of preventing spammers or spambots to have free access. We hope you understand.
	~~--[[User:Mr.Mouse\|Mr.Mouse]]~~

	~~Thanks for disabling anonymous posting - that should hopefully make a difference. It got really annoying - I think I blocked about 25-30 people in 2 days! lets hope never again.~~

	~~[[User:WATTO\|WATTO]]~~

	~~Agreed. Too bad it got out of hand.~~
	~~[[User:Captain\|Captain]]~~

	~~Hmm... should we unprotect select pages, then?~~
	~~[[User:Dinoguy1000\|Dinoguy1000]]~~

	~~What pages specifically should you want unprotected?~~
	~~Well, we already have our first signed up l0ser spammer called "Bounty". I blocked him for life. 240000 hours should suffice.~~
	~~--[[User:Mr.Mouse\|Mr.Mouse]]~~

	~~Well, we blocked anonymous users, but now bots still log in and spam. The Age Of Empires 3 Talk page seems to be popular. --[[User:Mr.Mouse\|Mr.Mouse]]~~

	~~Yes, but it's a lot less frequent than it was.~~ [[~~User~~:~~Captain\|Captain~~]]

	~~---~~

imported>Mr.Mouse at 21:16, 25 August 2006

2006-08-25T21:16:12Z

← Older revision	Revision as of 21:16, 25 August 2006
(No difference)

imported>Mr.Mouse at 21:16, 25 August 2006

2006-08-25T21:16:12Z

← Older revision		Revision as of 21:16, 25 August 2006
Line 1:		Line 1:
			= BMS Extension Tutorial posted =

			http://wiki.xentax.com/index.php/BMS_to_Wiki

			;)

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

	= BMS extension update =		= BMS extension update =

imported>Mr.Mouse: /* Working on BMS hack */

2006-08-22T19:07:02Z

Working on BMS hack

← Older revision	Revision as of 19:07, 22 August 2006
(No difference)

imported>Mr.Mouse: /* Working on BMS hack */

2006-08-22T19:07:02Z

Working on BMS hack

← Older revision		Revision as of 19:07, 22 August 2006
Line 32:		Line 32:
	Next up for me will be a hack that 'll make it possible to tag BMS sections like this:		Next up for me will be a hack that 'll make it possible to tag BMS sections like this:

	<bms ~~GAME~~=~~Whole-Death AUTHOR~~=~~PXR EXT~~=~~PAK VERSION~~=1>		<bms ext="grp" games="'Duke Nukem 3d', 'Shadow Warrior'" author="Mr.Mouse" platforms="'PC', 'PC'" version="1.0">
			ImpType SFileSize ;
			IDString 0 KenSilverman ;
			Get FC Long 0 ;
			Set MFC Long FC ;
			Math MFC *= 16 ;
			Math MFC += 16 ;
			SavePos FS 0 ;
			For TE = 1 To FC ;
			GoTo FS 0 ;
			GetDString FN 12 0 ;
			SavePos FSO 0 ;
			Get FSI Long 0 ;
			SavePos FS 0 ;
			Log FN MFC FSI 0 FSO ;
			Math MFC += FSI ;
			Next TE ;
			</bms>

	~~IDString SCREW_YOU_HACKER~~

	~~Get FN Long 0~~

	~~For T = 1 To FN~~

	~~Get FO Long 0~~

	~~Get FS Long 0~~

	~~Log "" FO FS 0 0~~

	~~Next T~~

	~~</bms>~~

imported>Mr.Mouse: /* BMS extension update */

2006-08-15T22:23:33Z

BMS extension update

← Older revision	Revision as of 22:23, 15 August 2006
(No difference)

imported>Mr.Mouse: /* BMS extension update */

2006-08-15T22:23:33Z

BMS extension update

← Older revision		Revision as of 22:23, 15 August 2006
Line 2:		Line 2:

	As you can see below, this extension works currently.		As you can see below, this extension works currently.
	However, all the code here is OBSOLETE, as during work on MexCom I realized I had done it all the wrong way. The WIKI focusses on archive extensions, and lists games that follow the same rule PER extension. So the archive file extension is pretty high up the ladder, if not on top as far as I'm concerned in the database programming. This I had not implemented at all. I figured people would write their script and then add it, single game, single script wise. I did check if a script wasn't used somewhere already, but in case of PAK files from Doom etc that would be a real pain in the ass to include in the database. We'd have to post every single script in there for each seperate game. In the new code, the games and platform values are linked. That means they both can be a list of values, that are indexed to eachother. So, we can have one PAK script and then add multiple games at once, via "games='Doom', 'Doom 2', 'Heretic', 'Hexen', platform='PC', 'PC', 'PC', 'PC'". That should improve everything a lot AND it is more compatible with the way this type of data is handled in MexCom, where the Archive Extension is at the top of the ladder as well.		However, all the code here is OBSOLETE, as during work on MexCom I realized I had done it all the wrong way. The WIKI focusses on archive extensions, and lists games that follow the same rule PER extension. So the archive file extension is pretty high up the ladder, if not on top as far as I'm concerned in the database programming. This I had not implemented at all. I figured people would write their script and then add it, single game, single script wise. I did check if a script wasn't used somewhere already, but in case of PAK files from Doom etc that would be a real pain in the ass to include in the database. We'd have to post every single script in there for each seperate game. In the new code, the games and platform values are linked. That means they both can be a list of values, that are indexed to eachother. So, we can have one PAK script and then add multiple games at once, via "games='Doom', 'Doom 2', 'Heretic', 'Hexen', platform='PC', 'PC', 'PC', 'PC'". That should improve everything a lot AND it is more compatible with the way this type of data is handled in MexCom, where the Archive Extension is at the top of the ladder as well. But.... after I realized I had done it all wrong, I could kill someone. Especially myself. I had to rewrite 90% of it all. And still it may present bugs. But I have to finish it at the end of august.

			--[[User:Mr.Mouse\|Mr.Mouse]] 18:23, 15 August 2006 (EDT)

	= Bad_Behavior hack =		= Bad_Behavior hack =

imported>Mr.Mouse at 22:21, 15 August 2006

2006-08-15T22:21:49Z

← Older revision	Revision as of 22:21, 15 August 2006
(No difference)

imported>Mr.Mouse at 22:21, 15 August 2006

2006-08-15T22:21:49Z

← Older revision		Revision as of 22:21, 15 August 2006
Line 1:		Line 1:
			= BMS extension update =

			As you can see below, this extension works currently.
			However, all the code here is OBSOLETE, as during work on MexCom I realized I had done it all the wrong way. The WIKI focusses on archive extensions, and lists games that follow the same rule PER extension. So the archive file extension is pretty high up the ladder, if not on top as far as I'm concerned in the database programming. This I had not implemented at all. I figured people would write their script and then add it, single game, single script wise. I did check if a script wasn't used somewhere already, but in case of PAK files from Doom etc that would be a real pain in the ass to include in the database. We'd have to post every single script in there for each seperate game. In the new code, the games and platform values are linked. That means they both can be a list of values, that are indexed to eachother. So, we can have one PAK script and then add multiple games at once, via "games='Doom', 'Doom 2', 'Heretic', 'Hexen', platform='PC', 'PC', 'PC', 'PC'". That should improve everything a lot AND it is more compatible with the way this type of data is handled in MexCom, where the Archive Extension is at the top of the ladder as well.


	= Bad_Behavior hack =		= Bad_Behavior hack =