Jump to content
  • 0
Sign in to follow this  
Triedge

Fail with custom Logs

Question

Working on a log damage, but a strange error when saving a data within the database.

void log_damage_skills(int char_id, const char *char_name, int class, int char_lvl,int batk,int watk, int mob_id, const char *mob_name, int mob_lvl, int skill_id, int skill_lv, struct Damage damagd, int porcentual) {

	ShowDebug("Iniciando logsamage \n");
	ShowDebug("(per	= '%d') \n", porcentual);

	int finalper = porcentual;
	char *Final = "finalmente";
	if (SQL_ERROR == SQL->Query(logs->mysql_handle, LOG_QUERY " INTO `control_skill_damage` ( `date`, `char_id`, `char_name`, `class`, `char_lvl`, `char_batk`, `char_watk`, `mob_id`, `mob_name`, `mob_lvl`, `skill_id`, `skill_lv`, `damage`, `porcentual`, `notas`) VALUES (NOW(), '%d', '%s', '%d', '%d', '%d', '%d', '%d', '%s', '%d', '%d', '%d', '%d', '%d', 'Finalmente')", char_id, char_name, class, char_lvl, batk, watk, mob_id, mob_name, mob_lvl, skill_id, skill_lv, damagd, porcentual)
		) {
		Sql_ShowDebug(logs->mysql_handle);
		return;
	}
}

The problem is the value "porcentual"

Always keep a value of 0.

post-3111-0-11570300-1463538007_thumb.png

 

 

Just I do not understand why always returning the value.
In fact, in the console it is that the value is 50, 400, etc ...

But when saving, always keeps 0.

Share this post


Link to post
Share on other sites

0 answers to this question

Recommended Posts

There have been no answers to this question yet

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.