Justn

Thank you. I tried that and still getting same issue. Maybe will try to reinstall VS completely. Seemed to be working fine a few days ago. I dont see anything in the code changes that would cause this.

Am I missing something when trying to pull the newest changes?

I think I may of solved my issue. I went through the source and my source is missing this change! I will test and update this post. Thanks Shenmue - if (mEntity.X < newX) + if (mEntity.X < newX && mEntity.Y == newY) Ok the error is gone. Moving SE still doesnt work once a npc locks on to the player but NE is fixed. Since I am the only one having this issue I assume it is the numerous sprite animations I have for players and npcs. Im sure I will get it worked out.

Yes then double click on the map and you should get a spawn icon to let you know where the NPC will spawn

you need to make sure the npc is highlighted on the list and click somewhere on the map to place a spawn marker.

Mine still follow me just fine. The only issue is that they do not move southeast or northeast after they target me. They will move up, down, up, down instead of diagonal. They will move southwest and northwest just fine when targeting.. also when they are not targeting a player they move just fine in all directions. Also getting an error on my server once they start chasing a player. Message: Index was outside the bounds of the array. Stack: at Intersect.Server.Entities.Pathfinding.SpatialAStar.StoreNeighborNodes (Intersect.Server.Entities.Pathfinding.PathNode inAround, Intersect.Server.Entities.Pathfinding.PathNode[] inNeighbors) [0x0016c] in C:\Users\Justin\Documents\New Intersect\Intersect-Engine\Intersect.Server\Entities\Pathfinding\SpatialAStar.cs:355 at Intersect.Server.Entities.Pathfinding.SpatialAStar.Search (Intersect.Point inStartNode, Intersect.Point inEndNode, Intersect.Server.Entities.Pathfinding.PathNode inUserContext) [0x0019e] in C:\Users\Justin\Documents\New Intersect\Intersect-Engine\Intersect.Server\Entities\Pathfinding\SpatialAStar.cs:185 at Intersect.Server.Entities.Pathfinding.Pathfinder.Update (System.Int64 timeMs) [0x008b2] in C:\Users\Justin\Documents\New Intersect\Intersect-Engine\Intersect.Server\Entities\Pathfinding\Pathfinder.cs:299 *I stated above that SE and NE were working.. I meant SW and NW are working.

Anyone else having an issue where the diagonal path-finding for NPCs only works for the northwest and southwest directions?

Started the slow process of adding new ground tiles for all my maps to make the transitions between new areas not so jagged. Still WIP Before: After:

Started messing around with the GUI this weekend... paperdolled select character screen create character working on player hud

Doesn't draw in the editor. To view you need to log in to the client to see the results.

Working great

During the first build I always have to close and reload Visual Studio and build again to get the sever to build. Have you tried that?

I tried this out with the new running animation. I noticed the FPS drop when going from stopped to walking or running and caused player to lag a bit. Any one else have this problem? Fps goes from 61 to 50 or below when I start to walk or run.

What errors are you getting?

yes

2

@Celtos Make sure your paperdoll stuff in the server config.json file is correct. I had the same issue as you cause the format had changed after applying the patch causing the crash.

Hmm just tested it on my end and it worked fine. Hopefully someone can help you figure out the issue. What version are you using?

