¡Vota por nosotros!

Vota diariamente por XatiyaRO para mejorar nuestra reputación y ayudarnos a crecer.

RagnaTOP - Top Ragnarok Online en Español Ragnarok private server
private server TOP RO Hispano

Autor Tema: Guía Creación de cliente funcional.  (Leído 282453 veces)

0 Usuarios y 1 Visitante están viendo este tema.

Desconectado Alepcis

  • First Job
  • *
  • Mensajes: 307
  • Todo es un sueño, una falsa realidad.
  • Guild: Agua&Jabón[GL]
  • Pj Principal: Alepcis
Re:Guía Creación de cliente funcional.
« Respuesta #15 en: 05 de Noviembre de 2013, 18:55:23 pm »
Tendrás que crear una cuenta nueva.
Un ejemplo:
ID: Alepcis_M
Pass: programacion

Será una cuenta de personajes hombres, después para volver a usarla sólo quitas el _M y usas la ID sola y con la pass correspondiente.

ID: Alepcis
Pass: programación.

Cuando intentes loguear revisa tus 3 ventanas del emulador y verifica que no te muestre algún error con los puertos.




Desconectado Xeron

  • Novice
  • *
  • Mensajes: 14
Re:Guía Creación de cliente funcional.
« Respuesta #16 en: 05 de Noviembre de 2013, 19:26:30 pm »
escribo Xeron_M y la contraseña que tengo en el emulador, la del Hsql, la del Diff, "p1" y me sale el mismo error , reject to server, o failed to authenticate.

me he fijado en las 3 ventanas del emulador y

en una de las ventanas me sale éste error..

http://www.subirimagenes.net/i/131105073047720429.jpg

DB-ERROR table "mi-server.login.log" doesn't exist....
« Última modificación: 05 de Noviembre de 2013, 19:30:57 pm por Xeron »

Desconectado Alepcis

  • First Job
  • *
  • Mensajes: 307
  • Todo es un sueño, una falsa realidad.
  • Guild: Agua&Jabón[GL]
  • Pj Principal: Alepcis
Re:Guía Creación de cliente funcional.
« Respuesta #17 en: 05 de Noviembre de 2013, 20:36:24 pm »
Podrías subir tu char_athena.conf,login_athena y map_athena en alguno debe estar en error. También verifica que estés usando correctamente las tablas de SQL.




Desconectado Xeron

  • Novice
  • *
  • Mensajes: 14
Re:Guía Creación de cliente funcional.
« Respuesta #18 en: 06 de Noviembre de 2013, 18:42:01 pm »
login_athena (yo creo que esta aquí el fallo, porque no recuerdo haber modificado nada de aquí)

Spoiler for Hidden:
// Athena Login Server configuration file.
// Translated by Peter Kieser <pfak@telus.net>

// Note: "Comments" are all text on the right side of a double slash "//"
// Whatever text is commented will not be parsed by the servers, and serves
// only as information/reference.

// The login server listens on the interface with this IP address.
// NOTE: This allows you to run multiple servers on multiple interfaces
// while using the same ports for each server.
//bind_ip: 127.0.0.1
 
// Login Server Port
login_port: 6900

//Time-stamp format which will be printed before all messages.
//Can at most be 20 characters long.
//Common formats:
// %I:%M:%S %p (hour:minute:second 12 hour, AM/PM format)
// %H:%M:%S (hour:minute:second, 24 hour format)
// %d/%b/%Y (day/Month/year)
//For full format information, consult the strftime() manual.
//timestamp_format: [%d/%b %H:%M]

//If redirected output contains escape sequences (color codes)
stdout_with_ansisequence: no

//Makes server output more silent by omitting certain types of messages:
//1: Hide Information messages
//2: Hide Status messages
//4: Hide Notice Messages
//8: Hide Warning Messages
//16: Hide Error and SQL Error messages.
//32: Hide Debug Messages
//Example: "console_silent: 7" Hides information, status and notice messages (1+2+4)
console_silent: 0

// Console Commands
// Allow for console commands to be used on/off
// This prevents usage of >& log.file
console: off

// Can you use _M/_F to make new accounts on the server?
new_account: yes

