Recent content by Leesne

Unless its just because I'm really tired. This is related to your database and not MyAAC. If you have run migration 26, it has removed the field you need. TFS 1.4 uses the new premium_ends_at not 1.2 which uses premdays. TFS 1.2 is showing migrations up to 19...

What version of my aac are you using as this was implemented in and is in a Dev and main build with a check to see if column, premdays or premium_ends_at exists. Also what TFS are you using? That looks like a server error for the premdays and not relating to myaac?

something like this? https://otland.net/threads/tfs-1-x-shrines.263473/

Thats because MyAAC doesn't copy the town from the sample chars, it creates it based on the selection the player chooses when creating a char. if you wanted to change this you will need to edit a number of files. example...

^.^

This is my last post here, as I really can't be bothered any more, I've tried to show you the way and all I see if someone who wants stuff given without trying, I literally spelt it out in 3 posts on what to do. a simple search on the internet on how to modify DBs. ALTER TABLE player_deaths...

You can only have a unique value as primary key. So if player ID is set as primary key, in the players_deaths there will only ever be 1 entry for that user as this is the unique id (primary key) and cannot be any more entries. I was trying to let him come to the conclusion himself. Teach a man...

"id" ;) not player_id. or none at all https://github.com/otland/forgottenserver/blob/master/schema.sql#L265

Coding isn't just about reusing people's codes and databases. Sometimes its about thinking outside the box. Databases don't need primary keys but its highly recommended. Look at your other tables and see what they use as unique identifiers or primary keys

If I run into an area on a level 1000 mage and kill 10 level 8's in 1 hit. They will all die at the same time. So no.

If you had actually looked it up, you would see the issue. You setting it to player_id, means player_id must be a unique value. You can put a primary key pretty much where ever you want. but the data in it must be unique. As you are wanting multiple deaths per character setting player_id as...

Where ever you want it to be. "read up what a primary key does in databases."

You are just adding the value to the end of the table. #itemList never changes as you are not inserting. if player:getStorageValue(123123) >= 1 then for i = 1, #tomes[1] do table.insert(itemsList, tomes[1][i]) end end