File Write Error

[No_Remorse]

So I've been working on my zone pretty much all day. I uploaded a new version of my map with a few modications, and let the arena recycle like it should. Then when I enter my zone the download gets to 99% and I get a "file write error". I uploaded an earlier map that worked, same error. Any idea what it could be? Right now I can't enter my zone and neither can anybody else.

 

The zone is SSCV Dooms Day

Edited March 15, 2011 by No_Remorse

[Samapico]

Is the map file particularly large? Do you have large LVZ files? I think any file over 4MB will break Continuum.

[No_Remorse]

Nope, it's a modest 1180 kb

[PoLiX]

If your Continuum folder is in C:\Program Files\ this is your problem. It doesn't have permissions to overwrite the map file.

 

You can either move Continuum or delete the map file. Might be able to change permissions on the folder, but dunno.

[No_Remorse]

My Continuum directory isn't in program files. I had already tried to delete the map file and lvz before entering, with no luck. But uploading a smaller map however, seems to have worked.

 

So I uploaded a much smaller map and it granted me access to my zone, phew. However, when I try to upload a bigger map it tells me, "File has arrived, but is too big (size limit of 512k)". I had this same map up earlier today, I'm not sure what changed between then and now and how to change it back.

Edited March 15, 2011 by No_Remorse

[No_Remorse]

While I'm here...

 

I'm having an issue with the flag drop radius in my zone... The flags drop very far apart and are not bunching up like I intended. Here are my flag settings, I've tried several different variations with no luck. So maybe somebody here knows what I'm doing wrong.

 

FlaggerOnRadar=1

FlaggerKillMultiplier=1

FlaggerGunUpgrade=1

FlaggerBombUpgrade=1

FlaggerFireCostPercent=1000

FlaggerDamagePercent=900

FlaggerBombFireDelay=0

FlaggerSpeedAdjustment=1

FlaggerThrustAdjustment=0

CarryFlags=1

FlagDropDelay=10000

FlagDropResetReward=1

EnterGameFlaggingDelay=0

FlagBlankDelay=300

NoDataFlagDropDelay=500

FlagMode=1

FlagResetDelay=1440000

MaxFlags=24

RandomFlags=0

FlagReward=0

FlagRewardMode=1

FlagTerritoryRadius=1

FlagTerritoryRadiusCentroid=1

FriendlyTransfer=0

 

Also, I was wondering if there is a Mervbot plugin that disallows flag carriers/flag drops/flag neuts/powerballs in certain areas of the map. IE: the outside. And no, I'm not using ASSS so I can't use regions.

[PlayWolf]

Wasn't there a flag spawn radius?

[PaRa$iTe]

Can't help you with the flag dropping problem (if you mean that when the timer runs out, they don't drop close to whoever carried them), but as for the Mervbot plugin:

 

http://www.mervbot.com/plugins.php

 

Search for Flag Mover and Ball Mover (they're in alphabetical order). I don't know about checking for flag carriers, though; the closest

that I can think of right now is setting the bot to warp EVERYONE who is outside the map (there are numerous bots that could do that).

Better yet, design the map so that no one gets outside the borders without staff powers.

[No_Remorse]

It is flag DROP radius that I'm worried about, flag spawn radius is in check. The neuts seems to drop fine but the flag drops themselves are dropping in an area about 10 square inches around...

 

That's the tricky part... The outside border of my map is a bunch of races that you can get to via warp tiles. All I need to do is prohibit flag carriers in this area, pballs aren't that big of a deal.

 

edit- I still don't know why the server tells me there is a size limit of 512k when uploaded maps in my public arena. Considering I have been using a map that was over 1mb in size all along...

Edited March 15, 2011 by No_Remorse

[No_Remorse]

Still getting 'File Write Error' when I manage to upload a map bigger than 512kb...

[Samapico]

1180 kB for a .lvl file is pretty huge, to be honest... Try to get rid of some useless tiles, like if you have very thick walls, or text with 1 tile per character... You can use lvz images to replace these.

Or, if you have lots of ASSS regions defined, that can also take some space. Making them as square as possible also saves space, due to how they are stored in the file.

 

 

Are you using ASSS or subgame? I never seen that message about a filesize limit... when does it appear? Ingame as you send the file? On the server console when the map is opened?

Or is it a client message?

[No_Remorse]

Ya, it is huge. It's because my flagdrops are so spread out and i need real thick borders to prevent flags from getting outside. I deleted them all however, and managed to get my map back up. So the problem basically stems from the problem of the bad flag drops... That is now priority number 1.

 

Interesting point about the regions.

 

I'm on subgame. That message appears in game when I try to upload a map larger than 512kb.

 

The real problem now is the flagterritoryradius issue. Pure speculation here but I am using L.C.'s template.sss, so maybe that has something to do with it. My flag settings are listed above.

 

edit- My zone is SSCV Dooms Day if you are curious exactly how spread out the flag drops are. Devastation uses FlagDropRadius of 5 and their flags drop considerably closer together than the flags in my zone...

 

the description for flagterritoryradius reads; "When you drop flags, this is how far out a flag is from your ship (in tiles)(0=spawn in the center of the map)"

 

the description for flagterritoryradiuscentroid reads; "when you drop flags, this is how spread out a flag spawns from it's actual drop location (in tiles)(1024= anywhere on the map)"

Edited March 15, 2011 by No_Remorse

[Jareth]

It looks like there is a 1,000,000 byte limit (976KB) when Continuum is writing lvl files.

[No_Remorse]

You may be right. I did a quick search through most of directories of zones i've been in and the largest map file I found was 760kb.

 

The only time I get the "File has arrived, but is too big (size limit of 512k)" warning is when I try to upload a map obviously larger than 512kb without using the sysop password. When I do have the password on, it will upload the map regardless of size but if it's over 512kb I will get a "file write error" at about 90% download. But once I go back to a smaller map, it works properly. Either way, I can't upload anything over 512kb successfully.

[Cheese]

its called a 'hard limit'

[Samapico]

It's probably more of a limitation of the *putfile itself... If you have any other mean of transferring the file (i.e. FTP), you could try that. I remember testing and using maps much larger than 512kb in the past... But it could have been on a local server, I don't remember.

[No_Remorse]

I tested your theory uploading through the ftp and it did in fact work on a map larger than 512kb. Good idea. It may also have been due to the fact that I use the ?setlevel command to upload maps. Oh well, problem solved, thank you.

 

I did however try to upload the 1180kb map through that method and it gave me the 'file write error' message. I think Jareth was correct regarding the 1,000,000 byte size limit.

Edited March 16, 2011 by No_Remorse

[Dr Brain]

Hyperspace has had problems with maps as small as 700kb. Beware.