//If new_account is enabled, minimum length to userid and passwords should be 4?
//Must be 'Yes' unless your client uses both 'Disable 4 LetterUserID/Password' Diffs
new_acc_length_limit: yes

// Account registration flood protection system
// allowed_regs is the number of registrations allowed in time_allowed (in seconds)
allowed_regs: 1
time_allowed: 10

// Log Filename. All operations received by the server are logged in this file.
login_log_filename: log/login.log

// To log the login server?
// NOTE: The login-sql server needs the login logs to enable dynamic pass failure bans.
log_login: yes

// Indicate how to display date in logs, to players, etc.
date_format: %Y-%m-%d %H:%M:%S

// Required account group id to connect to server.
// -1: disabled
// 0 or more: group id
group_id_to_connect: -1

// Minimum account group id required to connect to server.
// Will not function if group_id_to_connect config is enabled.
// -1: disabled
// 0 or more: group id
min_group_id_to_connect: -1

// Starting additional sec from now for the limited time at creation of account
// -1: new account are created with UNlimited time (default value)
// 0 or more: new accounts was created by addition of the value (in sec) to the actual time (to set first limited time)
start_limited_time: -1

// Check The clientversion set in the clientinfo ?
check_client_version: no

// What version we would allow to connect? (if the options above is enabled..)
client_version_to_connect: 20

// Store passwords as MD5 hashes instead of plaintext ?
// NOTE: Will not work with clients that use <passwordencrypt>
use_MD5_passwords: no

// Ipban features (SQL only)
ipban.enable: yes
//ipban.sql.db_hostname: 127.0.0.1
//ipban.sql.db_port: 3306
//ipban.sql.db_username: ragnarok
//ipban.sql.db_password: ragnarok
//ipban.sql.db_database: ragnarok
//ipban.sql.codepage:
//ipban.sql.ipban_table: ipbanlist
// Dynamic password failure ipban system
ipban.dynamic_pass_failure_ban: yes
ipban.dynamic_pass_failure_ban_interval: 5
ipban.dynamic_pass_failure_ban_limit: 7
ipban.dynamic_pass_failure_ban_duration: 5

// Interval (in seconds) to clean up expired IP bans. 0 = disabled. default = 60.
// NOTE: Even if this is disabled, expired IP bans will be cleaned up on login server start/stop.
// Players will still be able to login if an ipban entry exists but the expiration time has already passed.
ipban_cleanup_interval: 60

// Interval (in minutes) to execute a DNS/IP update. Disabled by default.
// Enable it if your server uses a dynamic IP which changes with time.
//ip_sync_interval: 10

// DNS Blacklist Blocking
// If enabled, each incoming connection will be tested against the blacklists
// on the specified dnsbl_servers (comma-separated list)
use_dnsbl: no
dnsbl_servers: bl.blocklist.de, socks.dnsbl.sorbs.net
// Here are some free DNS Blacklist Services: http://en.wikipedia.org/wiki/Comparison_of_DNS_blacklists
//==============================================================================
//   dnsbl_servers                 Description
// - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
// bl.blocklist.de                 IP-Addresses who attack other servers/honeypots over SSH, FTP, IMAP, etc.
// ircbl.ahbl.org                  AHBL (open proxies, compromised machines, comment spammers)
// safe.dnsbl.sorbs.net            All zones in dnsbl.sorbs.net except "recent" and "escalations"
// sbl-xbl.spamhaus.org            Spamhaus blacklist (spammers, open proxies)
// socks.dnsbl.sorbs.net           Open SOCKS proxy servers
// tor.ahbl.org                    Current tor relay and exit nodes

// Which account engine to use.
// 'auto' selects the first engine available (txt, sql, then others)
// (defaults to auto)
account.engine: auto

// Account data storage configuration
// SQL
//account.sql.db_hostname: 127.0.0.1
//account.sql.db_port: 3306
//account.sql.db_username: ragnarok
//account.sql.db_password: ragnarok
//account.sql.db_database: ragnarok
//account.sql.codepage:
//account.sql.case_sensitive: no
//account.sql.account_db: login
//account.sql.accreg_db: global_reg_value

// Client MD5 hash check
// If turned on, the login server will check if the client's hash matches
// the value below, and will not connect tampered clients.
// Note: see doc\md5_hashcheck.txt for more details.
client_hash_check: off

