Last edited by NaMeLeS; 09-03-12 at 03:35 AM.
Add culti 8 to the starter xml of the character templates and that way they can then pick if they want to go sage or demon, other than that, nope
Make a new account
Go to your mysql database with something like mysql
Change the account id of it to 16
use my force password addon for pwadmin to force change the password
log into the account ingame
there you have the templates
log into each one
go to iweb and use these ids to get the xmls
16 = Blademaster
17 = Mystic
18 = Seeker
19 = Wizard
20 = Psychic
23 = Venomancer
24 = Barbarian
27 = Assassin
28 = Archer
31 = Cleric
TAKE BACKUPS OF THE XMLS TOO, IT SOMETIMES GOES WEIRD WITH 1.4.4 AND CHANGES
Okay i will have to find out how to install iweb. Every time i try it is a blank page.
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: /role_testNO/../include/header.jsp(1,1) Page directive: illegal to have multiple occurrences of contentType with different values (old: text/html; charset=GBK, new: text/html; charset=UTF-8)
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:39)
org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:405)
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:234)
org.apache.jasper.compiler.Validator$DirectiveVisitor.visit(Validator.java:127)
org.apache.jasper.compiler.Node$PageDirective.accept(Node.java:549)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2163)
org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2213)
org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2219)
org.apache.jasper.compiler.Node$Root.accept(Node.java:456)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2163)
org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2213)
org.apache.jasper.compiler.Validator$DirectiveVisitor.visit(Validator.java:94)
org.apache.jasper.compiler.Node$IncludeDirective.accept(Node.java:597)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2163)
org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2213)
org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2219)
org.apache.jasper.compiler.Node$Root.accept(Node.java:456)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2163)
org.apache.jasper.compiler.Validator.validate(Validator.java:1452)
org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:157)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:267)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:255)
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:556)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:293)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:291)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
note The full stack trace of the root cause is available in the Apache Tomcat/5.5.9 logs.
Sigh. T_T