TheGodOfLegends

velho mudei pra vivo fibra to com mesmo problema, e agorA? pqp.

tem scriptado ja o critiacl strike leech e tals? alguem tem link tbm pra baixa ip cahnger 11.0? n acho

o que é preciso para ter os itens com a tag de dual wield de vvolta?

tive este erro também, uso windows 8.10 como corrigir? coloquei todas as DLls 64bits

obrigado pelas respostas..se alguem souber se funciona windows 8.10 me avisa de algum jeito abrass parabéns.

meu win é 8.10 nao roda? Outra pergunta, os scripts, a linguagem mudou 1 pouco tipo ficou player: ... os scripts antigos não funcionariam nesta versão? teria como fazer 1 lib pra deixa ras funções antigas ..ainda funcionais? ex; fiz 10 mil scripts pras versões anteriores, tipo 10.31 nao da pra usa-los mais teria q mudar td?

Alguém ajuda pf? todos os Ots 10.8+ quando tento abrir eu baixo dll 1 por 1 , 64bits todos e da esse erro dps q baixa td:

me ajuda mano, no meu server qdo eu uso mais de 1 script com modeldialog Mesmo usando nomes diferentes nos callback e no dialog (ex: callback333 e modeldialog335) qdo eu mando usar 1 script ta chamando a janela do outro q ntem nada haver 1 coisa com a otra ex: o 1 script pra escolher profissão por janela/choice E outro pra ver rank no de escolher rank aparece o das profissão

hey man, ajuda urgente, toda vez que uso uma magia de convince creature o server crash n sei oq fazer. o server é perfeito td foda mas sem arrumar isso n da pra usar ele meu server é cheio de magia de convince creature /summoning

tenso cmg também não vende os itens novos que criei, e quand odou look , manda o nome de um item parecido vender tbm nao da

ta dando o msm erro aqui tbm bang do net framework como resolvo? ja baixei tds os net framework q tem :s ajjuda ae See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** File name: 'file:///C:\The World Of Legends\Alissow OTS 5.0 (2013)\Alissow OTS 5.0 (2013)\EDITORS\otitemeditor (1)\plugins\plugin1000.dll' ---> System.NotSupportedException: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information. at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, Boolean suppressSecurityChecks, StackCrawlMark& stackMark) at System.Reflection.Assembly.LoadFrom(String assemblyFile) at Host.PluginServices.AddPlugin(String FileName) at Host.PluginServices.FindPlugins(String Path) at Host.PluginServices.FindPlugins() at otitemeditor.otitemeditor.otitemeditor_Load(Object sender, EventArgs e) at System.Windows.Forms.Form.OnLoad(EventArgs e) at System.Windows.Forms.Form.OnCreateControl() at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) at System.Windows.Forms.Control.CreateControl() at System.Windows.Forms.Control.WmShowWindow(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.ContainerControl.WndProc(Message& m) at System.Windows.Forms.Form.WmShowWindow(Message& m) at System.Windows.Forms.Form.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.17929 built by: FX45RTMREL ---------------------------------------- otitemeditor Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.17929 built by: FX45RTMREL ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.17929 built by: FX45RTMREL ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.17929 built by: FX45RTMREL ---------------------------------------- PluginInterface Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.17929 built by: FX45RTMREL ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.17929 built by: FX45RTMREL ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box. e se eu ignoro o erro; fala q deu erro do plugin 47; ( to tentando usar pra 9.83)