What's new
  • Visit Rebornbuddy
  • Visit Resources
  • Visit API Documentation
  • Visit Downloads
  • Visit Portal
  • Visit Panda Profiles
  • Visit LLamamMagic

Moving routine to new folder causes crashes.

Infinite Monkeys

Community Developer
Joined
Jul 7, 2012
Messages
224
Reaction score
16
I have a custom routine in the Legacy folder, and it works fine, but every time the bot updates it's removed from 3rdparty.json and has to be re-added. I tried moving it to the base 3rdparty folder, but it gives this error:
Code:
2018-03-23 14:53:04,899 [7] DEBUG Logger - [Navali] Enable
2018-03-23 14:53:04,900 [7] INFO  Logger - [Enable] Legacy.ObjectExplorer.ObjectExplorer
2018-03-23 14:53:04,901 [7] INFO  Logger - [Enable] Legacy.PythonExample.PythonExample
2018-03-23 14:53:04,902 [7] INFO  Logger - [Enable] SkillAwarePlayerMover.PlayerMoverPlugin
2018-03-23 14:53:04,903 [7] DEBUG Logger - [Skill-Aware Player Mover] Enable
2018-03-23 14:53:05,393 [7] ERROR Logger - An exception occurred.
System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Games\Path of Exile\EB\3rdParty\_CONFIGS_\Default\Legacy\Content-361055359\InfiniteRoutine\SettingsGui.xaml'.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
   at System.IO.FileStream..ctor(String path, FileMode mode)
   at Legacy.InfiniteRoutine.InfiniteRoutine.get_Control() in C:\Games\Path of Exile\EB\3rdParty\_CONFIGS_\Default\InfiniteRoutine\Content-361055312\InfiniteRoutine.cs:line 851
   at Exilebuddy.NewSettingsWindow.?????????????????????????????????????????()
   at Exilebuddy.BotWindow.?????????????????????????????????????????()
   at System.Windows.Threading.DispatcherOperation.InvokeDelegateCore()
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Windows.Threading.DispatcherOperation.Wait(TimeSpan timeout)
   at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherOperation operation, CancellationToken cancellationToken, TimeSpan timeout)
   at System.Windows.Threading.Dispatcher.Invoke(Action callback, DispatcherPriority priority, CancellationToken cancellationToken, TimeSpan timeout)
   at System.Windows.Threading.Dispatcher.Invoke(Action callback)
   at Exilebuddy.BotWindow.?????????????????????????????????????????(Object )

This is the 3rdparty.json:
Code:
{
  "AssemblyName": "InfiniteRoutine",
  "FileList": [
    "InfiniteRoutine.cs",
    "InfiniteRoutineSettings.cs",
    "SettingsGui.xaml"
  ],
  "Dependencies": [],
  "References": []
}

If I put the same FileList in the Legacy 3rdparty.json (with folder paths) and put the routine folder there, it works fine. As soon as I move the routine out of Legacy, it crashes. Neither .json has any dependencies or references, so it's not because they're missing. I've also tried deleting my config because it's mentioned in the error report, but it didn't help. Anyone know what I'm doing wrong?
 
The issue you're seeing is that you're using our content's folder for your stuff, which causes problems because when our stuff gets updated every patch, your files will be lost.

Instead, you need to setup your plugin to reside in its own folder outside of Legacy/Default

In other words, make a folder called "InfiniteRoutine" and have all your files in there instead.
 
Back
Top