// Client MD5 hashes
// A player can login with a client hash at or below the account group_id.
// Format: group_id, hash
client_hash: 0, 113e195e6c051bb1cfb12a644bb084c5
client_hash: 99, cb1ea78023d337c38e8ba5124e2338ae

import: conf/inter_athena.conf
import: conf/import/login_conf.txt

inter_athena:

Spoiler for Hidden:
// Athena InterServer configuration.
// Contains settings shared/used by more than 1 server.

// Options for both versions

// Log Inter Connections, etc.?
log_inter: 1

// Inter Log Filename
inter_log_filename: log/inter.log

// Level range for sharing within a party
party_share_level: 15

// SQL version options only

// You can specify the codepage to use in your mySQL tables here.
// (Note that this feature requires MySQL 4.1+)
//default_codepage:


// For IPs, ideally under linux, you want to use localhost instead of 127.0.0.1
// Under windows, you want to use 127.0.0.1.  If you see a message like
// "Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)"
// and you have localhost, switch it to 127.0.0.1

// Global SQL settings
// overridden by local settings when the hostname is defined there
// (currently only the login-server reads/obeys these settings)
sql.db_hostname: 127.0.0.1
sql.db_port: 3306
sql.db_username: root
sql.db_password: q2e8endat0
sql.db_database: miserver
sql.codepage:

// MySQL Character SQL server
char_server_ip: 127.0.0.1
char_server_port: 3306
char_server_id: root
char_server_pw: q2e8endat0
char_server_db: miserver

// MySQL Map SQL Server
map_server_ip: 127.0.0.1
map_server_port: 3306
map_server_id: root
map_server_pw: q2e8endat0
map_server_db: miserver

// MySQL Log SQL Database
log_db_ip: 127.0.0.1
log_db_port: 3306
log_db_id: root
log_db_pw: q2e8endat0
log_db_db: miserver
log_codepage:
log_login_db: loginlog

// MySQL Reconnect Settings
// - mysql_reconnect_type:
//   1: When MySQL disconnects during runtime, the server tries to reconnect
//      mysql_reconnect_count times and shuts down if unsuccessful.
//   2: When mysql disconnects during runtime, it tries to reconnect indefinitely.
mysql_reconnect_type: 2
mysql_reconnect_count: 1

// DO NOT CHANGE ANYTHING BEYOND THIS LINE UNLESS YOU KNOW YOUR DATABASE DAMN WELL
// this is meant for people who KNOW their stuff, and for some reason want to change their
// database layout. [CLOWNISIUS]

// ALL MySQL Database Table names

// Char Database Tables
char_db: char
hotkey_db: hotkey
scdata_db: sc_data
cart_db: cart_inventory
inventory_db: inventory
charlog_db: charlog
storage_db: storage
reg_db: global_reg_value
skill_db: skill
interlog_db: interlog
memo_db: memo
guild_db: guild
guild_alliance_db: guild_alliance
guild_castle_db: guild_castle
guild_expulsion_db: guild_expulsion
guild_member_db: guild_member
guild_skill_db: guild_skill
guild_position_db: guild_position
guild_storage_db: guild_storage
party_db: party
pet_db: pet
friend_db: friends
mail_db: mail
auction_db: auction
quest_db: quest
homunculus_db: homunculus
skill_homunculus_db: skill_homunculus
mercenary_db: mercenary
mercenary_owner_db: mercenary_owner
elemental_db: elemental
ragsrvinfo_db: ragsrvinfo

// Map Database Tables
item_db_db: item_db
item_db_re_db: item_db_re
item_db2_db: item_db2
item_cash_db_db: item_cash_db
item_cash_db2_db: item_cash_db2
mob_db_db: mob_db
mob_db2_db: mob_db2
mob_skill_db_db: mob_skill_db
mob_skill_db2_db: mob_skill_db2
mapreg_db: mapreg

// Use SQL item_db, mob_db and mob_skill_db for the map server? (yes/no)
use_sql_db: no

import: conf/import/inter_conf.txt

char_athena

Spoiler for Hidden:
// Athena Character configuration file.

// Note: "Comments" are all text on the right side of a double slash "//"
// Whatever text is commented will not be parsed by the servers, and serves
// only as information/reference.

// Server Communication username and password.
userid: s1
passwd: p1