EDIT: Please ignore my dumb post. Somehow when I ported over changes to my server host the config.json file didnt have the correct paperdoll order. Maybe someone can help me take a look at this. I am getting a client crash when attempting to log in to an existing account with hair. When creating a new account or character I have no issues it is only when I try to log back in. I currently have 3 players per account set and the crash happens when it tries to load the character select screen. -------------------------------------------------------------------------------- 2020-04-23 05:14:14.987 [Error] Message: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index Stack: at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource) at System.Collections.Generic.List`1.get_Item(Int32 index) at Intersect.Client.Interface.Menu.SelectCharacterWindow.UpdateDisplay() in C:\Users\Justin\Documents\New Intersect\Intersect-Engine\Intersect.Client\Interface\Menu\SelectCharacterWindow.cs:line 249 at Intersect.Client.Interface.Menu.SelectCharacterWindow.Show() in C:\Users\Justin\Documents\New Intersect\Intersect-Engine\Intersect.Client\Interface\Menu\SelectCharacterWindow.cs:line 320 at Intersect.Client.Interface.Menu.MainMenu.CreateCharacterSelection() in C:\Users\Justin\Documents\New Intersect\Intersect-Engine\Intersect.Client\Interface\Menu\MainMenu.cs:line 269 at Intersect.Client.Interface.Menu.MainMenu.Update() in C:\Users\Justin\Documents\New Intersect\Intersect-Engine\Intersect.Client\Interface\Menu\MainMenu.cs:line 169 at Intersect.Client.Interface.Menu.MenuGuiBase.Draw() in C:\Users\Justin\Documents\New Intersect\Intersect-Engine\Intersect.Client\Interface\Menu\MenuGuiBase.cs:line 66 at Intersect.Client.Interface.Interface.DrawGui() in C:\Users\Justin\Documents\New Intersect\Intersect-Engine\Intersect.Client\Interface\Interface.cs:line 175 at Intersect.Client.Core.Graphics.Render() in C:\Users\Justin\Documents\New Intersect\Intersect-Engine\Intersect.Client\Core\Graphics.cs:line 484 at Intersect.Client.MonoGame.IntersectGame.Draw(GameTime gameTime) in C:\Users\Justin\Documents\New Intersect\Intersect-Engine\Intersect.Client\MonoGame\IntersectGame.cs:line 247 at Microsoft.Xna.Framework.Game.DoDraw(GameTime gameTime) at Microsoft.Xna.Framework.Game.Tick() at Microsoft.Xna.Framework.SdlGamePlatform.RunLoop() at Microsoft.Xna.Framework.Game.Run(GameRunBehavior runBehavior) Here is line 249: if (Options.EquipmentSlots.IndexOf(Options.PaperdollOrder[1]) == Options.EquipmentSlots.IndexOf(Options.Equipment.HairSlot)) Any ideas? EDIT Please ignore my dumb post. Somehow when I ported over changes to my server host the config.json file didnt have the correct paperdoll order.

I know Tibia has a few different types of severs when it comes to Player killing. I think the base severs have pop up warning that you are about to attack a player with a toggle to turn on/off the warning on the main ui.

Has anyone attempted to block the attacking animation from starting while walking or is this a engine limitation at the moment? There already seems to be a check for a If moving = then just walk. I have attempted to add !IsMoving in a few sections below but seems to not stop the attack animation completely. Thank you. SpriteAnimation = AnimatedTextures[SpriteAnimations.Idle] != null && LastActionTime + TimeBeforeIdling < Globals.System.GetTimeMs() ? SpriteAnimations.Idle : SpriteAnimations.Normal; if (IsMoving) { SpriteAnimation = SpriteAnimations.Normal; LastActionTime = Globals.System.GetTimeMs(); } else if (AttackTimer > Globals.System.GetTimeMs()) //Attacking { var timeIn = CalculateAttackTime() - (AttackTimer - Globals.System.GetTimeMs()); LastActionTime = Globals.System.GetTimeMs(); if (AnimatedTextures[SpriteAnimations.Attack] != null) { SpriteAnimation = SpriteAnimations.Attack; SpriteFrame = (int)Math.Floor((timeIn / (CalculateAttackTime() / 3f))); }

Easy way to disable is by finding these in the CharacterCreationWindow.json and setting Hidden and Disabled to true for the following If you just want select a Player name "ClassCombobox" "CharacterContainer" "GenderPanel" "MaleCheckbox" "Checkbox" "FemaleCheckbox" "Disabled": false, "Hidden": false, Then have an unlocked default class to beable to create your player's name and lock all the classes you want to select via events.

A weight system might be a better option then limiting each item. Also good job kasplant.

Try picking a hairstyle first @Shenmue

Yea they changed the server packetsender.cs quite a bit yesterday in the dev branch causing the conflict.