Any ideas?
Dear forum users! In compliance with the new European GDPR regulations, we'd just like to inform you that if you have an account, your email address is stored in our database. We do not share your information with third parties, and your email address and password are encrypted for security reasons.
New to the forum? Say hello in this topic! Also make sure to read the rules.
New to the forum? Say hello in this topic! Also make sure to read the rules.
Server shutdown
Forum rules
By using the forum you agree to the following rules. For this forum you also need to follow these additional rules.
By using the forum you agree to the following rules. For this forum you also need to follow these additional rules.
- Captain_dikal
- Fighter
- Posts: 10
- Joined: Mon Apr 11, 2016 12:53 am
- Title: Mapmaker?
- SFD Account: Captain_dikal
- Location: Russia
- Gender:
Server shutdown
0 x
- Gurt
- Lead Programmer
- Posts: 1884
- Joined: Sun Feb 28, 2016 3:22 pm
- Title: Lead programmer
- Started SFD: Made it!
- Location: Sweden
- Gender:
- Age: 34
Do you see any additional information in your \Documents\Superfighters Deluxe\Reports\ folder? Try to locate a textfile with creation date around the same time as the message.
Otherwise it's most likely an unresponsive script causing this in the current version of SFD (fix to terminate unresponsive scripts in Events will come in the next update).
Otherwise it's most likely an unresponsive script causing this in the current version of SFD (fix to terminate unresponsive scripts in Events will come in the next update).
0 x
Gurt
- Captain_dikal
- Fighter
- Posts: 10
- Joined: Mon Apr 11, 2016 12:53 am
- Title: Mapmaker?
- SFD Account: Captain_dikal
- Location: Russia
- Gender:
The first thing I checked there. No log files. So just wait for the next game update?Gurt wrote: ↑Thu Sep 05, 2019 5:50 pmDo you see any additional information in your \Documents\Superfighters Deluxe\Reports\ folder? Try to locate a textfile with creation date around the same time as the message.
Otherwise it's most likely an unresponsive script causing this in the current version of SFD (fix to terminate unresponsive scripts in Events will come in the next update).
0 x