// Server name, use alternative character such as ASCII 160 for spaces.
// NOTE: Do not use spaces or any of these characters which are not allowed in
//       Windows filenames \/:*?"<>|
//       ... or else guild emblems won't work client-side!
server_name: rAthena

// Wisp name for server: used to send wisp from server to players (between 4 to 23 characters)
wisp_server_name: Server

// Login Server IP
 The character server connects to the login server using this IP address.
// NOTE: This is useful when you are running behind a firewall or are on
// a machine with multiple interfaces.
 login_ip: 127.0.0.1

// The character server listens on the interface with this IP address.
// NOTE: This allows you to run multiple servers on multiple interfaces
// while using the same ports for each server.
//bind_ip: 127.0.0.1

// Login Server Port
login_port: 6900

// Character Server IP
// The IP address which clients will use to connect.
// Set this to what your server's public IP address is.
 char_ip: 127.0.0.1

// Character Server Port
char_port: 6121

//Time-stamp format which will be printed before all messages.
//Can at most be 20 characters long.
//Common formats:
// %I:%M:%S %p (hour:minute:second 12 hour, AM/PM format)
// %H:%M:%S (hour:minute:second, 24 hour format)
// %d/%b/%Y (day/Month/year)
//For full format information, consult the strftime() manual.
//timestamp_format: [%d/%b %H:%M]

//If redirected output contains escape sequences (color codes)
stdout_with_ansisequence: no

//Makes server output more silent by ommitting certain types of messages:
//1: Hide Information messages
//2: Hide Status messages
//4: Hide Notice Messages
//8: Hide Warning Messages
//16: Hide Error and SQL Error messages.
//32: Hide Debug Messages
//Example: "console_silent: 7" Hides information, status and notice messages (1+2+4)
console_silent: 0

// Console Commands
// Allow for console commands to be used on/off
// This prevents usage of >& log.file
console: off

// Type of server.
// No functional side effects at the moment.
// Displayed next to the server name in the client.
// 0=normal, 1=maintenance, 2=over 18, 3=paying, 4=P2P
char_maintenance: 0

// Enable or disable creation of new characters.
// Now it is actually supported [Kevin]
char_new: 1

// Display (New) in the server list.
char_new_display: 0

// Maximum users able to connect to the server.
// Set to 0 to disable users to log-in. (-1 means unlimited)
max_connect_user: -1

// Group ID that is allowed to bypass the server limit of users.
// Default: -1 = nobody (there are no groups with ID < 0)
// See: conf/groups.conf
gm_allow_group: 99

// How often should the server save all files? (In seconds)
// Note: Applies to all data files on TXT servers.
// On SQL servers, it applies to guilds (character save interval is defined on the map config)
autosave_time: 60

// Display information on the console whenever characters/guilds/parties/pets are loaded/saved?
save_log: yes

// Starting point for new characters
// Format: <map_name>,<x>,<y>
start_point: new_1-1,53,111

// Starting items for new characters
// Max number of items is MAX_STARTITEM in char.c (default 32)
// Format: <id>,<amount>,<position>:<id>,<amount>,<position>:...
// To auto-equip an item, include the position where it will be equipped; otherwise, use zero.
start_items: 1201,1,2:2301,1,16

// Starting zeny for new characters
start_zeny: 0

// Size for the fame-lists
fame_list_alchemist: 10
fame_list_blacksmith: 10
fame_list_taekwon: 10

// Guild earned exp modifier.
// Adjusts taxed exp before adding it to the guild's exp. For example, if set
// to 200, the guild receives double the player's taxed exp.
guild_exp_rate: 100

// Name used for unknown characters
unknown_char_name: Unknown

// To log the character server?
log_char: 1

// Allow or not identical name for characters but with a different case (upper/lower):
// example: Test-test-TEST-TesT; Value: 0 not allowed (default), 1 allowed
name_ignoring_case: no

// Manage possible letters/symbol in the name of charater. Control character (0x00-0x1f) are never accepted. Possible values are:
// NOTE: Applies to character, party and guild names.
// 0: no restriction (default)
// 1: only letters/symbols in 'char_name_letters' option.
// 2: Letters/symbols in 'char_name_letters' option are forbidden. All others are possibles.
char_name_option: 1

