Rendril

Indeed AP is a very inflexible game mechanic for quest use. You also have to account for things like faster regen times or greater storage capacity. That is not to say AP could not be used, but it seems very limiting to both the quest maker and the player questing.

[b]int[/b] mds_location_visits(string $location) [b]Parameters[/b] $location can be 'current' or the coordinates of a location, for example '1_0x0_1'. [b]Returns[/b] Number of time player has been in the location. Will return null if the location does not exist. Example 1: [code] @vv = mds_location_visits('current'); echo "You have been here " .@vv ."times."; [/code] Example 2: [code] @vv = mds_location_visits('1_0x0_1'); echo "You have been to the Gazebo of Equilibrium " .@vv ."times."; [/code]

Lets say you want players to have... magic points. Minimum 0, maximum 50. Every hour they get 5 magic points and they use them one your clickables. Compare the current time to the last time they accessed some place, and adjust the points accordingly. For example, they opened the chest of bacon at 14:00, and had 30 magic points. Now it is 16:00, that means their magic points should increase by 10 and they are left with 40. They use 15 magic points to cook some bacon, now they have 25 magic points etc.

Were the other creatures not conflicting with the species limits?

That is up to Mur. I don't think a uv('ap') is necessary because it is very easy to simulate. Maybe later there will be functions to affect a player's AP, we shall see.

You are right AP is missing, I think it would be useful to have. As for the heat functions, I have added them to the MDS manual section.

[b]int[/b] mds_player_heat(); [b]Returns[/b] The player's active heat count. Example: [code] @va = mds_player_heat(); echo 'You currently have ' . @va ' active heat'; [/code]

[b]array[/b] mdsi_item_heat(); [b]Returns[/b] -Amount of heat that has been stored in the item. -Players that have had heat stored in the item -How much heat each player has stored The return array is in this form: array(2) { ["current"] => total heat ["players"]=> array( ["player name"]=> heat stored by player, ["player name2"]=> heat stored by player, ["player name3"]=> heat stored by player, etc ) } } All the heat that has ever been stored will be returned. Later on heat might gradually decrease over time or be able to get retrieved through other functions. Example 1: [code] @va = mdsi_item_heat(); echo 'The box has ' . @va['current'] . ' heat in it'; [/code] Shows how much heat is in the item. Example 2: [code] @vp = mdsi_item_heat(); foreach(@vp['players'] as @vk => @vh){ echo @vk . ' has stored ' . @vh . ' heat<br />'; } echo 'In total ' . count(@vp['players']) . ' have stored heat in talisman'; [/code] Makes a list of players that stored heat in the item and how much. [i]The function is intended for item use only (hence the mdsi) but can be used in any clickable at present.[/i]

[b]int[/b] mdsi_takeheat(int $heat); Takes heat from the player's active heat and stores it in the item. [b]Returns[/b] how much heat was taken. Amount to take must be positive. Can only take as much heat as what the player has, trying to take more will cause the player's heat to drop to 0 (currently) and will not store any in the item. Example: [code] @va = mdsi_takeheat(100); echo @va . ' heat was taken'; [/code] [i]The function is intended for item use only (hence the mdsi) but can be used in any clickable at present.[/i]

Good luck and come back soon.

Is this the only code that gives/reads the keys? I don't see any logic error in the code, are you sure that you are not reusing @vz elsewhere and thereby overriding your key prefix or that some other clickable doesn't accidentally give the wrong key?

I somehow doubt it, but do you have a comma in your prefix? Multiple keys are sent through as a comma seperated string not as individual variables.

As I recall, you cannot put variables in the locations definition.

Gaining items is the benefit (quite a big one actually, considering what they can cost) I think it is clear there was a misunderstanding on behalf of MRAlyon in his discussion with Udgard, but that doesn't make it an excuse to abuse alts.

What kind of information do you need to make the wallpaper? Colors, theme, images? On a side note, there [i]are[/i] [url="http://magicduel.com/index.php?pag=featureinfo"]official MD wallpapers[/url] (near the bottom of the page)

The problem is not that you gained wish points for your alts or that you had them create items. The abuse is because you then sent the items to your main account. Edit: Seems dst already said the same

Try clearing your cache and refreshing the page.

[quote name='Chewett' date='10 July 2010 - 11:17 AM' timestamp='1278753444' post='63728'] Your main isnt benefitting, But those people using the service are... [/quote] How is it different to anyone making a tokening service on their main? The tokens are to be bought legitimately with credits. As long as the trade profits are not sent off to the main, I don't see why this would be abuse.

You could also have got attacked in between that time with the battle being forgotten.

There should no longer be any #sl1m warnings being shown. @Grido: that's something else that might change yet. There should not be any issues with the NPC's, can anyone confirm that they cannot be fought?

Happy birthday

'Any' is not really a species, it just means you can have any number of them (for now). It will probably change later.

It is impossible for those two errors to appear together, please have him try again.

Random ritual fixed, see if anything else comes up.

@Kyphis: that was just a message because file was missing temporarily. If such an error does not repeat itself don't worry about it. As the announcements said combat might behave strangely, like with the random ritual creation. Random rituals should not obey the species limitations, please can someone confirm this. @Lifeline: if at least one of them can be put into a ritual then all of them should be useable.