// Set the letters/symbols that you want use with the 'char_name_option' option.
// Note: Don't add spaces unless you mean to add 'space' to the list.
char_name_letters: abcdefghijklmnopqrstuvwxyz ABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890

// How many Characters are allowed per Account ? (0 = disabled)
// You can not exceed the limit of MAX_CHARS slots, defined in mmo.h
// Doing that, chars_per_account will be default to MAX_CHARS.
chars_per_account: 0

// Restrict character deletion by BaseLevel
// 0: no restriction (players can delete characters of any level)
// -X: you can't delete chars with BaseLevel <= X
// Y: you can't delete chars with BaseLevel >= Y
// e.g. char_del_level: 80 (players can't delete characters with 80+ BaseLevel)
char_del_level: 0

// Amount of time in seconds by which the character deletion is delayed.
// Default: 86400 (24 hours)
// NOTE: Requires client 2010-08-03aragexeRE or newer.
char_del_delay: 86400

// What folder the DB files are in (item_db.txt, etc.)
db_path: db

//===================================
// Pincode system
//===================================
// NOTE: Requires client 2011-03-09aragexeRE or newer.
// A window is opened before you can select your character and you will have to enter a pincode by using only your mouse.
// Default: yes
pincode_enabled: yes

// How often does a user have to change his pincode?
// 0: never (default)
// X: every X days
pincode_changetime: 0

// How often can a user enter the wrong pincode?
// Default: 3 (client maximum)
pincode_maxtry: 3

// Are users forced to use a pincode when the system is enabled?
// Default: yes
pincode_force: yes

//===================================
// Addon system
//===================================
// Character moving
// NOTE: Requires client 2011-09-28aragexeRE or newer.
// Allows users to move their characters between slots.
// Default: yes
char_move_enabled: yes

// Allow users to move a character to a used slot?
// If enabled the characters are exchanged.
// Default: yes
char_movetoused: yes

// Allow users to move characters as often as they like?
char_moves_unlimited: no

import: conf/import/char_conf.txt

map_athena
Spoiler for Hidden:
//--------------------------------------------------------------
//rAthena Map-Server Configuration File
//--------------------------------------------------------------

// Note: "Comments" are all text on the right side of a double slash "//"
// Whatever text is commented will not be parsed by the servers, and serves
// only as information/reference.

//--------------------------------------------------------------
//                     Configuration Info
//--------------------------------------------------------------
// Interserver communication passwords, set in account.txt (or equiv.)
userid: s1
passwd: p1

// Character Server IP
// The map server connects to the character server using this IP address.
// NOTE: This is useful when you are running behind a firewall or are on
// a machine with multiple interfaces.
 char_ip: 127.0.0.1

// The map server listens on the interface with this IP address.
// NOTE: This allows you to run multiple servers on multiple interfaces
// while using the same ports for each server.
//bind_ip: 127.0.0.1

// Character Server Port
char_port: 6121

// Map Server IP
// The IP address which clients will use to connect.
// Set this to what your server's public IP address is.
 map_ip: 127.0.0.1

// Map Server Port
map_port: 5121

//Time-stamp format which will be printed before all messages.
//Can at most be 20 characters long.
//Common formats:
// %I:%M:%S %p (hour:minute:second 12 hour, AM/PM format)
// %H:%M:%S (hour:minute:second, 24 hour format)
// %d/%b/%Y (day/Month/year)
//For full format information, consult the strftime() manual.
//timestamp_format: [%d/%b %H:%M]

//If redirected output contains escape sequences (color codes)
stdout_with_ansisequence: no

//Makes server log selected message types to a file in the /log/ folder
//1: Log Warning Messages
//2: Log Error and SQL Error messages.
//4: Log Debug Messages
//Example: "console_msg_log: 7" logs all 3 kinds
//Messages logged by this overrides console_silent setting
console_msg_log: 0

//Makes server output more silent by omitting certain types of messages:
//1: Hide Information messages
//2: Hide Status messages
//4: Hide Notice Messages
//8: Hide Warning Messages
//16: Hide Error and SQL Error messages.
//32: Hide Debug Messages
//Example: "console_silent: 7" Hides information, status and notice messages (1+2+4)
console_silent: 0

//Where should all database data be read from?
db_path: db

// Enable the @guildspy and @partyspy at commands?
// Note that enabling them decreases packet sending performance.
enable_spy: no

// Read map data from GATs and RSWs in GRF files or a data directory
// as referenced by grf-files.txt rather than from the mapcache?
use_grf: no

// Console Commands
// Allow for console commands to be used on/off
// This prevents usage of >& log.file
console: off

// Database autosave time
// All characters are saved on this time in seconds (example:
// autosave of 60 secs with 60 characters online -> one char is saved every
// second)
autosave_time: 300

// Min database save intervals (in ms)
// Prevent saving characters faster than at this rate (prevents char-server
// save-load getting too high as character-count increases)
minsave_time: 100

// Apart from the autosave_time, players will also get saved when involved
// in the following (add as needed):
// 1: after every successful trade
// 2: after every vending transaction
// 4: after closing storage/guild storage.
// 8: After hatching/returning to egg a pet.
// 16: After successfully sending a mail with attachment
// 32: After successfully submitting an item for auction
// 64: After successfully get/delete/complete a quest
// NOTE: These settings decrease the chance of dupes/lost items when there's a
// server crash at the expense of increasing the map/char server lag. If your
// server rarely crashes, but experiences interserver lag, you may want to set
// these off.
save_settings: 127

// Message of the day file, when a character logs on, this message is displayed.
motd_txt: conf/motd.txt

// When @help or @h is typed when you are a gm, this is displayed for helping new gms understand gm commands.
help_txt: conf/help.txt
help2_txt: conf/help2.txt
charhelp_txt: conf/charhelp.txt

// Maps:
import: conf/maps_athena.conf

import: conf/import/map_conf.txt

aquí las tablas con HeidiSQL:



Me aparece Login, pero no loginlog

« Última modificación: 06 de Noviembre de 2013, 19:07:43 pm por Xeron »

Desconectado Alepcis

  • First Job
  • *
  • Mensajes: 307
  • Todo es un sueño, una falsa realidad.
  • Guild: Agua&Jabón[GL]
  • Pj Principal: Alepcis
Re:Guía Creación de cliente funcional.
« Respuesta #19 en: 06 de Noviembre de 2013, 18:47:05 pm »
Sube tu inter_athena.conf.

También revisa tener todas las tablas en el HeidiSQL en especial la de login.log
Un ejemplo
« Última modificación: 06 de Noviembre de 2013, 18:54:34 pm por Alepcis »




Desconectado Xeron

  • Novice
  • *
  • Mensajes: 14
Re:Guía Creación de cliente funcional.
« Respuesta #20 en: 06 de Noviembre de 2013, 19:10:16 pm »
Te lo pongo aquí ,aunque lo edité, pero  no se si te notifican cuando edito. GRACIAS

lo que no tengo es "loginlog"


Desconectado Alepcis

  • First Job
  • *
  • Mensajes: 307
  • Todo es un sueño, una falsa realidad.
  • Guild: Agua&Jabón[GL]
  • Pj Principal: Alepcis
Re:Guía Creación de cliente funcional.
« Respuesta #21 en: 06 de Noviembre de 2013, 19:31:31 pm »
Tendrás que revisar las tablas nuevamente es necesario para poder evitar los errores en la DB.




Desconectado Xeron

  • Novice
  • *
  • Mensajes: 14
Re:Guía Creación de cliente funcional.
« Respuesta #22 en: 06 de Noviembre de 2013, 19:41:38 pm »
Okey, pero a que te refieres con revisar?., ya veo que no existe la tabla loginlog. que hago la creo?. y todo lo que ella lleva dentro.? o tengo que volver al apartado donde explicas crear las tablas?

Desconectado Alepcis

  • First Job
  • *
  • Mensajes: 307
  • Todo es un sueño, una falsa realidad.
  • Guild: Agua&Jabón[GL]
  • Pj Principal: Alepcis
Re:Guía Creación de cliente funcional.
« Respuesta #23 en: 06 de Noviembre de 2013, 20:18:47 pm »
Sería lo más recomendable, hacer nuevamente la parte de las tablas.




Desconectado Xeron

  • Novice
  • *
  • Mensajes: 14
Re:Guía Creación de cliente funcional.
« Respuesta #24 en: 06 de Noviembre de 2013, 21:39:02 pm »
He creado la  nueva tabla "loginlog" yendo a mi emulador>sql-files>logs vuelvo a compilar para comprobar que todo funciona, abro el runserver-sql por si me da algún error. Abro el juego como administrador. Y al poner s1 y p1 que son el nombre y contraseña que tengo puestos. Me sale el mismo error "failed to authenticate"

Voy a repetir el paso de creación de tablas, pero luego tengo que modificar algo mas? el paso de visual studio, o el de sincroinzar la data con el cliente?



EDITADO: He vuelto a hacer todo desde cero, he vuelto a releer y hacer los pasos , paso a paso y al fin me ha dejado acceder.



muchas gracias por toda la atención,de verdad gracias.

por último, el archivo de "archivos complementarios" en el que esta el winrar "luafiles514" para que sirve? que hago con el? y ahora que ya tengo el servidor, como puedo hacer que mis amigos entren a jugar?
« Última modificación: 06 de Noviembre de 2013, 23:04:59 pm por Xeron »

Desconectado Alepcis

  • First Job
  • *
  • Mensajes: 307
  • Todo es un sueño, una falsa realidad.
  • Guild: Agua&Jabón[GL]
  • Pj Principal: Alepcis
Re:Guía Creación de cliente funcional.
« Respuesta #25 en: 07 de Noviembre de 2013, 10:18:28 am »
Los últimos archivos lua que dejé en un mensaje son para evitar la mala traducción de algunas cosas en el servidor. Para poder darle acceso a tus amigos tendrás que proporcionales una copia del cliente, grf y cambiar las direcciones IP de tu emulador y las del cliente.




Desconectado Bogante

  • Novice
  • *
  • Mensajes: 1
Re:Guía Creación de cliente funcional.
« Respuesta #26 en: 23 de Noviembre de 2013, 23:48:47 pm »
en el archivo rar de luas que publicaste en unos mensajes atras viene dentro 2 carpetas "lua files y luafiles 514" me podrias informar donde colocar cada una de ellas?

tambien tengo un problema extra, cuando los monstruos dropean item, no puedo recogerlos, lo mismo pasa cuando intento crear uno o que aparezca uno, por lo tanto en el training al principio cuando se supone que el npc te da los primeros equipos no aparecen en el inventario.

Desconectado Alepcis

  • First Job
  • *
  • Mensajes: 307
  • Todo es un sueño, una falsa realidad.
  • Guild: Agua&Jabón[GL]
  • Pj Principal: Alepcis
Re:Guía Creación de cliente funcional.
« Respuesta #27 en: 25 de Noviembre de 2013, 07:04:25 am »
Agrega las dos carpetas a tu Data.
Te dice algo el emulador, pueden ser problema de tu DB el cliente ¿modificaste algo?.




Desconectado Loreck

  • Novice
  • *
  • Mensajes: 6
  • Pj Principal: Nyamuz
Re:Guía Creación de cliente funcional.
« Respuesta #28 en: 24 de Marzo de 2014, 03:36:16 am »
Bien... parece que todo esta bien... el cliente y todo, sin embargo, cuando quiero acceder con usuario s1, contraseña p1... me dice que fallo en conctar al servidor, esto tiene arreglo?
Otra cosa, hay alguna modificacion para poder cambiar a full screen?

Desconectado Alepcis

  • First Job
  • *
  • Mensajes: 307
  • Todo es un sueño, una falsa realidad.
  • Guild: Agua&Jabón[GL]
  • Pj Principal: Alepcis
Re:Guía Creación de cliente funcional.
« Respuesta #29 en: 24 de Marzo de 2014, 07:07:00 am »
Para poder crear una cuenta deberás hacerlo de la siguiente forma

NOMBREDEUSUARIO_M (en caso de querer cuenta de hombre).
NOMBREDEUSUARIO_F(en caso de querer una cuenta de mujer).

Y una contraseña la que tú gustes, para poder iniciar posteriormente con la misma cuenta sólo deberás iniciar con el nombre de usuario sin el _M o _F.
Por ejemplo:
ID: alepcis_M
Password: 12345

Posteriormente para poder accesar deberás iniciar de la siguiente forma:
ID: alepcis
Password: 12345